Error 80040408 - QuickBooks Doesn't Start

Modified on Sat, 29 Jun at 3:44 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.
BeginSessionError Code: 80040408 Could not start Quickbooks
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


Cause


This error comes directly from the Intuit Software Development Kit (SDK) and indicates that it is unable to open the requested QuickBooks company file because it is "not clear" to do so.  It is the most common error.


There are eight possible causes:

  1. QuickBooks is currently opened by someone else in single user mode.
  2. QuickBooks is currently opened by another colleague using the same QuickBooks QQube user you created and assigned to connect to QuickBooks.
  3. 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.
  4. 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.
  5. QuickBooks is setup to run as administrator.  QQube cannot talk to QuickBooks if this "run as administrator property" is set
  6. Multiple QuickBooks company files. QuickBooks is open to a particular company file before attempting to load multiple company files.
  7. In a Multi-User environment, someone logged out of the user account where the synch takes place - instead of disconnect.
  8. Incorrect Setup in a Remote Desktop/Terminal Services Environment.  QQube is not installed in this environment according to these instructions.


Resolution


Cause 1. This usually happens when someone remotely logs in and needs to perform an 'Administrator' only task, requiring single user mode, to merge accounts, items.  Etc. Just requires awareness.


Cause 2. This can occur if the specific QQube user to automatically open the QuickBooks file, is being logged into elsewhere by another user.  This can also occur with an incorrect setup in a Remote Desktop / Terminal Services environment where several users are erroneously setup to synch the data.  (See Cause 8. below.)


Cause 3. You can either change the QuickBooks company file name back to what was previously listed in the QQube Configuration Tool, or Add or Remove 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 under the user where you installed QQube.




Cause 4. Use the QQube Configuration Tool to change the path. If you have a multi-user version, you can only do this on the server under the user where you installed QQube.




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




Cause 6. Open up QuickBooks to NO company file, before attempting to load multiple QuickBooks files.  The Software Development Kit (SDK) does not allow developers to close a QuickBooks file that is already manually opened.


QuickBooks Open to No Company File



Cause 7.  The synch takes place under a specific user where you install QQube (Administrator on a local network; [qqubesynch] on a remote desktop or hosted network.)  If you log out of that user where the synch takes place, then the QuickBooks client can't run, and therefore QQube cannot communicate with QuickBooks.  You can, however, disconnect. If you are unfamiliar with the proper implementation, please review our installation guides.


Cause 8.  The synch takes place under the user where QQube is installed.  However, regular users, in a multi-user implementation, may erroneously attempt to run the synchronizer under their own user name (or erroneously install an update under their own user name causing the synch to auto kick off), and cause errors like this to occur.  A regular user is never a synch user unless you have a single-user on a workstation or laptop.  If you are unfamiliar with the proper implementation, please review our installation guides.

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