With unattended access granted, the Web Connector opens the company file itself when QuickBooks is closed, runs the session and exits it, so a closed QuickBooks is not a connection error for that app

Observed 2026-10-28 on QuickBooks Web Connector 34.0.10010.76 on the sample manufacturing company; QuickBooks edition not recorded; the Web Connector reported qbXML 17.0.

When an application was authorized to access the company file even when QuickBooks is not running, and authenticate answers with work and a company file path, the Web Connector starts QuickBooks itself if it is closed, opens the file, runs the session and closes QuickBooks again. A closed QuickBooks is then no error: connectionError is never called. When authenticate answers none, the Web Connector does not try to open QuickBooks at all.

With no QuickBooks process running, the Web Connector's log read OpenConnection() : Connecting to QuickBooks... and, 27 seconds later, Connected., Session started. It then called sendRequestXML, receiveResponseXML and closeConnection, and no QuickBooks process was left. The application's registry entry under HKCU\Software\Intuit\QBWebConnector had AuthFlags 0xF.

When the open fails, connectionError comes straight after authenticate, before any sendRequestXML. With QuickBooks closed and authenticate answering a path that does not exist, the log read (timestamps and the ticket line omitted):

Text
CheckCFNResponse() : User authenticated.
OpenConnection() : Connecting to QuickBooks...
handleAllOtherError() : QBWC1013: Error connecting to QuickBooks. Returning error message to application.
do_connectionError() : Received from connectionError() <tryAgain="done">
OpenConnection() : Error connecting to QuickBooks. Application sent back DONE. Job ending.
DoUpdateSelected() : Update completed with errors. See log (QWClog.txt) for details.

The connectionError call carried hresult 0x80040408 and the message "Could not start QuickBooks.". After done there was no getLastError and no closeConnection. An application authorized only while QuickBooks runs fails the same way, with hresult 0x8004041D.

What to do

In your own Web Connector SOAP service, do not treat a closed QuickBooks as a failure for an application authorized to run unattended. Treat connectionError as arriving right after authenticate, before any request was sent, so the work you handed out was not run and can be sent again on the next session. Match the message without regard to case: the Web Connector writes "Could not start QuickBooks."

Not observed

  • The QuickBooks edition used.
  • A company file locked by another user.
  • Whether QuickBooks shows anything on screen during an unattended open.
  • An unattended start that hung later, on the same machine, with no call to the service; the cause is not known.

Error codes on this page

QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.