LedgerCrossingLedgerCrossing Buy LedgerCrossing — $299

QBWC1085: "There Was a Problem With the Log File" — the 2-Minute Fix

You opened the Web Connector (or logged into Windows) and got:

QBWC1085: There was a problem with the log file. QuickBooks Web Connector will continue without the log file.

or the uglier sibling:

QBWC1085: Unexpected error. Check the QBWebConnector.log file.

Here's the fix. It takes about two minutes, and syncs usually run fine afterward.

Fix it right now

The Web Connector's log file (QWCLOG.TXT) is corrupted, and QBWC can't get past it. Clear it:

  1. Exit the Web Connector completely. Right-click its icon in the system tray (bottom-right, near the clock — click the ^ arrow if it's hidden) and choose Exit. Closing the window isn't enough; it keeps running in the tray.
  2. Open the log folder. Paste this into the File Explorer address bar and press Enter: C:\ProgramData\Intuit\QBWebConnector\log (You can't browse to it casually — ProgramData is a hidden folder.)
  3. Rename QWCLOG.TXT to QWCLOG.OLD. Renaming beats deleting: you keep the old log in case an integration vendor asks for it, and the effect is identical — QBWC creates a fresh one.
    • If Windows says the file is in use, the Web Connector is still running. Open Task Manager, end QBWebConnector.exe, and rename again.
  4. Start the Web Connector again (Start menu → Web Connector). It recreates a clean QWCLOG.TXT and the error is gone.
  5. Run your sync to confirm.

If it comes back immediately (permissions variant)

If a fresh launch throws QBWC1085 again right away — common on servers and locked-down machines — the connector can't write to that log folder at all:

  1. Right-click the log folder → Properties → Security.
  2. Give the Windows account that runs the Web Connector Modify permission on the folder.
  3. If you run the Web Connector as administrator, run QuickBooks as administrator too — a mismatch in elevation between the two causes its own set of failures.

Why it keeps happening

Notice the error usually appears after a reboot, a crash, or a forced shutdown. That's not a coincidence — it's the mechanism:

The Web Connector writes to QWCLOG.TXT constantly while it runs. When the process dies mid-write — because it crashed, because Windows Update rebooted the server at 3 a.m., because someone shut down without exiting the tray app — the log is left truncated mid-entry, and the next launch chokes on it. The connector has no recovery logic: it doesn't detect the corruption, doesn't rotate the file, doesn't start a new one. It just fails and waits for you.

And since the Web Connector crashes a lot, and servers reboot on patch schedules, QBWC1085 isn't an error so much as a subscription. Every unclean shutdown is a ticket to this page. The 2002-era architecture guarantees it, and Intuit stopped meaningfully updating the Web Connector years ago — this behavior is permanent.

The permanent fix

LedgerCrossing retires the Web Connector entirely: a lightweight Windows system-tray app that gives your integration a reliable, local HTTP/qbXML pass-through to QuickBooks Desktop. It's the same qbXML you send today, delivered over a plain HTTP POST — no fragile SOAP polling agent, and no QWCLOG.TXT, in the middle. It works with anything that can make a web request; if you or your developer control the integration code, switching is a small one-time change. (Off-the-shelf apps that sync through the Web Connector are controlled by their vendors — LedgerCrossing can't be swapped in underneath those.)

If you've fixed QBWC1085 more than once, you've already spent more than $299 of your time on it.

Buy LedgerCrossing — $299 →

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.