QuickBooks Error Codes List: Common Codes and What Each One Means

Last reviewed 2026-08-24

When QuickBooks throws an error code, the number itself tells you a surprising amount. This page groups the codes you are most likely to meet into families, explains what each family means, and gives you the practical fix path for each, so you can tell within seconds whether you are dealing with a settings problem, a network problem, or real damage inside your company file.

The error code tells you which layer is broken

QuickBooks errors almost always come from one of four layers: the company file itself, the connection between your computer and the file, the QuickBooks installation, or the operating system underneath it all. The code number is the fastest clue to which layer is failing. A file that opens fine on one machine but not another is a connection problem, not corruption. A file that fails to verify on every machine is damage inside the file, and no amount of reinstalling will fix that.

Before you troubleshoot anything, make a manual copy of your company file and its transaction log file to a safe location. Work on the copy. Many repair steps change the file, and you want the original untouched.

The -6000 series: file and network errors

This is the largest family, and most of these codes mean QuickBooks cannot open the company file. The suffix after the dash narrows it down.

• -6000, -77: the file is on a network path QuickBooks cannot reach, or the folder permissions block access.
• -6000, -80: the file is damaged, or QuickBooks lost the connection while the file was open.
• -6000, -82: a folder-permission or network-sharing problem on the computer hosting the file.
• -6000, -83: the file is damaged, being opened in the wrong way, or blocked by folder permissions.
• -6000, -301: often follows an interrupted update or a sudden shutdown; the file header needs repair.
• -6000, -304: not enough memory or disk space to open the file.
• -6000, -816: QuickBooks cannot open the file because it is already open in another session or was not closed cleanly.

The first-line fixes: open the file directly on the host computer rather than over the network, run the QuickBooks File Doctor tool if your edition includes it, restore a recent backup if one exists, and check that the hosting computer's shared folder gives full permissions to the user account opening the file. If the file fails on the host machine too, the problem is inside the file, not the network.

C= errors: data damage inside the file

Codes beginning with C= point to damage in the data itself: broken transaction links, a damaged list, or an unbalanced entry. Common ones include C=43 (cannot read a transaction or list), C=44 (cannot write to a transaction), C=47 (cannot find a transaction while navigating), C=88 (problem reading a data block), C=225 (cannot read a list entry), and C=342 (damaged data in a payroll or transaction group).

Run Verify from the File menu, then Utilities, to get a specific report of what QuickBooks thinks is wrong. Follow it with Rebuild. Rebuild fixes a good share of C= errors on its own. If Verify still fails after two or three Rebuild passes, stop; repeated rebuilds on a badly damaged file can make things worse. At that point the file needs professional repair, and our QuickBooks Verify and Rebuild repair service handles exactly this situation.

H-series: multi-user hosting errors

H101, H202, H303, and H505 all mean the same thing in slightly different costumes: QuickBooks cannot reach the computer hosting the company file in multi-user mode. The file is usually fine; the connection is not.

Check that hosting is turned on only on the host computer and off on workstations, that the QuickBooks Database Manager is installed and running on the host, and that the firewall on the host allows QuickBooks through. The QuickBooks File Doctor tool resolves many H-series errors automatically.

6000-301 style update and shutdown errors

An error like 6000-301 typically appears after a power loss or forced shutdown while QuickBooks had the file open. The file header records the state of the last clean close, and a sudden stop leaves that record out of date. Try opening the file with the transaction log file in the same folder, since QuickBooks can often replay the log to recover the final transactions. If that fails, restore the most recent backup and compare what is missing.

Installation and update errors

• Error 1304, 1603, 1935: installation failures, usually permissions or a missing system component. Run the QuickBooks Install Diagnostic Tool and retry as an administrator.
• Error 15215, 15222, 15240, 15243: payroll or update download failures, typically caused by antivirus software blocking the update or a broken internet Explorer setting.
• Error 1712: a previous install or uninstall left debris behind. Use the Clean Install Tool and reinstall.
• Error 3371, status code 11118: QuickBooks cannot load its licence data. This is a licensing component problem, not file damage; the QuickBooks Tool Hub has a dedicated fix for it.

-6123, 0 and -6189, 0

-6123, 0 appears when opening a file over a network or restoring a backup, and usually means a damaged backup, a blocked network connection, or antivirus interference. -6189, 0 means QuickBooks cannot open the company file in the condition it expects, often because the file was not closed properly or another user still has it open. Both are worth one attempt with the Tool Hub before assuming damage.

Unrecoverable errors and crashes

An "unrecoverable error" with a five-digit code means QuickBooks crashed mid-operation. The code identifies where, but the fix path is the same: note what action triggered it, open the sample company file to test whether the installation is healthy, and if the sample opens fine, the problem is your file. Suppress the crash by holding down the Control key while performing the triggering action, then run Verify and Rebuild.

What to check before assuming corruption

Three quick tests save hours of wrong turns. First, open the sample company file; if it opens and runs, your installation is fine. Second, copy the company file to the local hard drive and open it there; if it works locally, the problem is your network, not the file. Third, open the file as a different Windows user; if that works, it is a permissions issue. Only when all three tests still fail should you treat the file itself as damaged.

When to hand the file to us

If Verify keeps failing, if Rebuild reports unrecoverable errors, or if the file will not open at all on any machine, the data inside needs direct repair rather than more tool passes. Our QuickBooks error code repair service works directly on the damaged file, and our engineers can usually tell you within a day what is broken and what is recoverable. Keep your last good backup and the transaction log file together; between them, almost nothing is ever truly lost.