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. Intuit says it can happen on both local and network setups. Below: the causes Intuit ties to each code, Intuit’s fix steps in order, and when to call a QuickBooks ProAdvisor.
Error 6000 is the QuickBooks Desktop 6000-series — a family of company-file errors that all mean QuickBooks cannot open the company file. Intuit’s current article (updated 8/5/2026) says a -6000 error usually has 3 or 4 more digits (such as -82, -83 or -301) and can happen on both local and network setups. Intuit’s first steps for any of them: update QuickBooks, then run File Doctor from QuickBooks Tool Hub; after that, the steps split by whether the file is opened locally or over a network. The 6000-series are QuickBooks Desktop and Enterprise errors — they do not appear in QuickBooks Online.
Published by TechBrot.
Error 6000, in five questions.
What is QuickBooks Error 6000?
A family of QuickBooks company-file errors (the 6000-series). Intuit’s article (updated 8/5/2026) says a -6000 error “usually has 3 or 4 more digits and a message that says you can’t open your company file,” and that it can happen on both local and network setups. A QuickBooks Desktop and Enterprise error — it does not occur in QuickBooks Online.
What causes Error 6000?
Intuit’s code table ties the codes to six kinds of cause: (1) the file hosted by a computer that isn’t the server, or more than one host; (2) a damaged company file, .TLG or .ND file; (3) a firewall blocking the connection; (4) wrong folder permissions or Database Server Manager problems; (5) wrong network setup; (6) a damaged QuickBooks installation, single-user mode conflicts, or a file already open locally.
Can I fix Error 6000 myself?
Often, yes — Intuit’s order: update QuickBooks; run File Doctor from Tool Hub; on a network, make sure hosting is off on the workstations; rename the .ND and .TLG files; open a sample company file; copy the company file to the desktop and open it there; then the network steps (close QuickBooks processes on the server, folder permissions, firewall and antivirus) or, for a local file, restore a backup or use Auto Data Recovery.
When does Error 6000 need a ProAdvisor?
When Intuit’s steps don’t resolve it, the error comes back, the company file is genuinely damaged, or a specific suffix won’t clear — a signal the file or its hosting setup needs careful repair.
What do the numbers after 6000 mean?
The second number narrows down the cause. From Intuit’s table: -6000, -82 is wrong network setup; -6000, -107 is a damaged .TLG file; -6000, -1076 is a damaged QuickBooks installation; -6000, -305 is wrong network setup or company-file damage. Intuit publishes separate articles for codes such as 6000, -83 and 6000, -301.
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. Intuit says the 6000 usually comes with 3 or 4 more digits that narrow down why — 6000 -83, 6000 -301, 6000 -82, and others — but the family shares one symptom. Intuit’s current article (updated 8/5/2026) says -6000 errors can happen on both local and network setups, and its code table ties each suffix to a cause — hosting, damaged files, firewall, permissions, or network setup.
Intuit’s steps start the same way for every code — update QuickBooks, then run File Doctor from QuickBooks Tool Hub — and then split by whether you open the file locally or over a network. If those steps don’t resolve it, the error comes back, or a suffix won’t clear, a QuickBooks ProAdvisor diagnostic looks at what’s left — often the network or hosting setup, or the company file itself. The 6000-series are QuickBooks Desktop and Enterprise errors; they do not appear in QuickBooks Online.
Six kinds of cause, from Intuit’s code table.
Grouped from the code table in Intuit’s current -6000 article (updated 8/5/2026). Intuit doesn’t rank them — match the suffix you see to the cause.
Cause 01 · File hosted by a computer that isn’t the server
Intuit ties several codes (-6010, -100; -6138, -105; -6210, 0; -6189, -83; -6190, -83) to a company file hosted by a computer that’s not the server, -6120, 0 to a workstation hosting the file, and -6073, -816 in part to multiple computers hosting it. Intuit’s advice: use one computer or server to host company files.
Cause 02 · Damaged company file, .TLG or .ND file
Intuit ties -6000, -107 to a damaged .TLG file, -6000, -832 to hosting being on or the .ND file not working right, -6144, -103 and -6144, 0 to an .ND file with an incorrect path, and -6000, -305 and -6073, -816 in part to company-file damage.
Cause 03 · Firewall blocking the connection
Intuit ties -6176, 0 to a firewall blocking the connection between two computers, and lists firewall settings as one cause of -6073, -816. Intuit’s fix is to configure the firewall ports and set up an exception in your antivirus software.
Cause 04 · Folder permissions or Database Server Manager
Intuit ties -6129, -101 to wrong folder permissions or QuickBooks Database Server Manager not working right, and -6144, -103 in part to damage to the QuickBooks Database Manager Windows user account.
Cause 05 · Wrong network setup
Intuit ties -6012, -1061, -6144, -82 and -6000, -82 to wrong network setup, and -6000, -305 in part to it.
Cause 06 · Damaged installation, single-user conflicts, or a file open locally
Intuit ties -6000, -1076 to a damaged QuickBooks installation; -6190, 816, -6190, -85 and -6190, -82 to a user in single-user mode instead of multi-user, or a mismatch between the .TLG and .QBW files; and -6087, 0 and -6131, 0 to the file being open locally.
Every -6000 code, and where its fix lives.
Match the second number you see. Where TechBrot has a page for the code it links there; otherwise it links Intuit’s own current article for that code (read September 28, 2026).
-6000, -77
Damaged .ND/.TLG configuration files, a mapped drive, or folder permissions when opening the company file. Intuit’s steps include renaming the .ND and .TLG files, which it says causes no data loss. Intuit’s -6000, -77 article.
-6000, -80
Intuit has no separate article; it covers -80 inside its article on a lost connection to the company file, citing folder permissions, firewall configuration or Windows internet settings. Intuit’s connection-lost article.
-6000, -82
Network setup or hosting, and Intuit’s own article ends by noting the company file may have data damage. Intuit’s -6000, -82 article.
-6000, -83
Opening, backing up or restoring, often on a server or a hosted file. TechBrot’s -6000, -83 page.
-6000, -301
Damaged support files, a damaged company file, or encryption software. TechBrot’s -6000, -301 page.
-6073
QuickBooks Desktop can’t open the company file; Intuit documents it with two second numbers. TechBrot’s 6073 page.
-6123
QuickBooks Desktop can’t open, upgrade or restore the company file; Intuit calls it likely a network or file issue. TechBrot’s 6123 page.
-6150
A company-file error Intuit says means the file could have issues that need repair. TechBrot’s 6150 page.
How to fix Error 6000 yourself.
Eight steps, in the order Intuit’s article gives them. Skip the network-only steps if the file is on your own computer; if none resolves it, stop and book a diagnostic.
Update QuickBooks to the latest release
Intuit’s first step for any -6000 error. Install the latest QuickBooks Desktop release, then try the file again.
Run File Doctor from QuickBooks Tool Hub
Close QuickBooks and open Tool Hub. Select Company File Issues → Run QuickBooks File Doctor (it can take up to a minute to open). Select your company file, choose Check your file (the middle option only), select Continue, and enter your QuickBooks admin password.
On a network: make sure only one computer hosts
Intuit suggests one computer or server hosts the company file. On each workstation, press F2 to open Product Information and find Local Server Information — hosting should be turned off.
Rename the .ND and .TLG files
In the folder with your company file, find the .ND and .TLG files with the same name as your company file and add .OLD to the end (for example company_file.qbw.nd.OLD). Intuit notes you won’t lose any QuickBooks data. On a network, then open Tool Hub → Network Issues → QuickBooks Database Server Manager on the server and scan the folder.
Open a sample company file
From the No Company Open window, open a sample file. If the sample opens, the problem is with your company file; if the sample shows the same error, Intuit says to repair your QuickBooks installation.
Copy the company file to the desktop and open it
Copy the .QBW file to the desktop, hold Ctrl while opening QuickBooks, choose Open or restore an existing company, and open the desktop copy. If it opens, Intuit says the location you save the file to may be damaged, or the file may be in too many folders for the file-system path limit.
On a network: processes, permissions, firewall
Sign in as Administrator on the server, open Task Manager, show processes for all users, and end QBW32.EXE, qbupdate.exe and QBDBMgr.exe; then open the file in multi-user mode. If it still fails, check the folder permissions for sharing company files, and configure your firewall ports and an antivirus exception — Intuit notes it can’t give steps for third-party antivirus.
Locally: restore a backup or use Auto Data Recovery, then escalate
Restore a backup copy to test whether the current .QBW is the problem — first make sure the computer isn’t hosting (File → Utilities → Stop Hosting Multi-User Access, if listed) and that the file path is under 210 characters. If the file is damaged, Intuit points to QuickBooks Auto Data Recovery. If the error survives all of this, stop and book a diagnostic; continued retries can mask deeper damage.
Where the Error 6000 steps come from.
The causes and steps above follow Intuit’s own support article, linked below so you can check them at the source. Where this page and Intuit’s article ever differ, follow Intuit.
- Fix error -6000 when opening a company file in QuickBooks — Intuit QuickBooks support
Three signals it’s a ProAdvisor call.
It persists after every step
You’ve worked Intuit’s steps and the Error 6000 still blocks the file. What’s left can be the network or hosting setup, or the company file itself.
It keeps coming back
The Error 6000 clears, then returns. A repeat means something in the setup, the security software or the file keeps breaking, and a one-time fix only masks it.
A specific suffix won’t clear
A 6000-series code with a stubborn suffix that survives Intuit’s steps points to deeper company-file or hosting problems. The moment to stop self-fixing and have the file assessed.
When Error 6000 is no longer a software problem.
Error 6000 is a family of file-access errors. When the file opens again, the software problem is over; what you find in the file is a bookkeeping question.
- The file you opened is an older copy or a restore.
- Recent weeks of transactions are missing or were entered twice.
- Reconciled months no longer tie.
Start with the free QuickBooks file review — a limited review that identifies likely issues and the information needed for a written scope, with the findings in plain English. If the findings show that the books themselves need work, that is QuickBooks cleanup, quoted as a fixed fee against a written scope before any work starts.
Self-fix didn’t clear Error 6000?
A QuickBooks ProAdvisor diagnoses the deeper cause — a focused diagnostic is from $1,200 — a fixed fee, set after scoping.
Certified QuickBooks ProAdvisor credentials.
2
Intuit certifications held — QuickBooks Online (Level 2) and Payroll; Desktop and Enterprise files worked in
L2
QuickBooks Online ProAdvisor tier
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.
- We work in Desktop and Enterprise files, led by TechBrot’s founder; Intuit’s public ProAdvisor directory lists active ProAdvisors for verification.
- Operational experience to diagnose the specific 6000 suffix past Intuit’s documented steps — not a script-reading queue.
A QuickBooks ProAdvisor diagnoses past the surface.
When Intuit’s steps don’t hold, what’s left is past the surface — a network-data (.ND) or transaction-log (.TLG) file that keeps breaking, a hosting setup that won’t stay on one computer, a firewall or antivirus that keeps blocking access, folder permissions, or damage to the company file itself. A QuickBooks ProAdvisor who works in Desktop and Enterprise files diagnoses the actual root cause behind the specific 6000 suffix, fixes it against a written scope, and verifies the file opens cleanly before closing.
Diagnostic
30-minute diagnostic, scheduled within one business day
What people ask about Error 6000.
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 call scopes the real cause — a focused diagnostic is from $1,200 — a fixed fee, set after scoping. Written scope before any work begins.