Complete QuickBooks Error Codes Reference

Understanding QuickBooks Error Codes

Error codes are the software's way of telling you something specific. QuickBooks does not throw random numbers at you -- each error code belongs to a category, and each category points to a particular type of problem. Understanding the pattern behind the codes is more valuable than memorizing individual fixes, because it lets you diagnose new errors you have never seen before.

This reference covers every major category of QuickBooks Desktop error codes. For each category, you will find what the codes mean, what causes them, how severe they are, and whether self-resolution is realistic or whether the situation calls for professional intervention.

The -6000 Series: Company File Access Errors

The -6000 series is the most common category of QuickBooks errors, and arguably the most frustrating. These errors occur when QuickBooks cannot open or access the company file. The full error typically appears as "Error -6XXX, -YYY" -- two negative numbers separated by a comma.

Common -6000 Errors

• -6000, -82 -- QuickBooks cannot open the company file. Often caused by a damaged file, incorrect file path, or hosting configuration issue.
• -6000, -301 -- The company file is located on a drive or folder where QuickBooks lacks sufficient permissions.
• -6000, -305 -- Similar to -301 but typically related to the network path or mapped drive losing connection.
• -6073, -99001 -- Another user is already logged into the file in single-user mode, or the file is locked by another process.
• -6123, 0 -- QuickBooks cannot connect to the company file on the network. The Database Server Manager may not be running on the host machine.
• -6144, -82 -- QuickBooks encountered an error while trying to access the company file. Often seen after a failed Windows update or QuickBooks update.
• -6147, 0 -- QuickBooks cannot create a copy of the company file for backup purposes. Usually a permissions or disk space issue.
• -6150, -1006 -- The company file cannot be created or the existing file is damaged beyond the point where QuickBooks can open it.
• -6176, -6190 -- The host machine cannot share the company file. The QuickBooks Database Server Manager needs attention.
• -6189, -816 -- The company file is being accessed by another QuickBooks process, or the .TLG (transaction log) file is damaged.
• -6190, -816 -- One of the most common network errors. Usually means the file was not closed properly and a lock persists.

What Causes -6000 Errors

The -6000 series almost always relates to one of four issues: file path problems (the file is not where QuickBooks expects it), permissions problems (QuickBooks or the Windows user lacks access), hosting problems (Database Server Manager misconfiguration), or file-level damage (the .QBW or .TLG file has structural issues).

Severity and Resolution

Most -6000 errors are resolvable without professional help -- they are often environmental rather than corruption-related. Start with the basics: verify the file path is correct, check that the QuickBooks Database Server Manager is running on the host, ensure the Windows user has full read/write permissions to the folder, and make sure only one machine is set to "Host Multi-User Access."

The exception is when a -6000 error persists after all environmental factors have been addressed. If the file simply refuses to open no matter what you try, the .QBW file itself may be damaged. That situation typically requires professional repair.

C= Errors: Internal Data Integrity

C= errors (pronounced "C-equals") are QuickBooks' internal data integrity codes. They appear as "C=" followed by a number -- for example, C=47, C=224, C=343, or C=9000. These are among the most serious errors in QuickBooks because they indicate structural problems inside the company file.

Common C= Errors

• C=47 -- A data mismatch in the file's internal structures. Often related to list corruption (customers, vendors, items, or accounts).
• C=224 -- Indicates a problem with the file's B-tree structures, which are used to organize and retrieve data. This one is common after power failures.
• C=343 -- A transaction log integrity error. The internal record of changes has become inconsistent with the rest of the file's data.
• C=387 -- Related to data allocation within the file. The internal space management has become inconsistent.
• C=9000 -- A general catchall for structural issues that do not fit other categories. Often the most difficult to diagnose.

What Causes C= Errors

C= errors are caused by events that interrupt or corrupt the file's internal structures. The usual suspects are: power failures during write operations, network drops during multi-user access, hard drive failures, bad RAM corrupting data in transit, and files that have grown very large over many years of use.

Severity and Resolution

C= errors are high severity. They represent actual structural damage to the data inside your file, not environmental issues you can fix by adjusting settings or permissions.

If you have a clean backup from before the error started appearing, restoring that backup is the fastest resolution. If you do not have a clean backup, or if the backup is too old and you cannot afford to lose the intervening data, professional repair is the standard path.

One critical note: if you have already run Verify and Rebuild and the C= error persists, that is a strong signal that the damage is beyond what the built-in tools can address. If you have not yet run those tools, be cautious -- on certain C= errors (particularly C=343), running Rebuild can actually worsen the damage by reorganizing data around the corrupted area.

H-Series Errors: Multi-User and Network

H-series errors (H101, H202, H303, H505) appear when QuickBooks is having trouble communicating between workstations and the host computer in a multi-user environment. The "H" stands for "hosting."

Common H-Series Errors

• H101 -- The workstation cannot reach the host computer. Typically a firewall, DNS, or network configuration issue.
• H202 -- QuickBooks can find the host computer but cannot communicate with the QuickBooks Database Server Manager (QBDBSM) on that machine. This is the most common H-series error.
• H303 -- The host computer's network name cannot be resolved. The workstation is trying to connect but cannot find the server by name.
• H505 -- A more complex networking issue. QuickBooks is finding multiple hosts for the same file, or there is a hosting conflict between machines.

What Causes H-Series Errors

Every H-series error traces back to network communication. Common causes include: the QuickBooks Database Server Manager not running on the host, Windows Firewall blocking QuickBooks ports (8019, 56728, 55378-55382), incorrect hosting configuration (multiple machines set to "Host Multi-User Access"), DNS resolution failures, and network infrastructure problems (switch failures, VLAN misconfigurations, IP address conflicts).

Severity and Resolution

H-series errors are moderate severity in terms of data risk -- they do not indicate file corruption. However, they are high severity in terms of business disruption because they prevent users from accessing the file.

These errors are almost always resolvable without professional help. The systematic approach is: verify Database Server Manager is running on the host, check that only one machine is hosting, configure firewall exceptions for QuickBooks, verify network connectivity between machines using ping and the computer name (not IP address), and restart the QuickBooks services.

If H-series errors appear suddenly in an environment that was previously working, look for recent changes: Windows updates, new firewall rules, network hardware changes, or a new machine added to the network.

OL and OLSU Errors: Banking and Online Services

OL (Online) and OLSU (Online Setup) errors occur during bank feed connections, online banking transactions, and web connector operations. These errors appear as "OL-" or "OLSU-" followed by a number.

Common OL/OLSU Errors

• OL-301 -- QuickBooks cannot connect to the bank. The bank may have changed its connection method or credentials are incorrect.
• OL-332 -- The bank rejected the connection request. Often caused by the bank migrating to a new online banking platform.
• OL-393 -- A timeout error. QuickBooks could not complete the bank communication in the expected time.
• OLSU-1013 -- The bank's connection information in QuickBooks is outdated and needs to be refreshed.
• OLSU-1024 -- QuickBooks is unable to validate the financial institution's certificate. May indicate a TLS/SSL compatibility issue.

What Causes OL/OLSU Errors

These errors are almost always caused by factors external to your company file: banks changing their web connect endpoints, expired authentication tokens, TLS version incompatibility (older QuickBooks versions may not support TLS 1.2), internet connectivity issues, or Intuit's own online services experiencing downtime.

Severity and Resolution

Low severity for data integrity -- these errors do not affect your company file at all. They only affect online connectivity features. Resolution usually involves updating QuickBooks to the latest release, re-entering bank credentials, deactivating and reactivating the bank feed, or waiting for the bank or Intuit to resolve a service disruption.

If an OL error persists, check the Intuit status page and your bank's online banking portal directly. Banks frequently change their QuickBooks connectivity without much notice, and Intuit maintains a list of banks that have switched connection methods.

15xxx Series: Update Errors

The 15000-series errors (15101, 15102, 15103, 15106, 15215, 15227, 15241, 15271) occur when QuickBooks cannot download or install updates -- either payroll updates, QuickBooks program updates, or both.

Common 15xxx Errors

• 15101 -- The update download failed. Usually a permissions or connectivity issue.
• 15102 -- The QuickBooks update program (QBUpdate.exe) could not access the file it needs to update.
• 15103 -- The update cannot be saved to the specified location.
• 15106 -- The update download failed because the destination folder cannot be accessed.
• 15215 -- A digital signature verification failure. The downloaded update could not be validated.
• 15227 -- Related to a damaged Windows component or corrupted QuickBooks installation.
• 15241 -- The payroll update could not be completed because a required component is not working properly.
• 15271 -- QuickBooks could not verify the digital signature of the downloaded update.

What Causes 15xxx Errors

These errors trace to three areas: internet connectivity and firewall settings blocking the update servers, file system permissions preventing QuickBooks from writing to its program directory, or a corrupted QuickBooks installation where core components need repair.

Severity and Resolution

Low severity for data integrity. Your company file is unaffected by update errors. The risk is that running outdated payroll tables can cause calculation errors, and missing security patches can leave the system exposed.

Resolution typically involves running QuickBooks as administrator, temporarily disabling antivirus/firewall software during the update, resetting the QuickBooks update settings, or in stubborn cases, using the QuickBooks Install Diagnostic Tool from Intuit's Tool Hub. If the QuickBooks installation itself is corrupted, a clean reinstall resolves the update errors permanently.

Error 3371: License and Registration

Error 3371 (Status Code -11118) appears when QuickBooks cannot read the license data from the EntitlementDataStore.ecml file. The full message usually reads: "Could not initialize license properties."

What Causes Error 3371

This error is caused by damage to the license validation file, which lives in the Windows ProgramData folder. Common triggers are: moving QuickBooks to a new computer without proper deactivation, upgrading Windows, restoring a system image, hard drive replacement, or changes to the system's hardware ID.

Severity and Resolution

No data risk whatsoever -- this error has nothing to do with your company file. It is purely a licensing and registration issue.

Resolution involves deleting or renaming the EntitlementDataStore.ecml file so QuickBooks regenerates it. The file is located at C:\ProgramData\Intuit\Entitlement Client\v8\ (the version number may vary). After deleting it, open QuickBooks and re-enter your license and product numbers. If you do not have your license number, it can be found on the original purchase confirmation email or in your Intuit account.

Error 80070057: The Parameter Is Incorrect

Error 80070057 is a Windows-level error that QuickBooks surfaces when the operating system reports that a file operation failed with "the parameter is incorrect." Despite being a Windows error code, it almost always appears in a QuickBooks context when working with company files.

What Causes Error 80070057

The most common cause is the company file name or path containing characters that Windows cannot process correctly -- special characters, excessively long file names, or paths that exceed the Windows MAX_PATH limit (260 characters). Other causes include disk errors on the drive hosting the file, damaged Windows user profile, or incompatible regional settings (particularly date format settings that conflict with QuickBooks' expectations).

Severity and Resolution

Moderate severity. The error itself does not corrupt your data, but the underlying cause (particularly disk errors) might be doing damage. Resolution involves renaming the file to remove special characters, moving it to a shorter path (like C:\QB\), running chkdsk on the host drive, or creating a new Windows user profile. If the error appears during backup operations, the issue is usually with the destination path rather than the source file.

Unrecoverable Errors

Unrecoverable errors are the most ominous-sounding category in QuickBooks. They appear in a dialog box that reads "QuickBooks has encountered a problem and needs to close" followed by a multi-digit error code in the format XXXXX YYYYY (five digits, space, five digits).

What They Mean

Despite the alarming name, "unrecoverable" does not mean your data is lost. It means QuickBooks encountered a condition it could not handle and had to shut down. Think of it as a controlled crash -- QuickBooks detected something wrong and stopped rather than continuing and potentially causing damage.

Common Patterns

• 00000 XXXXX -- Usually related to display or UI rendering issues. Low severity.
• XXXXX 00000 -- Often related to damaged preference files or corrupted QuickBooks installation.
• 19119 XXXXX -- Printing-related unrecoverable errors. Triggered by PDF driver conflicts.
• 14982 XXXXX -- Often triggered by a specific transaction or list entry that contains corrupted data.

Severity and Resolution

Variable severity. Some unrecoverable errors are benign (display glitches, PDF driver conflicts) and are resolved by updating QuickBooks, resetting preferences, or fixing the PDF converter. Others -- particularly those triggered by opening a specific transaction or running a specific report -- can indicate data corruption that requires attention.

If an unrecoverable error is reproducible (it happens every time you do the same thing), note the exact error code and the action that triggers it. If it happens randomly, it is more likely an environmental issue. For the data-corruption variety, you may need to work with a specialist who can identify and repair the specific corrupted record.

Severity Quick Reference

Understanding the severity of each error category helps you prioritize your response:

Critical -- Act Immediately

• C= errors -- Structural file damage. Stop using the file, secure a copy, assess backups.
• -6150, -1006 -- File cannot be created or opened due to severe damage.

High -- Address Promptly

• -6000 series (persistent) -- If environmental fixes do not resolve the error, the file may be damaged.
• Unrecoverable errors (repeatable) -- When the same action consistently triggers the crash, a data issue is likely.
• -6189, -816 -- Transaction log damage can compound if ignored.

Moderate -- Resolve When Convenient

• H-series -- Business disruption but no data risk. Fix the network configuration.
• 80070057 -- Investigate the underlying cause but data is not in immediate danger.
• -6000 series (first occurrence) -- Often resolves with basic environmental troubleshooting.

Low -- Informational

• 15xxx series -- Update failures. No data risk.
• 3371 -- Licensing issue only.
• OL/OLSU -- Bank connectivity. No file impact.
• Unrecoverable (random/one-time) -- Often environmental.

A Systematic Approach to Any Error

Regardless of which error code you are facing, the diagnostic process follows the same framework:

1. Identify the Category

Look at the error code format. Is it -6XXX? C=? H-series? 15xxx? The category tells you immediately what area of QuickBooks is affected and narrows your troubleshooting.

2. Determine Reproducibility

Can you trigger the error consistently by performing the same action? Or does it appear randomly? Reproducible errors are easier to diagnose because they point to a specific cause. Random errors often indicate environmental issues (hardware, network instability).

3. Check the Timeline

When did the error first appear? What changed? Windows update, new user, network change, power outage, large data import? The triggering event often reveals the cause.

4. Assess Data Risk

Is this a data integrity error (C=, persistent -6000, data-related unrecoverable) or an environmental/connectivity error (H-series, OL, 15xxx, 3371)? If there is any data risk, stop using the file and secure a copy before attempting fixes.

5. Start Simple

For environmental errors, work through the basic fixes first: restart QuickBooks, restart the computer, verify file permissions, check network connectivity. Many errors resolve with these steps.

6. Know When to Stop

If you have worked through the standard troubleshooting steps and the error persists -- especially for C= errors and persistent -6000 errors -- additional attempts at self-repair can make the situation worse. This is the point where professional help typically produces better outcomes than continued DIY troubleshooting. Data repair specialists have tools and techniques that go well beyond what the standard QuickBooks utilities offer, and they work with corrupted files daily.

Keeping a Clean Error History

One practice that pays dividends over time is maintaining a log of errors your file has experienced. Note the date, the error code, what you were doing when it appeared, and how it was resolved. Patterns emerge -- recurring errors in the same category often point to an underlying issue (oversized file, failing hardware, unreliable network) that, once addressed, eliminates the errors entirely.

QuickBooks error codes are not random noise. They are diagnostic information. Understanding the system behind the codes puts you in a position to make informed decisions about your data, rather than guessing at solutions or panicking at an unfamiliar number.