A recent QuickBooks update for QuickBooks 2014, 2015 and 2016 versions has changed the way QuickBooks allows unattended/closed-mode syncing to function for 3rd party applications, such as Qvinci. Some users may find that their unattended/closed-mode syncing is not functioning as it did in the past. In Qvinci this sync process is known as Bulk Syncing.
Intuit, in efforts to increase security in QuickBooks Desktop, release an update for 2015 and 2016 versions when files contain fraud sensitive data (credit card numbers, social security number, bank numbers, etc). When 2015 or 2016 QuickBooks files contain this fraud sensitive data and undergo a QuickBooks update (r-version update) the "strong password" workflow is implemented. This means a user must update their QuickBooks password to contain upper and lower case letters, numbers and symbols. However, it is the handling/storage of these passwords which causes issues for closed-mode/unattended syncing. The update took place in June 2016 for QuickBooks 2015 and 2016, and in October 2016 for QuickBooks 2014.
The prior workflow was as follows:
- When a QB file is connected to a 3rd party application a .LGB file was created
- The .LGB file held the encrypted login credentials to the corresponding QB file
- The .LGB file was stored in the same file folder as the corresponding QB company file
- When a 3rd party application (which was already connected to the QB file) attempted a closed-mode/unattended sync (syncing while QB was closed) the .LGB file allowed the 3rd party application to access the QB file for syncing by offering the encrypted login credentials for access
What QuickBooks Changed:
- The .LGB files have been replaced with .SDU files
- The new .SDU files no longer reside in the same file folder as the corresponding QuickBooks company file
- The new .SDU files must be manually created for every QB file in order for closed-mode/unattended syncing to be able to resume
- Not all environment types will be able to have closed-mode/unattended syncing function again, even with .SDU files having been created
What components are needed:
- The filepath that the Qvinci Sync App shows (this could be a UNC or mapped path (this precise path is VERY important))
- The Windows user account in question (which Windows user is trying to perform a closed-mode/unattended sync)
- The QB user account which performed the connection to Qvinci (almost always the Admin)
- QuickBooks 2014 needs to be running R-version 14+; QuickBooks 2015 needs to be running R-version 10+; QuickBooks 2016 needs to be running R-version 7+.
How to create .SDU files:
- Log into the Windows user account in question where unattended/closed-mode syncing needs to occur (if this is more than 1 user these steps will need to be repeated for each Windows user account)
- Open the Qvinci Sync App and log into the Link tab. Notate the filepath that is shown for the first location you wish to address (this may be a UNC or mapped path)
- Launch the QuickBooks application (not a QB file, but the application itself)
- Chose the option to "Open or Restore existing QB file"
- In the "browse to" screen input the filepath that was shown in the Qvinci Sync App for the location (again, possibly a UNC or mapped path) and click enter
- Proceed with opening the QB file and log in using the QB user account which was utilized when linking this file to Qvinci (likely Admin)
- From inside the QB file migrate to Edit > Preferences > Integrated Applications > Company Preferences tab
- Click on Qvinci in the center of the screen and click the "Reauthorize button" (no confirmation will be given when done)
- Close this QB file and proceed to repeat steps 2-6 for the next QB file. There is no need to perform step 7-8 for subsequent files (Reauthorize is only needed one time per Windows user account). The goal here is to simply log in to each QB file using the file path that Qvinci Sync App shows
- Once the user has logged into each QB file using the appropriate file path that appears in Qvinci Sync App they should check that .SDU files have been created
Check if .SDU files have been created
- In the Windows user account where QB files were logged into for .SDU creation the user should migrate to this folder: C:/users/"Windows User Name"/Intuit/QuickBooks (if the Windows user does not see the C: drive their IT person needs to grant visibility for them)
- Inside this QuickBooks folder (under the same Windows user account folder) the Windows user should see folders with long strings of names (GUID folders)
- Inside each GUID folder should be a .SDU file for each QB file that was included in the above steps
- The timestamp of each .SDU file will correspond with the date/time that the Windows user logged into the QB file during the above "create .SDU file" steps
- The .SDU file is where the encrypted login credentials reside for the specific combination of "Windows user account + QB user account + Qvinci file path"
- Every user who needs to be able to perform unattended/closed-mode syncing will need to create their own .SDU files because the process for generating the .SDU files is specific to the combination of "Windows user account + QB user account + Qvinci file path"
The user may now attempt a Qvinci Bulk sync process (closed-mode/unattended sync).
To learn more about this QuickBooks update and how it affects closed-mode syncing please view the QuickBooks article here.
Note: There are times when a terminal services environment sees issues occur with Qvinci's bulk syncing capabilities. Typically this revolves around other Windows user accounts actively using QuickBooks on the server at the same time. It is advised that all additional user accounts log out of the QuickBooks process while a bulk sync is attempted by the desired user. At times QuickBooks can see issues, when a terminal service environment exists, because QuickBooks can get the user account requesting the bulk sync crossed with another. It is advised to test bulk syncing with all additional Windows user accounts logged out of QuickBooks when it appears that Qvinci's bulk syncing is not working in a terminal services environment.