QuickBooks Error QBWC1085 -- Web Connector Cannot Write Log File

QuickBooks Web Connector stops running and reports QBWC1085 because it cannot write its QWCLOG.TXT log file; our engineers walk through resolving the lock and restoring synchronization.

QuickBooks Web Connector relies on a plain-text log file to record every synchronization pass between your company file and a third-party web service. When that log file becomes locked, corrupted, or unwritable, Web Connector halts mid-sync and throws error QBWC1085. The underlying company file and the web service itself are usually unaffected — the failure is confined to Web Connector's own logging layer.

What the error message says

The most common presentation is a Windows-style dialog titled "QuickBooks Web Connector" with text resembling:

QBWC1085: There was an error writing to the log file. The process cannot access the file because it is being used by another process.

In some installations the message continues with the full path to the log file, typically located at:

C:\Users\<username>\AppData\Local\Intuit\QuickBooks Web Connector\QWCLOG.TXT

Web Connector may then stop processing the current application's queue and refuse to proceed to the next scheduled update until the log conflict is cleared.

What the code means

QBWC1085 is an I/O exception. Web Connector attempts to open QWCLOG.TXT in read-write mode at the start of each sync cycle. If the operating system denies that handle — because another process already holds it, because the file is flagged read-only, or because the user account lacks write permissions to the AppData folder — Web Controller cannot append its session entries and aborts before attempting any data exchange.

What triggers it

Our engineers see QBWC1085 most often in these scenarios:

1. A second Web Connector instance is running. A duplicate launch — sometimes caused by a shortcut in both the Startup folder and the Task Scheduler — holds QWCLOG.TXT open. The second instance cannot acquire the handle and reports the error.
2. Antivirus or backup software is scanning the file. Real-time scanning engines momentarily lock files while inspecting them. If that lock coincides with a Web Connector sync, the write fails.
3. The QWCLOG.TXT file is corrupted. An improper shutdown, a Windows update reboot, or a prior crash can leave the log file in a state where Web Connector cannot parse or append to it.
4. Folder permissions were changed. A profile migration, a domain policy update, or a manual folder move can strip write access from the AppData path.
5. Cloud sync software (OneDrive, Dropbox) is redirecting AppData. When AppData is redirected to a synced cloud folder, file-locking conflicts occur frequently.

How to fix it

Work through these scenarios in order — the first one resolves the majority of cases we encounter.

Scenario 1 — A second Web Connector instance is running

1. Close QuickBooks Web Connector completely (right-click its system tray icon and select Exit).
2. Press Ctrl+Shift+Esc to open Task Manager. On the Details tab, look for any lingering QBWebConnector.exe processes. End each one.
3. Check the Windows Startup folder (%AppData%\Microsoft\Windows\Start Menu\Programs\Startup) and Task Scheduler Library for duplicate Web Connector entries. Remove the extra entry so only one launch point remains.
4. Relaunch Web Connector and run an update.

Scenario 2 — Antivirus or backup software locked the file

1. Temporarily disable real-time scanning on the folder C:\Users\<username>\AppData\Local\Intuit\QuickBooks Web Connector.
2. Run a Web Connector update to confirm the error clears.
3. If it does, add an exclusion for that folder in your antivirus or backup product so future scans skip QWCLOG.TXT.

Scenario 3 — The log file is corrupted

1. Close Web Connector and verify no processes remain in Task Manager.
2. Navigate to C:\Users\<username>\AppData\Local\Intuit\QuickBooks Web Connector.
3. Rename QWCLOG.TXT to QWCLOG.OLD.
4. Relaunch Web Connector. It creates a fresh log file automatically on the next sync.

Scenario 4 — Folder permissions are wrong

1. Right-click the QuickBooks Web Connector folder under AppData\Local\Intuit and select Properties.
2. On the Security tab, confirm that the current Windows user has Full Control or at least Modify permission.
3. If the user is missing or denied write access, click Edit, add the user, and grant Modify permission. Apply and close.
4. Relaunch Web Connector.

Scenario 5 — Cloud sync is redirecting AppData

1. Check whether a OneDrive, Dropbox, or Google Drive icon appears on the AppData folder path.
2. If AppData is being synced, exclude the Intuit\QuickBooks Web Connector folder from sync, or move the sync redirect so AppData remains local.
3. Rename the existing QWCLOG.TXT as described in Scenario 3, then relaunch Web Connector.

How to prevent it recurring

Keep only one Web Connector launch point — either a Startup shortcut or a scheduled task, not both. Add the Web Connector AppData folder to your antivirus exclusion list. If you use folder redirection or roaming profiles, ensure the Web Connector log path stays on a local drive. Periodically close and reopen Web Connector after Windows updates, since forced reboots during an active sync are a frequent source of log file corruption.