QuickBooks Error 6000: causes & how to fix it.
Error 6000 — usually shown as 6000 followed by another number (for example -83, -301, or -82) — is the family of QuickBooks Desktop company-file errors meaning QuickBooks can’t open the company file. It commonly appears when opening a file over a network, restoring a backup, or running in multi-user mode. Below: the causes in order of likelihood, the ordered self-fix, and when to call a Certified ProAdvisor. Independent firm, not affiliated with Intuit Inc.
Error 6000 is the QuickBooks Desktop 6000-series — a family of company-file errors that all mean QuickBooks cannot open the company file. It usually shows as 6000 followed by a second number (such as -83, -301, or -82), and most often surfaces when opening a file over a network, in multi-user mode, while restoring a backup, or after a file has been moved. A handful of causes account for the large majority, and the self-fix steps work in order of likelihood; QuickBooks Tool Hub resolves many 6000-series errors. The 6000-series are QuickBooks Desktop and Enterprise errors — they do not appear in QuickBooks Online.
Reference maintained by the Certified QuickBooks ProAdvisor team at TechBrot Inc., an independent firm — not Intuit’s software support. Not affiliated with Intuit Inc.
Error 6000, in five questions.
What is QuickBooks Error 6000?
A family of QuickBooks company-file errors (the 6000-series): QuickBooks Desktop can’t open the company file. It’s usually shown as 6000 followed by a second number — for example “6000 -83”, “6000 -301”, or “6000 -82” — and most often appears when opening a file over a network, in multi-user mode, or while restoring a backup. Exclusive to QuickBooks Desktop and Enterprise — it does not occur in QuickBooks Online.
What causes Error 6000?
Six causes account for the large majority: (1) a damaged or misconfigured network/hosting (multi-user) setup; (2) a damaged company file (.QBW) or its supporting .ND/.TLG files; (3) a firewall or antivirus blocking QuickBooks; (4) opening a file on an external or network drive with bad permissions; (5) the file being converted, restored, or opened in the wrong QuickBooks version; (6) a file moved across machines.
Can I fix Error 6000 myself?
Often yes, in order of likelihood: run QuickBooks Tool Hub (Quick Fix my File, then File Doctor); rename the .ND and .TLG files; copy the company file to the local drive and open it there; check hosting/multi-user configuration; check firewall and antivirus; restore from a clean backup. Tool Hub alone clears many 6000-series errors.
When does Error 6000 need a ProAdvisor?
When self-fix doesn’t resolve it, the error recurs, the company file is genuinely damaged, or it appears with a specific suffix (such as -83, -301, or -82) that won’t clear — a signal the file or its hosting configuration needs professional repair past the documented surface steps.
What do the numbers after 6000 mean?
The 6000 marks the 6000-series company-file family; the second number narrows down why QuickBooks can’t open the file. 6000 -83, 6000 -301, and 6000 -82 are common suffixes tied to network/hosting, permission, or file-integrity issues. They share one diagnostic approach: repair the connection and hosting first, then the file.
Certified QuickBooks ProAdvisor credentials.
4
core QuickBooks platforms certified — Desktop, Enterprise, Online (Level 2), Payroll
L2
QuickBooks Online ProAdvisor tier (the highest)
Yearly
Annual Intuit re-certification
- Error 6000 is a Desktop/Enterprise company-file error — resolving it takes fluency in hosting, network paths, .ND/.TLG files, and file-integrity repair.
- Every ProAdvisor holds active Desktop and Enterprise certifications; Intuit’s public ProAdvisor directory lists active ProAdvisors for verification.
- Operational experience to diagnose the specific 6000 suffix past the documented surface steps — not a script-reading queue.
Error 6000, plainly.
Error 6000 is the QuickBooks Desktop 6000-series — a whole family of company-file errors that all mean the same thing at the core: QuickBooks reached for your company file and couldn’t open it. You almost always see the 6000 paired with a second number that narrows down why — 6000 -83, 6000 -301, 6000 -82, and others — but the family shares one symptom and one diagnostic approach. It most often appears when opening a file over a network, working in multi-user mode, restoring a backup, or after the file has been moved to a new computer or drive.
The good news is that the 6000-series is highly fixable, and the self-fix steps below work in order of likelihood — running QuickBooks Tool Hub (Quick Fix my File, then File Doctor) resolves many 6000-series errors before deeper troubleshooting is needed. If self-fix doesn’t resolve it, the error recurs within days, or it appears with a suffix that won’t clear, a Certified ProAdvisor diagnostic identifies the deeper cause — typically network/hosting configuration or genuine company-file integrity damage past the documented surface steps. The 6000-series are QuickBooks Desktop and Enterprise errors; they do not appear in QuickBooks Online.
Six common causes, in order of likelihood.
The self-fix steps address these in the same order — so working through them sequentially resolves an Error 6000 efficiently.
Cause 01 · Damaged or misconfigured network / hosting setup
The most common cause in multi-user environments. When the company file lives on a server or another computer, a damaged network connection or an incorrectly configured multi-user/hosting setup stops QuickBooks from reaching the file — an Error 6000. A workstation mistakenly set to host, or a stopped Database Server Manager, is a frequent trigger.
Cause 02 · Damaged company file or supporting .ND/.TLG files
Genuine integrity damage to the company (.QBW) file, or corruption in the network-data (.ND) or transaction-log (.TLG) files that QuickBooks uses to open it, breaks access and produces a 6000-series error. This is where surface steps stop working and a diagnostic is warranted.
Cause 03 · Firewall or antivirus blocking QuickBooks
Windows Firewall or third-party antivirus blocks the executables or ports QuickBooks needs to reach the company file. This often appears right after a security-software or Windows update changes the rules. The fix is explicit exceptions for the QuickBooks program files and ports.
Cause 04 · Bad permissions on an external or network drive
Opening a company file stored on an external drive or a network share where the Windows account QuickBooks runs under lacks read/write permission surfaces as an Error 6000. Permission changes after an update, a new user profile, or a relocated folder can all cause it.
Cause 05 · File being converted, restored, or opened in the wrong version
A file mid-conversion, mid-restore, or opened in a different QuickBooks year-version than it was created in can produce a 6000-series error. The file and the program disagree about version, state, or location, and the open fails.
Cause 06 · File moved or restored across machines
Moving the company file to a new computer, or restoring it onto different hardware, can break the path and the supporting files QuickBooks expects — producing an Error 6000 the first time the file is opened on the new machine.
How to fix Error 6000 yourself.
Six steps, in order. Most 6000-series cases clear within the first two — if all six don’t resolve it, stop and book a diagnostic.
Run QuickBooks Tool Hub (Quick Fix my File, then File Doctor)
Open QuickBooks Tool Hub → Company File Issues → Quick Fix my File, then run QuickBooks File Doctor. This alone resolves many 6000-series errors by repairing the connection, hosting, and file settings automatically. Run it on the computer that stores the file when possible.
Rename the .ND and .TLG files
In the folder with your company file, rename the matching .ND and .TLG files (add .OLD to the end). QuickBooks rebuilds them automatically on the next open. This clears corruption in those supporting files without touching the company file itself.
Copy the company file locally and open it
Copy your company file to the local Desktop and open it there. If the local copy opens cleanly, the problem is the network path, drive permissions, or hosting — not the file itself. If the local copy still fails, the issue is the file or the QuickBooks install.
Check hosting / multi-user configuration
If the file is shared, make sure only the host computer is set to host multi-user access and that Database Server Manager is running there. A workstation mistakenly set to host, or a stopped service, breaks the connection that an Error 6000 reports.
Check firewall and antivirus
Add exceptions for the QuickBooks program files and ports in Windows Firewall and any third-party antivirus, or temporarily disable the security software to test. If the file opens with protection off, create permanent rules so the block doesn’t return after a reboot.
Restore from a clean backup, then escalate
If the Error 6000 persists, restore from a known-good backup created before the error began. If the error survives even a clean restore, stop — continued retries can mask deeper damage. A Certified ProAdvisor diagnostic identifies the underlying cause and resolves it against a written scope.
Self-fix didn’t clear Error 6000?
A Certified ProAdvisor diagnoses the deeper cause — typically a $1,200–$3,000 fixed-fee scope. Independent firm.
Three signals it’s a ProAdvisor call.
It persists after all six steps
You’ve worked the ordered fix and the Error 6000 still blocks the file. The cause is past the documented surface — usually network/hosting configuration or genuine company-file integrity damage.
It keeps coming back
The Error 6000 clears, then returns. A recurring error signals an underlying configuration, security-software, or file-integrity problem that a one-time fix masks rather than resolves.
A specific suffix won’t clear
A 6000-series code with a stubborn suffix — such as 6000 -83, 6000 -301, or 6000 -82 — that survives the self-fix points to deeper company-file or hosting problems. The moment to stop self-fixing and have the file assessed before damage progresses.
A Certified ProAdvisor diagnoses past the surface.
When the documented steps don’t hold, the cause is usually past the surface — a damaged network-data (.ND) or transaction-log (.TLG) file, a misconfigured multi-user/hosting setup, a security program that re-blocks access after each reboot, bad folder permissions on an external or network drive, or genuine company-file integrity damage. A Certified ProAdvisor with active Desktop and Enterprise certifications diagnoses the actual root cause behind the specific 6000 suffix, fixes it against a written scope, and verifies the file opens cleanly before closing. Independent firm — not Intuit, and not Intuit’s software support.
Diagnostic
30-minute diagnostic, usually scheduled within a day
$1,200–$3,000
typical fixed-fee scope for focused Error 6000 resolution
Independent
Certified ProAdvisor firm — not Intuit, not Intuit’s software support
What people ask about Error 6000.
Is this Intuit’s official support?
What is QuickBooks Error 6000?
What causes QuickBooks Error 6000?
Can I fix QuickBooks Error 6000 myself?
What do the numbers after 6000 mean?
When does Error 6000 require a ProAdvisor?
Does Error 6000 appear in QuickBooks Online?
Self-fix didn’t resolve it?
Self-fix didn’t work? Book a diagnostic.
If an Error 6000 code persists after the steps below, recurs within days, or appears with a suffix that won’t clear, a 30-minute diagnostic surfaces the real cause — typically a $1,200–$3,000 fixed-fee scope for focused resolution. Independent ProAdvisor firm, written scope before any work begins.