QuickBooks Error Code Lookup

How to use this error-code index

Find your code in the family tables below. Every row gives the meaning in plain English, the cause you are most likely to find on a real machine, and a link to the full repair guide. Treat a code as a starting point, not a verdict: the same number can have two different causes, and the dialog wording plus the timing usually tells you which one you have.

If you have no code at all, start with How to Fix QuickBooks Errors, then return here with the exact message.

How to read a QuickBooks error dialog

A QuickBooks dialog carries more information than the number. Read four things before you dismiss it:

• The exact wording. "Could not open" points at access; "has lost integrity" points at data damage. The numbers may be similar while the fixes are not.
• The second number. In Error (-6000, -82), the suffix narrows the cause. The -77 suffix is usually a path or permission problem, while -82 and -106 usually mean hosting is switched on in the wrong place.
• When it appears. Opening, backing up, and restoring can raise the same code for different reasons. A 6000 error during a backup points at the file; during an open it often points at the network.
• Where it appears. If one workstation fails and the others work, suspect that workstation. If every workstation fails, suspect the file, the host, or the path.

Take a screenshot of the dialog, including the title bar. The exact wording matters more than memory later. Press F2 in QuickBooks to record the product version and release.

QuickBooks error codes by family

H-series: multi-user and hosting errors

Intuit documents H101, H202, H303, and H505 together because they share one root: the connection between a workstation and the computer that hosts the company file. Before you chase the network, confirm that only the server has Host Multi-User Access turned on.

6000-series: company file access errors

This family means QuickBooks reached the file but could not open it. Your data is almost always still inside. Work the error 6000 sequence in order, starting with background processes and a local copy test.

C= errors: data and component checks

C= codes rarely describe a network problem. They usually mean QuickBooks opened the file and found something inside that failed an internal check. Stop entering new transactions until you verify the file.

3xxx and 6xxx: file version and path codes

Installer and MSI codes

These come from Windows Installer, not from your books. They appear during an install, update, repair, or uninstall, and they never indicate company-file damage. Repair the Windows component named in the dialog, then retry the installer.

Payroll update and subscription codes

Intuit groups the payroll update codes under one official article because they share the same causes: the Shared Download drive, firewall filtering, the File Copy Service, digital signatures, and Windows components.

How to find your code in the qbwin.log

QuickBooks Desktop writes every open, Verify, and Rebuild to a plain-text file called QBWIN.log, which often contains the module and record the dialog leaves out. On most Windows installations it sits under your user profile at C:\Users\<your name>\AppData\Local\Intuit\QuickBooks\Log\. The AppData folder is hidden, so turn on hidden items in File Explorer or search the drive for qbwin.log.

1. Open the newest QBWIN.log in Notepad.
2. Press Ctrl + F and search for your code, or for Begin Verify to jump to the last verification.
3. Read upward from the failure: the line above usually names the list, account, or transaction involved.
4. Keep the file. If you escalate to Intuit Data Services, they will ask for it.

What to do with a code: the safe response order

Verify the fix

Run Verify Data once more and confirm it reports no problems. Then open the file without administrator rights, and from a second workstation if you share it. If either test fails, return to the family table and work the next step in that guide.