You are using an unsupported browser. Please update your browser to the latest version on or before July 31, 2020.
close
Need immediate help? Phone support is available between Monday and Friday from 9am to 9pm EST at 888-297-6172
announcement close button
Trouble Connecting to the QuickBooks File
print icon

ISSUE:

When connecting Rightworks Transaction Pro Importer (TPI), Exporter (TPE), or Deleter (TPD) to a QuickBooks Desktop (QBDT) or QuickBooks Enterprise (QBE) company file, one of the following messages appear:

  • Please start QB and open your company file before continuing
  • Automation error The object invoked has disconnected from its clients
  • This application has not accessed this QuickBooks company data file before. The QuickBooks administrator must grant an application permission to access a QuickBooks company data file for the first time.
  • QuickBooks found an error when parsing the provided XML text stream

 

RESOLUTION:

Please follow the steps below to troubleshoot this issue. Try each step until a resolution is found.
 

  1. Ensure that QB is installed, the QB company file is opened, and only one QB company is opened.
  2. Check that the minimum systems requirements are met to use the TP application. System Requirements are found at bottom of this page.
  3. Ensure that User Account Control  (UAC) is set to NOTIFY ME ONLY WHEN APPS TRY TO MAKE CHANGES or ALWAYS NOTIFY ME.
  4. Ensure that both QB and TPro are not being started with the shortcut security tab option RUN AS ADMINISTRATOR. The QBSDK requires non-elevated Windows permissions for both products, and this box must not be checked.
  5. Be sure that the Quick Startup feature is disabled. Applications that use the QBSDK cannot be used when this feature is enabled. To disable this feature, in QB select the EDIT menu and click PREFERENCES. Then select the GENERAL section and the MY PREFERENCES tab, and uncheck the box labeled KEEP QUICKBOOKS RUNNING FOR QUICK STARTUPS.
  6. Change the Data Execution Prevention (DEP) settings in Windows
    1. Go to System Properties
    2. Select Advanced Tab
    3. Click Performance Settings button
    4. Select the Data Execution Prevention tab 
    5. Select the first option TURN ON DEP FOR ESSENTIAL WINDOWS PROGRAMS AND SERVICES ONLY.
    6. Or select the second option and add the TPI file by clicking ADD and selecting the file C:\Program Files\01 Transaction Pro Importer (version #)\Transaction Pro Importer (version #).exe (where version # = your version of the TPro application)
  7. Verify that the QB Admin user has granted permission to the QB company file.
    1. Close TPro application
    2. Open QB file logged in as the ADMIN user and in single user mode
    3. Click EDIT and select PREFERENCES
    4. Select INTEGRATED APPLICATIONS
    5. Click the COMPANY PREFERENCES tab
    6. Remove all applications named BAYSTATE CONSULTING (if present)
    7. Click OK
    8. Restart TPro application with the QB ADMIN still logged into the company file. Make sure to choose YES, WHENEVER THIS COMPANY FILE IS OPEN (third option).
    9. Note that if running US and non-US versions of QB on the same machine, this will cause an issue. The same is true for attempting to run older versions of UK/CA/AU with current versions.
  8. Determine if the issue is a corrupt QB interface or the TPro application
    1. Download, install and run the QB SDK Diagnoses Tool (attached on the right-hand side of this article) to determine if the problem is a QB or TPro issue.
    2. If unable to connect with the SDK Diagnosis Tool, then it may be because the QB interface files have been overwritten or corrupted. Follow the instructions found in item 9 below to clean up the installation.
  9. The QBSDK may be damaged. Follow these steps to repair this issue:
    1. Close QB
    2. Delete the following folder: C:\Program Files (x86)\Common Files\Intuit\QuickBooks. 
      • Note: Any QB processes still running in Windows Task Manager after QB is closed first need to be stopped in order to be able to delete the folder.
    3. Reboot the computer
    4. Re-install QB
    5. Re-install TPro
Feedback
0 out of 2 found this helpful

Attachments

QBSDKDiagSetup.exe
scroll to top icon