Skip to content
Desktop Accounting API

QBWC1041 and QBWC1042: Send or receive failed

View as Markdown

During an update, the Web Connector makes a series of calls to our server: one to fetch the app’s next request, then another to hand back QuickBooks’ answer. QBWC1041 means the first kind of call failed, and QBWC1042 means the second kind failed. In both cases the Web Connector could not finish a call to our server, usually because of the network between your computer and the internet. QuickBooks and the company file are fine.

What you see

Section titled “What you see”

The Web Connector writes the error to its log, QWCLog.txt, with the reason after it. For a call that took too long, the log shows:

QBWC1041: SendRequestXML failed. Error message: The operation has timed out

QBWC1042 appears the same way with ReceiveResponseXML failed and the reason. The Web Connector waits about two minutes for each call before it gives up. The app’s request may then fail, or the app may show that the connection is not active until the next successful check-in.

Why it happens

Section titled “Why it happens”
  • The internet connection dropped or slowed down during the update.
  • A firewall, proxy or antivirus program delayed or blocked the Web Connector’s call to qbwc.desktopaccountingapi.com.
  • A VPN or a network change, such as moving between Wi-Fi networks, interrupted the call.

How to fix it

Section titled “How to fix it”
  1. Check that the computer can reach the internet. Open a web page in a browser on the same computer.
  2. In the Web Connector, select the app and click Update Selected. A one-off network hiccup clears on the next update. With Auto-Run on, the Web Connector also checks in again on its own.
  3. If the error comes back, ask your IT person whether a firewall, proxy or antivirus program inspects or slows HTTPS traffic. If one does, allow qbwc.desktopaccountingapi.com through it without inspection.
  4. If the computer uses a VPN, try an update with the VPN off, or ask your IT person to let qbwc.desktopaccountingapi.com bypass it.

How to check it worked

Section titled “How to check it worked”

Click Update Selected again. The update finishes and the app’s row shows no error in the Status column. The app’s next request succeeds.

When to contact the app’s support

Section titled “When to contact the app’s support”

Contact them if the error keeps coming back on a working internet connection. Send the time of the error, the exact message from the log, and a screenshot of the Web Connector window.

Section titled “Related pages”

For developers, see QBD_CONNECTION_ERROR and QBD_WRITE_OUTCOME_UNKNOWN.