Every QuickBooks Web Connector Error Code, Fixed (And How to Never See Them Again)

This is the complete guide to QuickBooks Web Connector errors — every QBWC code that actually shows up in the wild, the real fix for each, and no phone-number bait. Use the table to jump to your code.

One thing to know up front, because it explains the whole list: the Web Connector is a SOAP polling agent Intuit built in 2002 and has barely touched since. Its errors fall into four families — its own log file (1085, 1033), app authorization state (1039, 1011, 1012, 1040), reaching QuickBooks (1013, 1007, and friends), and talking to your web service (1042, 1048, "application requested to abort"). All four are fragile state the connector maintains and routinely loses. That's why the same codes keep coming back after you fix them.

Quick index

QBWC1085: There was a problem with the log file

The most common Web Connector error, full stop. The connector corrupts its own QWCLOG.TXT — typically after a crash or unclean shutdown — then fails on the corrupt log at every launch until you intervene.

Fix: Exit the Web Connector, rename C:\ProgramData\Intuit\QBWebConnector\log\QWCLOG.TXT to QWCLOG.OLD, restart. Full walkthrough, including the permissions variant and why it recurs on reboots: the dedicated QBWC1085 page.

QBWC1039: unique OwnerID/FileID pair value required

The Web Connector stamps each company file with an OwnerID the first time an app connects. QBWC1039 (in its several message variants — "there was a problem adding the application," "this application does not have permission to access this QuickBooks company data file," "unique OwnerID/FileID pair value required") means that stamp and reality have diverged: the company file was moved, renamed, restored from backup, or the app was removed and re-added.

Fix, by variant:

• App can't be re-added / OwnerID pair error: the old stamp is still in the file. Download Intuit's CP3 Tool, open your .qwc file with it, and remove the OwnerID stamp; then add the app again in the Web Connector.
• No permission to access the file: in QuickBooks, Edit → Preferences → Integrated Applications → Company Preferences, remove the stale entry for your app, then re-run the sync and grant access when prompted (log in as the QuickBooks admin, in single-user mode).
• File was moved or renamed: point the app's .qwc at the new path, or move the file back.

QBWC1013: error connecting, or could not start QuickBooks

The connector couldn't reach a running QuickBooks. Usual causes, in order of likelihood:

1. QuickBooks isn't open and can't auto-open. Either keep QuickBooks running with the right company file open, or authorize the app to connect when QuickBooks is closed (Integrated Applications preferences) — noting that auto-open requires the file path stored in the .qwc/app authorization to still be correct.
2. Elevation mismatch. QuickBooks running as admin and QBWC as a normal user (or vice versa) blocks the COM connection. Run both the same way.
3. The wrong company file is open. The connector will refuse rather than write into the wrong file — check which file the sync expects.
4. A modal dialog is blocking QuickBooks. Dismiss every dialog on screen.

If this happens on a server where nobody is logged in: that's not a bug, it's the architecture — see Can You Run the Web Connector as a Windows Service?

QBWC1012: authentication failed

The password the Web Connector has saved for your web service no longer matches. Get the current password from the integration vendor's dashboard (most regenerate it there), clear the password field in the Web Connector, re-enter it, press Tab so it saves, and run the sync. If it fails again immediately, the saved credential store is stale — remove the app from QBWC and re-add the .qwc fresh.

QBWC1011: application not found in the registry

The connector's own registration of your app is broken — its internal record no longer matches the .qwc data. Remove the application from the Web Connector, then re-add it from the original .qwc file (re-download it from your integration vendor if you don't have it). You'll re-enter the password and re-authorize in QuickBooks.

QBWC1005 / QBWC1006: the Web Connector failed to run

Startup failures of QBWC itself, almost always environmental: a damaged .NET Framework or a broken install. Repair .NET (Windows Settings → Apps, or Intuit's Component Repair Tool), then uninstall and reinstall the current Web Connector and re-add your .qwc files.

QBWC1007: error connecting to QuickBooks

A near-sibling of QBWC1013, usually transient: QuickBooks was mid-launch, mid-update, or showing a dialog when the poll fired. Dismiss dialogs, let QuickBooks finish starting, run again. If persistent, work the QBWC1013 list above.

QBWC1033: failed to initialize QWCLog

The connector can't create or write its log file — a permissions problem on C:\ProgramData\Intuit\QBWebConnector\log, most common on servers with hardened ACLs or after a restore. Grant the account running QBWC modify rights on that folder (or run QBWC as administrator, and then — per the elevation rule — QuickBooks as administrator too).

QBWC1040: password problems

The saved web-service password is missing or malformed. Same treatment as QBWC1012: re-enter, Tab to save, re-add the app if it won't stick.

QBWC1042: ReceiveResponseXML failed / operation timed out

The other side of the conversation — your integration's web service — took too long or returned a fault while processing. Common with large syncs and big company files. Reduce the batch size in the integration's settings if it has one, lengthen the auto-run interval so runs never overlap, and run the sync on the machine hosting the company file rather than across a network share. If it's chronic, the fix belongs to the integration vendor's server, not your machine.

QBWC1048: could not verify the web application server certificate

The connector can't validate the HTTPS certificate of the web service it's polling. Check the machine's system clock first (a skewed clock invalidates every certificate), then Windows Updates for root-certificate updates, then TLS protocol settings if the box is old. If it broke for everyone on the same day, it's the vendor's certificate — or Intuit's; a code-signing incident on Intuit's side has previously broken Web Connector integrations everywhere at once.

"Application requested to abort"

Not a QBWC code but the message everyone remembers. It means the web service told the connector to stop — usually because the service hit an error processing your data, and sometimes en masse after QuickBooks version upgrades. Check the sync log in your integration's dashboard for the real error (a bad record, an unmapped field), fix that, and re-run. If it started right after a QuickBooks upgrade, update both the Web Connector and the integration's connector component to their newest versions.

Why this page will stay bookmarked (unless you fix the cause)

Every fix above works. None of them lasts, because each one repairs a piece of state the Web Connector will lose again — the log it corrupts, the registrations it breaks, the sessions it can't survive. Intuit's development effort left QuickBooks Desktop's plumbing years ago; the connector you have today is the best it will ever be.

LedgerCrossing is the permanent fix for integrations you control: a local Windows tray app that does the Web Connector's job over a reliable HTTP/qbXML pass-through. Same qbXML, sent as a plain HTTP POST by anything that can make a web request — none of the SOAP polling architecture that produces this page. Auto-starts, runs unattended, keeps your data on your network, and writes logs designed to be read by humans. Off-site systems can reach it too — self-managed tunnel (free) or the built-in Remote relay ($39/mo). (If your sync belongs to an off-the-shelf vendor app, it can't be repointed — the fixes above are your toolkit, and your vendor is the one to push.)

$299 one-time, per machine, unlimited company files. No subscription. Pro, Premier, and Enterprise. 30-day money-back guarantee.

Buy LedgerCrossing — $299 →

Related guides

• QuickBooks Web Connector Keeps Crashing: Every Fix, and the Permanent One
• QBWC1085: There Was a Problem With the Log File
• Can You Run the Web Connector as a Windows Service?
• QuickBooks Web Connector Alternatives in 2026

QuickBooks is a registered trademark of Intuit Inc. LedgerCrossing is an independent product for QuickBooks Desktop and is not affiliated with or endorsed by Intuit.