When the QuickBooks the Web Connector starts never finishes opening the company file, the Web Connector waits on "Connecting to QuickBooks..." with no timeout and calls nothing, blocking every entry behind it; ending the QuickBooks process gives connectionError 0x80040402
Observed 2026-11-11 on QuickBooks Enterprise Solutions 24.0 (US), Web Connector 34.0.10010.76, QBXMLRP2 v34.13.
When the Web Connector has to start QuickBooks itself for an entry authorized to run while QuickBooks is closed, the start can hang while the company file opens. The Web Connector then makes no call after authenticate: its window reads "Connecting to QuickBooks...", your service hears nothing more from that entry, and every other entry on the same Web Connector waits behind it. The longest wait seen was 34 minutes, and it had not timed out.
The Web Connector's qbsdklog.txt stops mid-open (its level column left out):
20261111.110909 16364 RequestProcessor Quickbooks is not running currently
20261111.110909 16364 RequestProcessor Launch a new instance of Quickbooks
20261111.110911 16364 RequestProcessor Getting the IUnknown COM instance of QB
20261111.110911 16364 RequestProcessor Opening the file in the DoNotCare mode.
Ending the QuickBooks processes in Task Manager (three were running with no window) ended the wait. The log recorded an error-level line:
20261111.114957 E 21224 RequestProcessor Begin Session error = 800706be
and the Web Connector called connectionError with hresult 0x80040402 and the message "Unexpected error. Check the "qbsdklog.txt" file for possible additional information." Three seconds later it ran the next entry, started another QuickBooks, and hung again. While a start was pending, QuickBooks opened by hand did not finish opening either. Later, with QuickBooks exited and no QBW process left, both entries ran normally, and the request that had failed with 0x80040402 answered when sent again.
What to do
Do not count on the Web Connector to report a failed start: after authenticate your service may hear nothing at all. Record when each entry last called, and treat an entry that has gone silent long after authenticate as stuck rather than busy. Other entries on the same Web Connector stop calling too, so their silence may have the same cause. A 0x80040402 after such a silence can mean QuickBooks died while opening the file, and the request can be sent again. The recovery that worked was ending the Web Connector and every QuickBooks process, then starting again with no QBW process left.
Not observed
- Why the start hung. The run that worked had no
QBWprocess left beforehand, but the state before the first hang was never checked. - Whether the Web Connector ever times out by itself.
Error codes on this page
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.