QuickBooks Error Codes — What Every Code Means and What to Do First
Seeing a QuickBooks error and not sure where to start? This independent reference guide covers every major error code across six categories — banking and connection errors, company file errors, network and multi-user errors, installation errors, payroll errors, and Windows-triggered errors — with plain-language explanations and a documented first step for each code.
QuickBooks error codes fall into six categories. 15XXX codes indicate banking connection or payroll service errors. 6XXX codes indicate company file access or data problems. HXXX codes — H101, H202, H303, H505 — indicate network and multi-user connection problems. 1XXX codes indicate Windows installation or update errors. 17XXX codes indicate payroll subscription or tax table errors. 80XXX codes indicate company file corruption or Windows component failures. Error 3371 is a licence load failure — increasingly triggered by Windows updates in 2025 and 2026. The first step for most QuickBooks errors is the same: update QuickBooks, then run QuickBooks Tool Hub from Intuit's website. These two actions resolve the majority of common errors before any deeper troubleshooting is needed.
What QuickBooks Error Codes Actually Tell You — and What They Do Not
QuickBooks error codes are generated from three different sources simultaneously — the QuickBooks software on your computer, Intuit's own servers, and the bank or payroll provider's infrastructure. This is why the same error code can appear for genuinely different reasons depending on your version, your operating system, and which bank or service is involved. A 15XXX banking error on one user's system may be caused by an outdated QuickBooks version while the same code on another user's system is caused by a bank server maintenance window — and the correct first step is different in each case.
The single most useful thing to check before any error-specific troubleshooting is whether QuickBooks is fully up to date. A significant proportion of recurring QuickBooks errors — particularly 15XXX banking errors and 6XXX file errors — are directly caused by running a version of QuickBooks that predates a fix already released by Intuit.
The second most useful action is downloading and running the QuickBooks Tool Hub. This official Intuit diagnostic tool automatically identifies and repairs the most common categories of error — company file problems, network issues, installation failures, and program crashes — and it should be run before attempting any manual fix. Download it from quickbooks.intuit.com — do not download it from any other source.
Check for Windows update conflicts first — 2025 and 2026
Windows cumulative updates released in 2025 and 2026 — particularly updates KB5051987 and subsequent releases — have triggered a wave of QuickBooks Desktop errors including Error 3371 licence failures, company files that will not open, frozen screens in QuickBooks, and WDDM service not running errors. If your QuickBooks error appeared immediately after a Windows update, check Intuit's status page before attempting any other troubleshooting — many of these are known issues with documented resolution steps.
Back up before any repair attempt
Before running any repair tool, using File Doctor, rebuilding data, or attempting any fix that modifies your company file — create a backup. Go to File → Back Up Company → Create Local Backup and save to an external drive or cloud folder. This is non-negotiable. Some repair operations — particularly Rebuild Data — modify the company file and cannot be fully reversed if they produce an unexpected result.
Desktop 2023 and earlier — payroll errors are now permanent
If you are running QuickBooks Desktop 2023 or an earlier version, payroll tax tables have been permanently discontinued as of May 31, 2026. Any payroll-related error on these versions — PS038, 17000, 17337, or 17500 — cannot be fully resolved on that version. The resolution is migration to QuickBooks Desktop 2024 or QuickBooks Online. Payroll errors on Desktop 2024 are still resolvable through normal troubleshooting until September 2027.
15XXX Series — Bank Feed and Connection Errors
Banking connection errors indicate a breakdown between QuickBooks and your financial institution's servers. Most are caused by outdated QuickBooks versions, expired bank authorisations, or bank-side authentication changes. The majority resolve without needing to modify your company file.
Error 15103 — Bank Connection Requires Re-Authorisation
CommonWhat it means
Your bank has updated its security settings or the authorisation token QuickBooks stored for your bank connection has expired. QuickBooks can no longer authenticate with the bank using the credentials currently stored. This often follows a bank security update that happened in the background without any notification to you.
Update QuickBooks via Help → Update QuickBooks Desktop → Update Now. Then go to Banking → Bank Feeds → Bank Feed Centre, disconnect the affected account, and reconnect using your current bank login credentials. Re-enter credentials rather than relying on stored ones.
Error 15106 — Cannot Verify Bank Connection
ModerateWhat it means
QuickBooks cannot verify the connection to your bank because of an outdated software version or a corrupted banking cache. The cached connection data QuickBooks stores for bank feed sessions has become stale or internally inconsistent. This can also be caused by incomplete previous bank feed sessions that did not close cleanly.
Update QuickBooks. Then go to Banking → Banking → and clear the banking cache from the settings. Restart QuickBooks and reconnect the bank feed.
Error 15215 — Bank Temporarily Unavailable
CommonWhat it means
QuickBooks attempted to contact your bank's server and received no response. This is almost always a temporary bank-side condition — scheduled maintenance, unexpected server load, or a brief outage. Your QuickBooks installation and company file are unaffected. This is one of the few QuickBooks errors where the correct first step is to do nothing immediately.
Wait one to two hours and retry. Check your bank's website directly for any maintenance or service notifications. Do not modify any settings in QuickBooks while waiting — the issue is on the bank's side.
Error 15222 — Firewall or SSL Certificate Blocking Connection
ModerateWhat it means
QuickBooks is being prevented from reaching your bank by your computer's firewall, antivirus software, or an SSL certificate configuration issue. Increasingly reported in 2025 and 2026 following Windows security updates that tightened TLS and SSL settings in ways that affect QuickBooks's outbound banking connections. Also commonly caused by VPN software intercepting QuickBooks's connection attempts.
Temporarily disable your VPN and retry. If that resolves it, your VPN configuration needs to allow QuickBooks outbound traffic. Also add QuickBooks as a permitted application in your firewall and antivirus settings. Check that Windows date and time settings are correct — incorrect system time causes SSL certificate validation failures.
Error 15240 — Payroll Service Temporarily Unavailable
ModerateWhat it means
QuickBooks attempted to contact Intuit's payroll servers and received no response or a maintenance response. Intuit's payroll infrastructure undergoes maintenance windows — particularly overnight and on weekends — that can produce this error for users who attempt payroll updates outside of business hours. Also caused by an expired payroll subscription or a lapsed payment method on the Intuit account.
Check Intuit's system status page at status.intuit.com for any reported payroll service outages. Verify your payroll subscription is active in your Intuit account. Wait 30 to 60 minutes and retry the payroll update.
Error 15243 — Bank Credentials Rejected
CommonWhat it means
QuickBooks transmitted credentials to your bank and the bank rejected them. Most commonly caused by a recent bank password change that has not been updated in QuickBooks. Also caused by a bank switching to multi-factor authentication — requiring a one-time code or security question response that QuickBooks cannot provide automatically. Some banks now require OAuth-based re-authorisation rather than stored username and password.
Log into your bank's website directly using a browser to confirm your current credentials are working. If they work on the website, return to QuickBooks and disconnect then reconnect the bank feed using your verified current credentials.
Error 15271 — Payroll Data Corruption
Less Common — SeriousWhat it means
QuickBooks has detected internal corruption in its payroll data files or tax table files. This can prevent payroll updates from downloading, prevent payroll from processing, or cause payroll figures to calculate incorrectly. Causes include an interrupted payroll update download, a system shutdown during a payroll tax table write, or underlying data file damage that has spread to payroll records.
Back up immediately before doing anything else. Run QuickBooks File Doctor. Then run File → Utilities → Verify Data — if errors are found, run File → Utilities → Rebuild Data. Attempt to download the latest payroll tax tables after rebuilding. If corruption persists, restore from the most recent clean backup.
Error 15217 — Cannot Verify Digital Signature of Downloaded Files
Increasing — Linked to Windows Updates 2025-2026What it means
QuickBooks cannot verify the digital signature of files being downloaded during an update — most commonly a payroll update or QuickBooks software update. This error has increased significantly following Windows updates in 2025 and 2026 that modified how Windows validates digital signatures. Often related to Internet Explorer security settings that QuickBooks Desktop still uses for some update communications, even on systems where Internet Explorer itself is not actively used.
Open Internet Explorer security settings through Control Panel → Internet Options → Advanced tab. Ensure TLS 1.2 is enabled. Verify that the Windows date and time are correct. Add Intuit's update URLs to Internet Explorer's trusted sites. Run QuickBooks as Administrator and retry the update.
Error 10000 — Generic Banking Connection Failure
ModerateWhat it means
QuickBooks encountered a general banking connection error that does not map to a specific identified failure. This is a catch-all code used when QuickBooks's banking connection layer reports a failure without a more specific code. Causes span the same range as other banking errors — internet connectivity, firewall, bank server availability, or an outdated QuickBooks version.
Verify your internet connection is stable. Check whether other QuickBooks bank accounts are also failing or just one — a single-account failure suggests a bank-side issue while all accounts failing suggests a QuickBooks or network issue. Temporarily disable antivirus and firewall and retry. Clear the banking cache.
6XXX Series — Company File Access and Data Problems
Company file errors prevent QuickBooks from opening, reading, or writing to your data file. These range from relatively minor — a file locked by another session — to critical — genuine data corruption. The 6000 series always includes a secondary code after the comma that identifies the specific cause. The secondary code matters as much as the primary.
For any 6XXX series error rated critical below — back up your current company file immediately before attempting any repair. Copy the QBW file to a separate location before opening QuickBooks Tool Hub, before running File Doctor, and before running Rebuild Data. This copy is your recovery safety net.
Error 6000 -77 — File Already Open in Another Location
ModerateWhat it means
QuickBooks believes the company file is already open — either by another user on the network, by a previous session that did not close cleanly, or by a lingering QuickBooks process in Task Manager. The file is locked and QuickBooks refuses to open a second instance of it to prevent simultaneous write conflicts.
Check Task Manager on all computers that might have QuickBooks open. Look for QBW32.exe or QBDBMgrN.exe processes and end them if QuickBooks should be closed. Also check the folder containing your company file for a file with the same name but an .LCK extension — delete it if found. Then retry opening the company file.
Error 6000 -82 — Damaged Company File
CriticalWhat it means
QuickBooks has encountered internal corruption in the company file that prevents it from opening or accessing data safely. This can result from a power failure or improper shutdown while QuickBooks was writing to the file, a hard drive developing bad sectors beneath the file, or antivirus software scanning the file while QuickBooks was actively writing to it. This is one of the more serious 6XXX errors because it indicates genuine data integrity issues rather than access or permission problems.
Back up the current file as-is immediately — even in its damaged state — before attempting any repair. Run QuickBooks File Doctor. If File Doctor does not resolve it, run File → Utilities → Verify Data followed by File → Utilities → Rebuild Data. If neither resolves it, restore from the most recent known-good backup.
Error 6000 -83 — Insufficient Windows File Permissions
ModerateWhat it means
The Windows user account attempting to open QuickBooks does not have sufficient read and write permissions on the folder containing the company file. Common after a Windows user account change, after moving the company file to a new folder or drive, or after a Windows update that reset folder permissions.
Right-click the folder containing your QuickBooks company file → Properties → Security tab → confirm the current user account has Full Control. If it shows Read-only or no access, grant Full Control to that user and apply to the folder and all files within it. Also confirm the QBW file itself is not marked Read-only in its own Properties.
Error 6000 -301 — Network Cannot Access File
ModerateWhat it means
In a multi-user environment, a workstation cannot reach the company file on the server — either because a firewall is blocking the connection, the network path to the server has changed, or the QuickBooks Database Server Manager service on the server is not running. Often appears after a server restart, a Windows update on the server, or a network infrastructure change.
Confirm the server computer is running and accessible on the network by pinging it from the workstation. On the server, open Services in Windows and verify that QuickBooksDB is running — start or restart it if stopped. Verify firewall rules allow QuickBooks Database Server Manager on ports 8019, 56728, and 55378-55382. Run QuickBooks Connection Diagnostic Tool from the Tool Hub.
Error 6000 -304 — File Path Too Long or Contains Special Characters
MinorWhat it means
The file path to the QuickBooks company file exceeds Windows's 256-character path length limit, or the folder names in the path contain special characters that Windows's file system cannot correctly resolve for QuickBooks. This often happens when company files are stored in deeply nested folder structures or on cloud storage with long path names.
Move the company file to a shorter, simpler path — for example C:\QB\Company.qbw. Remove any spaces, ampersands, brackets, or other special characters from folder names in the path. Open QuickBooks and use File → Open Company to navigate to the new location.
Error 6073 — User Does Not Have Permission to Access Company File
ModerateWhat it means
The Windows user account or the QuickBooks user account attempting to access the company file lacks the permissions needed. Different from 6000 -83 — this code specifically indicates a QuickBooks-level user permission issue rather than a Windows-level file system issue. Also appears when the company file is marked Read-only at the file system level.
Right-click the QBW file → Properties → confirm it is not marked Read-only. Then open QuickBooks as Administrator and try again. If in a multi-user environment, confirm the QuickBooks user has appropriate access rights in the QuickBooks user management settings.
Error 6123 — Cannot Verify Company File — Network Data File Damaged
ModerateWhat it means
QuickBooks cannot verify the company file because the associated .ND network data file — which stores information about how the file is shared on the network — is damaged or points to an incorrect server location. The .ND file is automatically regenerated by QuickBooks, so deleting it is safe and is often the fastest resolution.
Navigate to the folder containing the company file. Find the file with the same name as your QBW but with a .ND extension. Delete it. QuickBooks will recreate it automatically when you next open the company file. Then run QuickBooks File Doctor and restart QuickBooks Database Server Manager.
Error 6144 — Corrupted Company File — Cannot Open Safely
CriticalWhat it means
QuickBooks has detected that the company file has structural corruption severe enough that it cannot open the file without risking further data loss. This is among the most serious 6XXX errors and requires immediate backup before any other action.
Make a copy of the QBW file to a completely separate location right now — before any other action. Then run QuickBooks File Doctor. If File Doctor cannot repair the file, restore from the most recent known-good backup. If no backup exists and File Doctor cannot help, professional data recovery assistance may be required.
Error 6007 — Database Server Cannot Connect to Company File
ModerateWhat it means
The QuickBooks Database Server Manager on the host machine cannot establish a connection to the company file. Often caused by the Database Server Manager scanning the wrong folder, the company file having been moved since the last scan, or the Database Server service not running. Also increasingly reported in 2026 after Windows updates that reset service startup configurations.
On the server computer, open QuickBooks Database Server Manager. Click Scan Folders and ensure the folder containing the QBW file is listed. Run a scan. Confirm the QuickBooksDB service is running in Windows Services. Restart the service if needed.
HXXX Series — Multi-User and Network Connection Errors
H-series errors appear in multi-user QuickBooks Desktop environments when a workstation cannot connect to the company file hosted on a server. They are caused entirely by network configuration — the company file itself is typically undamaged. Understanding which H-code you are seeing is critical because each one has a specific cause and fix.
H-series errors never appear in QuickBooks Online — they are Desktop-only. They also do not appear when running QuickBooks in single-user mode. If you see an H-series error in what you believe is a single-user setup, someone else on your network may be hosting the file.
Error H101 — Workstation Cannot Reach Server
ModerateWhat it means
A QuickBooks workstation cannot communicate with the computer that is hosting the company file. The workstation knows where the server should be but cannot establish a network connection to it. Usually caused by firewall rules blocking QuickBooks's required ports or DNS resolution failing for the server hostname.
From the workstation, ping the server by name and by IP address. If ping fails by name but succeeds by IP address, DNS is the issue — add the server's hostname and IP to the Windows hosts file on the workstation. If ping fails entirely, check network connectivity. Add QuickBooks firewall exceptions for ports 8019, 56728, and 55378-55382 on both the server and workstation.
Error H202 — Database Server Manager Not Running or Not Configured
Moderate — Most Common H-Series ErrorWhat it means
QuickBooks on a workstation cannot connect to the company file because the QuickBooks Database Server Manager on the hosting computer is either not running, not scanning the correct folder, or not configured to allow other computers to access the file. H202 is the most frequently reported H-series error and is almost always resolved by addressing the Database Server Manager on the host computer — not by changing anything on the workstation.
On the host computer — the machine where the company file is stored — open QuickBooks Database Server Manager through the Windows Start menu. Scan the folder containing the QBW file. Confirm the service is running. If it shows as stopped, click Start Service. On workstations, go to File → Utilities and confirm Stop Hosting Multi-User Access is the option showing — meaning the workstation is correctly set to not host.
Error H303 — Hosting Configuration Conflict
ModerateWhat it means
Either multiple computers are configured to host the company file simultaneously — which causes a conflict — or the server is set not to host when it should be. QuickBooks requires exactly one computer to be the host in a multi-user environment. Workstations must have hosting turned off. If a workstation previously acted as host and was not correctly switched back, H303 results.
On the server: File → Utilities → Host Multi-User Access. On every workstation: File → Utilities → Stop Hosting Multi-User Access. Only one computer — the server — should have hosting enabled. Restart all QuickBooks instances after making this change.
Error H505 — Server File Damaged or .ND File Corrupted
CriticalWhat it means
The company file on the server is damaged, or the .ND network data file is corrupted to the point where multi-user access cannot be established. Workstations cannot connect because the file they are trying to reach is in an inconsistent state. Back up before attempting any repair — the company file may have data integrity issues.
On the server, navigate to the folder containing the company file. Delete the .ND file. Run QuickBooks File Doctor on the server computer — not the workstation. Rescan the folder in QuickBooks Database Server Manager. Run Verify Data and Rebuild Data if File Doctor identifies errors.
Error H101 / H202 / H303 Combined — Firewall Blocking QuickBooks Ports
When Multiple H Errors Appear TogetherWhat it means
When multiple H-series codes appear at the same time — particularly if they appear on different workstations with different error codes — the most likely cause is a firewall or network security appliance blocking QuickBooks's required communication ports rather than individual machine-level configuration issues.
- Port 8019 — QuickBooks Database Server Manager
- Port 56728 — QuickBooks file sharing
- Ports 55378 to 55382 — QuickBooks communication range
On the Windows Firewall of both server and workstations, create inbound and outbound rules for these ports. If you use a hardware firewall or network security appliance, your IT administrator needs to open these same ports. Run the QuickBooks Connection Diagnostic Tool from the Tool Hub after adding the rules.
PS and 17XXX Series — Payroll and Tax Table Errors
If you are running QuickBooks Desktop 2023 or any earlier version — payroll tax tables are permanently discontinued as of May 31, 2026. Payroll errors on these versions cannot be fully resolved. The only resolution is migrating to QuickBooks Desktop 2024 or QuickBooks Online before processing further payroll. Continuing to run payroll on Desktop 2023 after this date means processing with outdated tax tables — which creates payroll compliance risk.
Error PS038 — Stuck Paychecks Blocking Payroll Update
High — Most Common Payroll ErrorWhat it means
One or more paychecks are stuck with an Online to Send status, blocking QuickBooks from processing payroll updates. This is the most widely reported QuickBooks Desktop payroll error in 2025 and 2026. When paychecks are stuck in this state, QuickBooks cannot complete payroll tax table downloads or send payroll data — even if the payroll subscription is active and QuickBooks is up to date.
Go to Employees → My Payroll Service → Send Usage Data first. Then press Ctrl + F to open the Find Transactions window. Click Advanced and set filters for Online Status → Online to Send. Any stuck paychecks will appear. Open each stuck paycheck, add a $0.00 payroll item temporarily to trigger the Net Pay Locked prompt, click Yes, delete the dummy item, and save. The paycheck status should clear. Then retry the payroll update.
Error 17000 — Payroll Subscription Expired or Not Activated
ModerateWhat it means
QuickBooks cannot verify that your payroll subscription is currently active. This appears when a subscription has lapsed, when a payment method on the Intuit account has expired, or when QuickBooks cannot communicate with Intuit's servers to confirm subscription status.
Log into your Intuit account at quickbooks.intuit.com and verify your payroll subscription status. Confirm the payment method on file is current and not expired. Update QuickBooks to the latest release. Then log out of QuickBooks completely, restart it, and retry the payroll tax table download.
Error 17337 — Payroll Tax Table Update Failed
ModerateWhat it means
QuickBooks attempted to download the latest payroll tax tables and the download failed — either due to an internet connection problem during the download, corrupted payroll data that prevents the tax tables from being applied, or a conflict with security software blocking the download.
Check your internet connection stability. Close QuickBooks and reopen it. Go to Employees → Get Payroll Updates and try the download again. If it continues to fail, run File → Utilities → Verify Data to check for company file errors that may be preventing the update from applying.
Error 17500 — Payroll Data Damaged
CriticalWhat it means
QuickBooks has detected corruption in the employee records, payroll items, or payroll transaction data that prevents payroll from processing. This is the most serious payroll error code — payroll cannot proceed until the underlying data damage is addressed.
Back up immediately before any other action. Run QuickBooks File Doctor with a focus on payroll. Run File → Utilities → Verify Data — if errors are found, run Rebuild Data. Review payroll items in the Payroll Item List for any that show as corrupted or display unusual values. If the damage is extensive and Rebuild does not resolve it, restore from the most recent clean backup made before the corruption appeared.
Errors Triggered by Windows Updates — Specific to 2025 and 2026
A distinct category of QuickBooks Desktop errors has been documented extensively in 2025 and 2026 — errors that appeared without any change to QuickBooks itself, triggered specifically by Windows cumulative updates. These are particularly important to identify because the standard QuickBooks troubleshooting steps do not always address the root cause, which is in Windows rather than in QuickBooks.
Error 3371 — Status Code 11118 — Licence Data Cannot Be Loaded
Very Common — Significantly Increased Post-Windows UpdatesWhat it means
QuickBooks cannot load its licence data because the EntitlementDataStore.ecml file — the file where QuickBooks stores licence verification data — is missing, corrupted, or cannot be read by the current Windows user account. This has always been a known error but became dramatically more common following Windows cumulative updates in late 2025 and early 2026, particularly update KB5051987 and subsequent releases, which changed how Windows handles certain application data files and permissions.
The error message typically reads: QuickBooks could not load the license data. This may be caused by missing or damaged files.
Open the QuickBooks Tool Hub. Go to Program Problems → Quick Fix My Program. If that does not resolve it, open the Tool Hub again, go to Program Problems → QuickBooks Program Diagnostic Tool, and let it run. If both fail, navigate manually to: C:\ProgramData\Intuit\Entitlement Client\v8 — delete the EntitlementDataStore.ecml file. QuickBooks will recreate it and prompt you to re-enter your licence number.
Important: ProgramData is a hidden folder. In Windows File Explorer, go to View → Options → Change folder and search options → View tab → select Show hidden files, folders, and drives.
WDDM Service Not Running Error — QuickBooks Cannot Start
Common — Post-Windows Update 2026What it means
QuickBooks displays an error stating that the WDDM service is not running or cannot be started, preventing QuickBooks from opening. WDDM — Windows Display Driver Model — is referenced by QuickBooks's rendering process. This error began appearing in February 2026 following Windows graphics driver updates that changed how certain applications interact with the display driver model.
Open Services in Windows by pressing Win + R, typing services.msc, and pressing Enter. Scroll down to find the QuickBooks service entries. Check whether any QuickBooks-related services show as stopped and start them. If the error persists, run QuickBooks as Administrator. Update Windows fully including all driver updates. If the display driver was recently updated, check Device Manager for any flagged display adapter issues.
QuickBooks Migration Failed Unexpectedly — Windows 11 Specific
Moderate — Reported Extensively on Windows 11What it means
During a QuickBooks Desktop version migration — upgrading from an older QuickBooks version, migrating a company file, or running the Desktop to Online migration tool — the process fails with a generic migration failure error. This has been specifically documented on Windows 11 systems following cumulative updates in late 2025 and 2026, with the migration tool failing partway through without a clear error code.
Run the migration process as Administrator. Temporarily disable antivirus and Windows Defender Real-Time Protection during the migration. Move the company file to a simple local path — C:\QB\ — before running the migration rather than attempting it from a network location, desktop, or cloud-synced folder.
QuickBooks Backup Not Working After Windows Update
CommonWhat it means
QuickBooks automated backups stop working or fail silently following a Windows update. This happens when Windows updates reset the permissions on the backup destination folder, when the backup destination path becomes inaccessible due to changes in network share mappings, or when Windows security settings change the access rights of background processes.
Open QuickBooks backup settings and verify the backup destination path is still accessible. Navigate to the backup folder and confirm the current Windows user has full read and write access. If backing up to a network location, verify the mapped drive or UNC path is still valid. Consider switching the backup destination to a local folder and adding cloud sync separately rather than backing up directly to a cloud-synced folder.
Five Steps That Resolve the Majority of QuickBooks Desktop Errors
Before attempting any error-specific solution, work through these five steps in order. They address the most common root causes across all error categories and take less than fifteen minutes.
Update QuickBooks to the latest release
Go to Help → Update QuickBooks Desktop → Update Now. Check all update categories and click Get Updates. Many errors — particularly 15XXX banking errors, 6XXX file errors, and payroll errors — are directly caused by an outdated QuickBooks version that predates a fix already released by Intuit. This is the single most impactful first action.
Run QuickBooks Tool Hub
Download the QuickBooks Tool Hub from quickbooks.intuit.com — only from Intuit's official website. Do not download it from any other source. Once installed, use the Company File Issues tab for 6XXX errors, the Network Issues tab for H-series errors, the Program Problems tab for crashes and Error 3371, and the Installation Issues tab for 1XXX errors. The Tool Hub resolves many errors automatically without any manual steps.
Back up before any repair attempt
Before running File Doctor, before running Rebuild Data, and before any step that modifies your company file — go to File → Back Up Company → Create Local Backup and save to an external drive or cloud folder. This is non-negotiable and takes two minutes. A repair that produces an unexpected result is recoverable with a backup. Without a backup, it may not be.
For banking errors — confirm your bank's website is accessible
Open a browser and log into your bank's website directly before troubleshooting anything in QuickBooks. If the bank's website is showing errors, maintenance messages, or is inaccessible — the problem is on the bank's side. Wait until the next business day and retry QuickBooks before changing any settings.
For persistent errors — check Intuit's system status
Go to status.intuit.com. If Intuit's servers are experiencing a known outage or maintenance affecting banking, payroll, or other services — your error may resolve on its own once Intuit restores service. Attempting troubleshooting while Intuit's infrastructure is down will not resolve the issue regardless of what you do locally.
When to request independent consulting
If these five steps do not resolve your error, and the error-specific first steps in the sections above also do not help — the issue may require deeper troubleshooting based on your specific system configuration, network setup, or company file structure. Independent written consulting provides guidance built around your exact situation rather than generic steps.
Request Consultant HelpAll QuickBooks Error Codes at a Glance — 2026
Use this table to quickly identify your error code, understand its category and severity, and find the primary cause before working through the detailed sections above.
| Error Code | Category | Severity | Primary Cause |
|---|---|---|---|
| 10000 | Banking Connection | Moderate | Generic connection failure — firewall or bank server |
| 15103 | Banking Connection | Moderate | Bank re-authorisation required |
| 15106 | Banking Connection | Moderate | Outdated software or corrupted banking cache |
| 15215 | Banking Connection | Minor | Bank server temporarily unavailable — wait and retry |
| 15217 | Banking Connection | Moderate | Digital signature verification failure — Windows update related |
| 15222 | Banking Connection | Moderate | Firewall or SSL certificate blocking connection |
| 15240 | Banking Connection | Moderate | Payroll service temporarily unavailable or subscription lapsed |
| 15243 | Banking Connection | Moderate | Bank credentials rejected — update credentials in QuickBooks |
| 15271 | Banking Connection | Critical | Payroll data corruption — back up immediately |
| 6000 -77 | Company File | Moderate | File already open in another location or session |
| 6000 -82 | Company File | Critical | Damaged company file — back up before any repair |
| 6000 -83 | Company File | Moderate | Insufficient Windows file permissions |
| 6000 -301 | Company File | Moderate | Network cannot access file — Database Server Manager issue |
| 6000 -304 | Company File | Minor | File path too long or contains special characters |
| 6007 | Company File | Moderate | Database Server cannot connect to company file |
| 6073 | Company File | Moderate | QuickBooks or Windows permission denied |
| 6123 | Company File | Moderate | .ND network data file damaged — delete and let QuickBooks recreate |
| 6144 | Company File | Critical | Severe company file corruption — restore from backup |
| H101 | Network | Moderate | Workstation cannot reach server — firewall or DNS issue |
| H202 | Network | Moderate | Database Server Manager not running on server — most common H error |
| H303 | Network | Moderate | Hosting configuration conflict — only one computer should host |
| H505 | Network | Critical | Server company file or .ND file damaged |
| 1310 | Installation | Moderate | Cannot write during installation — permissions issue |
| 1328 | Installation | Moderate | Cannot update file — locked by another process |
| 1402 | Installation | Moderate | Cannot open registry key — run as Administrator |
| 1603 | Installation | Critical | Fatal installation failure — run Clean Install Tool |
| 1618 | Installation | Minor | Another installation already in progress |
| 1904 | Installation | Moderate | Cannot register module or DLL |
| 1935 | Installation | Critical | .NET Framework component registration failed |
| PS038 | Payroll | High | Stuck paychecks with Online to Send status |
| 17000 | Payroll | Moderate | Payroll subscription expired or not activated |
| 17337 | Payroll | Moderate | Payroll tax table update failed |
| 17500 | Payroll | Critical | Payroll data damaged — back up before repair |
| 3371 -11118 | Windows / Licence | High — Increasing 2026 | Licence data cannot load — EntitlementDataStore.ecml damaged |
| WDDM Error | Windows | Moderate | WDDM service not running — Windows graphics driver update |
| 80029 | Company File | Critical | Component registration failed — damaged installation |
| 80040 | Company File | Critical | Windows component communication failure — .NET or MSXML |
| -6189 -816 | Company File | Critical | .TLG transaction log mismatch — delete .TLG and run File Doctor |
Frequently Asked Questions — QuickBooks Error Codes
A: QuickBooks error codes are numerical identifiers that pinpoint the category of a problem. 15XXX codes are banking and connection errors. 6XXX codes are company file access and data errors. HXXX codes are network and multi-user errors. 1XXX codes are installation errors. 17XXX codes are payroll errors. 80XXX codes are company file corruption and Windows component errors. Error 3371 is a licence data failure that has become significantly more common following Windows updates in 2025 and 2026. Understanding the category tells you immediately whether to look at your bank, your company file, your network, or your Windows installation.
A: Two things — in order. First, update QuickBooks via Help → Update QuickBooks Desktop. A significant proportion of recurring errors are caused by outdated software that predates a fix already released. Second, download and run the QuickBooks Tool Hub from quickbooks.intuit.com. The Tool Hub is Intuit’s official diagnostic tool and automatically resolves many errors — particularly company file issues, network problems, and installation failures — without any manual steps. Always back up your company file before running any repair tool.
A: Error 6000 always appears with a secondary code that identifies the specific cause. 6000 -77 means the file is already open in another session. 6000 -82 means damaged data preventing access. 6000 -83 means Windows permission issues. 6000 -301 means a network configuration problem — typically QuickBooks Database Server Manager is not running. 6000 -304 means the file path is too long. The secondary code after the comma is more important than the 6000 itself — it determines which fix is appropriate.
A: Error 3371 — status code 11118 — has increased significantly following Windows cumulative updates in 2025 and 2026 that changed how Windows handles application data files and permissions. The error occurs when QuickBooks cannot read its licence verification file — EntitlementDataStore.ecml. The resolution is to use the QuickBooks Tool Hub Program Problems tab, or if that does not resolve it, to manually navigate to C:\ProgramData\Intuit\Entitlement Client\v8 and delete the ecml file so QuickBooks recreates it fresh.
A: H202 means QuickBooks on a workstation cannot connect to the company file on the server because QuickBooks Database Server Manager is not running, not scanning the correct folder, or not configured to allow network access to the file. The resolution is always on the host computer — not the workstation — open QuickBooks Database Server Manager on the server, scan the folder containing the company file, and confirm the service is running. Workstations should have hosting turned off in File → Utilities → Stop Hosting Multi-User Access.
A: PS038 means one or more paychecks are stuck with an Online to Send status, blocking payroll updates. Go to Employees → My Payroll Service → Send Usage Data first. Then use Ctrl + F → Advanced → filter by Online Status → Online to Send to find stuck paychecks. Open each stuck paycheck, add a $0.00 dummy payroll item to trigger the Net Pay Locked prompt, click Yes, delete the dummy item, and save. This clears the stuck status. Retry the payroll update after clearing all stuck paychecks.
A: Some can — particularly the critical-rated 6XXX and 80XXX errors involving company file corruption. However, data loss from these errors is not inevitable if you act correctly. The most important protective step is backing up before attempting any repair — even a damaged file copy is a recovery option. Errors rated Moderate or Minor — particularly network errors, permission errors, and connection errors — do not directly risk data loss. The risk of data loss most commonly comes from attempting multiple repair approaches in the wrong order without backing up between each attempt.
A: Contact Intuit directly for subscription billing issues, product activation, licence recovery, Intuit account access problems, and QuickBooks Online platform-specific issues requiring backend access. Use independent consulting when you need detailed written troubleshooting guidance specific to your version and system, when standard fixes from official documentation have not resolved a persistent error, or when you need migration or multi-user setup guidance that official support handles less thoroughly. For payroll issues on Desktop 2023 and earlier — contact Intuit about migration options since those versions have lost support.
If the Steps on This Page Have Not Fixed Your Error — Independent Consulting Is the Next Step
Our independent QuickBooks consultant service provides written advisory guidance built specifically around your QuickBooks version, your operating system, your company file situation, and the exact error you are seeing — not a generic response. KD Sharma reviews every request personally. No obligation when you submit. Fee confirmed before payment is taken.