Error 80040403 - Could Not Open QuickBooks File

Modified on Sat, 29 Jun at 3:42 AM

Overview

You have an error in the QQube Synch log:


<<<<<<<<<<<<<<<<<<<<<< 10/15/2024 06:44:57 PM >>>>>>>>>>>>>>>>>>>>>>
QBXMLSession_OpenConnection
File named F:\QB Data\Rock Castle.QBW is not opened.
BeginSession
Error Code: 80040403
Could not open the specified QuickBooks company data file.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


Cause

This error comes directly from the Intuit Software Development Kit (SDK) and indicates that it either cannot find the specified QuickBooks (Non-Enterprise) file, or it is finding it, but can't connect to it.


There are four possible causes:

  1. Different QuickBooks File Name. You have QuickBooks open to a different file, OR the name of the QuickBooks file has been changed, and no longer matches the name that was originally used when added to the QQube Configuration Tool.
  2. Different QuickBooks Path. This generally occurs if somebody moves the QuickBooks file, and it is now different than what you originally setup inside the QQube Configuration Tool.
  3. QuickBooks is setup to run as administrator.  QQube cannot talk to QuickBooks if this "run as administrator property" is set
  4. The Company File has not been updated to the latest Release of QuickBooks. QuickBooks requires that the latest update must be applied after a specified number of attempts.  There are no exceptions to this Intuit rule.
  5. There is corruption in the sign-in mechanism (user) that you assigned from QuickBooks. This might involve the regular QuickBooks user you assigned to login to QuickBooks, or it might involve the special Intuit user which Intuit enforces on files that use other 3rd party Intuit apps, like Merchant Services, or Payroll.


Resolution

Cause 1. You can either change the QuickBooks company file name back to what was previously listed in the QQube Configuration Tool and Remove and Add the company file to reset the correct name. (You can't change the name of the company in the QQube Configuration Tool Directly).  If you have a multi-user version, you can only do this on the server while logged in where you installed QQube.






Cause 2. Use the QQube Configuration Tool to change the path. If you have a multi-user version you must do this on the server while logged in where you installed QQube.




Cause 3. Ensure that the properties for the QuickBooks Icon is not checked to be "Run As Administrator".  




Cause 4. This may involve multiple steps.

  1. First, open up the QuickBooks file, and make sure the latest release has been applied, and that you can open up the QuickBooks file manually.
  2. Run the QuickBooks Tool Hub choosing both the file and network options: https://quickbooks.intuit.com/learn-support/en-us/help-article/login-password/fix-common-problems-errors-quickbooks-desktop-tool/L3Yab5gNN_US_en_US


Cause 5. This may involve multiple steps.

  1. Attempt to login manually to the affected company file - using the regular QuickBooks user you have designated for QQube to auto login.  It should be free of errors.  If, by some chance, it is requesting a special Intuit user - you must create that, and it MUST be a different e-mail for each QB file you have in QQube.  The portion of the last statement is critical.
  2. Once you can login manually with the regular QuickBooks user (and the special Intuit user if prompted), without error, then attempt to just run the company setup data model for that company in QQube.  It should run.  If it doesn't:
    1.  Remove the regular QuickBooks user you designated for QQube to access the file.
    2.  Remove QQube from the Integrated Applications in QuickBooks (Edit>Preferences>Integrated Applications)
    3.  Rebuild the QuickBooks file
    4.  Remove and Add the company file in the QQube Configuration Tool to reset the correct name.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article