Skip to content
Desktop Accounting API

Requests stop working after restoring a backup

The Web Connector looks normal and checks in, but every request from the app times out. This happens after you restore a company file backup that was made before the app was connected.

  • The app reports that QuickBooks Desktop is not responding, even though no window is open in QuickBooks, the Web Connector is running and the app’s row shows no clear error.
  • The Web Connector log (C:\ProgramData\Intuit\QBWebConnector\log\QWCLog.txt) contains QBWC1079 near the time of the request.
  • You recently restored a backup (.qbb) or replaced the company file with an older copy.

When the Web Connector adds an app, it stores a registration for that app inside the company file. Restoring a backup made before the app was added replaces the file with a version that has no such registration. The Web Connector on your computer still lists the app and remembers its password, so it keeps checking in, but QuickBooks no longer recognizes the app inside this file.

Restoring a backup made after setup does not cause this.

  1. Open the Web Connector, select the app’s row and click Remove.
  2. Close the Web Connector completely with Exit, then start it again from the Windows Start menu.
  3. Ask the app for a setup link and open it on this computer, signed in to QuickBooks as Admin with the restored company file open. The first page asks What changed? Choose I restored a QuickBooks backup, click Get a new connector file, and follow the download, access and password steps again.

Removing the old row before adding the new connector file avoids the QBWC1039 OwnerID/FileID error.

The setup page passes Connection test passed, and the app’s next request succeeds.

Contact them if requests still time out after a fresh setup. Send the time, the date of the backup you restored, the lines around QBWC1079 from the Web Connector log, and a screenshot of the Web Connector window.

For developers: the API reports these requests as QBD_QUICKBOOKS_NOT_RESPONDING, with the diagnosis cause web_connector_registration_lost.