QuickBooks Error QBWC1013: Web Connector Cannot Write Its Log File
Web Connector error QBWC1013 stops QuickBooks syncs because its log file cannot be written; our fix guide clears it in a few steps.
QBWC1013 shows up in the QuickBooks Web Connector rather than in QuickBooks itself. The connector cannot write the plain text log that records each run, so it stops the session before any data moves. Our engineers treat it as a Windows file access problem, not an accounting data problem, and it is cleared at the machine rather than in the company file.
The exact message you see
The Web Connector flags the row for your application with QBWC1013 and status text along the lines of:
QBWC1013: Error creating log file
Some releases add a prompt asking an administrator to grant permission to the log file or to move it. The wording shifts a little between connector versions. The code and the reference to the log file stay constant, so every variant points at the same fault.
What does QBWC1013 mean?
Every time the connector runs, it opens its log, appends a session header, and only then calls your application. The log normally sits in the shared program data folder for the Web Connector, on current Windows versions under C:\ProgramData\Intuit\QuickBooks Web Connector. If Windows refuses to create or append to that file, the run aborts immediately with QBWC1013.
Nothing reaches the company file, and no data is lost. The connector simply will not proceed without its record of the session, so the whole sync halts over a file it uses for housekeeping.
What triggers the error?
- Permissions on the log folder were tightened, so your Windows account has no write access.
- The connector runs on a schedule under an account with fewer rights than your desktop login.
- The log path points at a folder that was deleted, at a mapped drive whose letter changed, or at a network share that is offline.
- The log file is flagged read-only, is held open by antivirus or a backup job, or sits on a disk that is full.
- The connector was run as administrator at some point, so the log belongs to the elevated account and normal runs cannot append to it.
How do you fix it?
Work through the scenarios in order. The first one clears most cases we see.
The log folder blocks your account.
- Close the Web Connector and QuickBooks.
- Paste C:\ProgramData\Intuit\QuickBooks Web Connector into the File Explorer address bar and press Enter. ProgramData is hidden by default.
- Right-click the folder, choose Properties, and open the Security tab.
- Select Edit, pick your user account plus any account the connector's schedule uses, and tick Allow for Modify.
- Apply, and let Windows replace permissions on the contents when prompted.
- Reopen the connector and run Update Selected for your application.
The log path is no longer valid.
- Read the path in the error detail. If it names a folder that no longer exists, recreate that folder at the exact path, or return the setting to the default local folder above.
- If the path uses a drive letter, confirm the letter still maps to the same volume after a reboot. Reassigned letters are a common cause on machines that log to network storage.
- If the path is a network share, bring the share back or move the log to a local folder. The log location lives in the connector's own settings on that machine, and a local path is the reliable choice.
The log file itself is stuck.
- Right-click the log file, choose Properties, and clear the Read-only tick.
- If antivirus or a backup product holds the file open, add the connector folder to that product's exclusion list, or move its scan window away from sync times.
- Rename the existing log, for example by adding _old before the extension, and run the sync again. The log is disposable and the connector creates a fresh one. This also handles a log that grew too large or filled the disk.
An elevation mismatch owns the file.
- Close the connector, then start it once with Run as administrator.
- Run a single sync so the log is written under the elevated token, close the connector, and go back to launching it normally.
- If the fault persists, delete or rename the old log while elevated so the next normal run can create it.
A successful fix shows at once. Run Update Selected, confirm the sync completes, and check that the log file carries a new timestamp.
How do you keep it from coming back?
Keep the log on a local fixed drive and leave the folder at its default location. Grant Modify rights to every account that launches the connector, including the scheduled task account, so access survives a change of login. Pick one launch mode, elevated or normal, and stay with it. Archive or delete old log files on a schedule of your own, since they grow without limit. Keep the connector folder out of antivirus scans and backup locks, and the log will stay writable for every unattended run.