Troubleshooting Get Data Problems with Reckon Accounts
Overview
The purpose of this article is to assist you troubleshooting connection issues with Reckon Accounts / QuickBooks.
Authorising BudgetLink to connect to Reckon Accounts data file
For BudgetLink or other third-party software to connect to your Reckon Accounts data file, the BudgetLink application must be authorized to connect. Sometime, this authorization does not carry through when upgrading Reckon accounts. For further information, see Authorising BudgetLink to connect to a Reckon Accounts data file.
Check the QBSDK log file
The Reckon Accounts / QuickBooks API creates a log file for all connections made to their data files. This log file can assist you in debugging connection issues.
Before checking the log file, we recommend editing the associated ini file to ensure the logging is set to verbose.
For Windows 7/8/10, the files are usually located in the following location.
- Ini File: C:\ProgramData\Intuit\QuickBooks\qbsdk.ini
- Log File: C:\ProgramData\Intuit\QuickBooks\qbsdklog.txt
For Windows XP and Vista, the files are usually located in the following location.
- Ini File: C:\Documents and Settings\All Users\Application Data\Intuit\QuickBooks\qbsdk.ini
- Log File: C:\Documents and Settings\All Users\Application Data\Intuit\QuickBooks\qbsdklog.txt
Edit the qbsdk.ini and add or edit the following lines.
- [Log]
- Level=verbose
- UnlimitedSize=Y
- [Parser]
- DumpRequestData=Y
- SdkAccelerator=N
Note that once debugging is complete, we recommend you turn off the verbose logging as it can slow reckon accounts down considerably.
- [Log]
- Level=info
- UnlimitedSize=N
- [Parser]
- DumpRequestData=N
- SdkAccelerator=N
When scanning for errors in the log file, we recommend you try to find lines that mentionned the words Error or Failed.
Clearing the QBINSTANCEFINDER17.INI file
An ini file is created by Reckon Accounts / QuickBooks to help the QBSDK identify the correct running instance. If any connection errors exist regarding starting or opening a data file, we recommend you backup the QBINSTANCEFINDER17.INI and then clear it. This will ensure that any corruption in the INI file is removed.
For Windows 7/8/10, the log file is usually located in the following location.
- C:\ProgramData\Intuit\QuickBooks\QBINSTANCEFINDER17.INI
For Windows XP and Vista, the log file is usually located in the following location.
- C:\Documents and Settings\All Users\Application Data\Intuit\QuickBooks\QBINSTANCEFINDER17.INI
Ensure both BudgetLink, Excel, Reckon Compatibility settings are using the defaults
Connection problems between software and Reckon Accounts / QuickBooks can occur if the user context between them is different.
With that in mind, we recommend that all compatibilitity settings be unticked for all three applications. To do so, follow these steps.
- Right-Click on the software's executable;
- Select the Compatibility tab;
- Untick Run this program in compatibility mode for;
- Untick Run as Administrator
- Click OK to save the settings;
- Restart the software.
To confirm that the software is not running in compatibility mode, follow these steps.
- Start all software;
- Open Task Manager;
- Go to the Details tab;
- Go to View and click on Select Columns;
- Tick the following options: Operating System Context, Elevated, UAC Virtualisation, Data Execution Prevention;
- Confirm they all use the same settings.
Permissions
Incorrect or corrupt windows permissions may cause issues with the API. We recommend granting Full Control to the following folders.
- C:\Program Files (x86)\Intuit\
- C:\Program Files (x86)\Common Files\Intuit\
- C:\ProgramData\Intuit\QuickBooks\
- C:\Documents and Settings\All Users\Application Data\Intuit\QuickBooks\
Run the Reboot.bat batch file
Reckon Accounts / QuickBooks ship a special Reboot.bat batch file that registers and installs various components. Running the Reboot.bat batch file as administrator may resolve most issues or problems with Reckon Accounts / QuickBooks.
The file is usually located in the C:\Program Files (x86)\Intuit\<latest version of Reckon or QuickBooks>.
Once you've run the file, we recommend rebooting the machine and seeing if the problem is fixed.
Test using the Windows Administrator user
We've found that sometimes, Reckon Accounts / QuickBooks is incorrectly configured for specific windows users. We recommend you test with the default Administrator windows account when starting your machine and seeing if you can connect correctly.
Test using a new Windows user account
We've found that sometimes, the current windows users account used is incorrectly configured. We recommend you create a new Windows user account and test to see if that account can connect successfully.
Rename your QBW data file
We've found an odd issue with the digital certificate used to sign an executable file. If it changes substantially (from SHA-1 to SHA-256 for instance), it can cause the get data process to fail while the file is closed. We believe some information is stored in the additional reckon files (ending with extensions such as .ND, .LGB, .QBW.ND and .QBW.TLG).
To resolve this issue, the best approach is to backup your Reckon Accounts / Quickbooks data file.
Then, rename only the .QBW file to a different name.
Once done, re-browse and reauthorise the data file using the new name and it should resolve the connection issue.