QuickBooks Help
7 Common QuickBooks Errors and How to Fix Them
Why QuickBooks errors cluster into families
QuickBooks error codes look random, but most belong to a few families: company-file access problems, multi-user networking issues, bank-feed and sync failures, and update or installation faults. Identifying the family tells you which category of fix to try — and which fixes could make things worse.
Before attempting any repair, make a backup copy of your company file. Many 'fixes' found in forums involve rebuilding or modifying the file, and a current backup is the difference between an inconvenience and a disaster.
6000-series errors: the file can't be opened
Errors beginning with -6000 mean QuickBooks couldn't access the company file. Common causes include damaged network paths, files stored in synced cloud folders (a frequent culprit), permission problems, or a corrupted transaction log.
Safe first steps: open the file from a local drive instead of a network or synced folder, rename the .ND and .TLG companion files so QuickBooks regenerates them, and run the official File Doctor tool. If the file opens but behaves oddly afterward, stop and get professional eyes on it — repeated rebuilds on a damaged file can compound corruption.
H202 and multi-user mode failures
H202 appears when a workstation can't reach the server hosting the company file. It's almost always a networking issue: the database server service isn't running, firewall ports are blocked, or hosting is enabled on the wrong machines.
Check that hosting is enabled only on the server, verify the QuickBooksDB service is running, and confirm firewall exceptions for the QuickBooks ports for your version. If your office network has changed recently — new router, new server, VPN — that change is usually the cause.
Bank feed errors and duplicate transactions
Bank feed failures (such as 102, 103, or 105 in QuickBooks Online) usually trace to the bank's side: changed credentials, new multi-factor prompts, or a redesigned bank website. Re-authenticate the connection first; if it persists for days, the bank's feed itself may be down.
Duplicates are more dangerous than missing transactions because they inflate income or expenses silently. If you see duplicates after reconnecting a feed, resolve them through the banking review screen rather than deleting ledger entries directly, and re-reconcile the affected period.
When to stop DIY and call a professional
Call in help when an error involves possible data damage (failed rebuilds, missing transactions, balance discrepancies), when payroll or filed periods are affected, or when the same error returns repeatedly. Those symptoms suggest a structural problem that quick fixes will only paper over.
A certified ProAdvisor can usually diagnose remotely in one session, fix the root cause, and document what changed — far cheaper than rebuilding months of damaged data later.
Stuck on this in your own books?
A certified advisor can look at your exact situation in a free consultation — and tell you honestly whether it's a five-minute fix or a project.
Call 1-888-871-0037