Error 80040402 - Unexpected error | CLEARIFY

Correcting Error Code 80040402

There is an error entry at the bottom of the log similar to this: 

Cause

This error comes directly from the Intuit Software Development Kit (SDK) and indicates that QuickBooks has shut down abruptly - and unable to further communicate with the file.

There are three possible causes:

1. Server synch user logs out instead of disconnects. On a server the dedicated synch user is always logged in, per our implementation guides.
2. You have another QuickBooks 3rd party application attempting to write to - or extract data from - QuickBooks while the QQube data synch is in progress.
3. You have corruption in your QuickBooks file.

Resolution

Cause 1.  Please review our installation guides. The dedicated synch server user (in a remote desktop environment) - or the administrative console (in a local network environment) never gets logged out of.  If you log out of that dedicated server user, then the QuickBooks client can't run, and therefore QQube cannot communicate with QuickBooks.  Remember that developers do not have direct access to the database, and instead communicates via the QuickBooks client (not database server).

Cause 2.  The Intuit SDK (Software Development Kit) does not allow two applications to simultaneously communicate with QuickBooks. Make sure that no other 3rd party QuickBooks application - including their backup program - runs at the same time QQube attempts to communicate with QuickBooks and extract data.

Cause 3.  Rebuild the QuickBooks file and reload from scratch in QQube as shown in the pictures at the bottom of this guide: Maintaining QuickBooks Data Integrity in QQube  This has a 50/50 chance of working.  If you get this same error again, then it is necessary to contact QuickBooks support and convince them to take the file into Intuit Data Services to repair the file.

CONVINCING INTUIT TO TAKE YOUR FILE

If you perform a rebuild, using the QuickBooks  - and it shows no errors - and you still get the same 80040402 error during the synch, then there is a corruption problem underneath the hood, that the rebuild, or verify logs may - and probably won't - not show.

If you attempt to contact QuickBooks about this issue, without taking the next steps, they will not take the file, and attempt to throw the problem back at you - and QQube.  However, we, like all QuickBooks 3rd party developers, are beholden to the Intuit SDK. If the SDK is unable to pull data, there is nothing that anybody can do to get around the problem.

So, we need to give Intuit Support proof that the SDK is unable to extract the information from QuickBooks.

THE INTUIT SDK CREATES A LOG

There is a file called qbsdklog.txt in which Intuit logs SDK the details of the interaction between QuickBooks and a 3rd party application like QQube.  It is located in c:\ProgramData\Intuit\QuickBooks

When you get the 80040402 error a second time, immediately grab the qbsdklog.txt and Create a Support Ticket, attaching that file, as well as the QQube synch log.

We can review the files, and ensure that you have the correct "ammunition" you need to convince Intuit that you have corruption in your file, and that they need to accept the file to fix it.

IF THE FILE IS LARGE CONSIDER ALTERNATIVES

If your file is one of the following:

• QuickBooks Enterprise file approaching 1.25 Gig
• QuickBooks Premier files larger approaching 350 Meg
• QuickBooks Pro files approaching 250 Meg
• QuickBooks file containing more than 10 years of data

Then we strongly advocate getting someone like Matt Clark at https://www.qbornotqb.com to split your file into two files:  (1) with old data, that you can open - or store in QQube, and (2) a current file for every day use.  DISCLAIMER: We do not receive kickbacks from this company - we recommend him because he has successfully taken care of hundreds of customers over the last decade.