QuickBooks 6000-Series: the file-access & integrity errors.
Intuit says -6000 errors come with a message that you can’t open your company file — but its articles for specific codes point in different directions: file access (6000-77, 6000-83), a multi-user network issue “not with your data file” (6189, 6190), or possible file damage (6000-301). Below: what Intuit says for each code, its general fix steps in order, and when to escalate.
6000-series errors are QuickBooks Desktop errors that, in Intuit’s words, come with a message that says you can’t open your company file. Intuit’s code-specific articles sort them three ways: file access (-6000, -77: QuickBooks can’t access the file; -6000, -83: backup, restore or server situations); multi-user network (6189 / 6190, 816: “not with your data file”); and possible file damage (-6000, -301: damaged support files, a damaged company file, or encryption software). Intuit’s general steps: update QuickBooks, run File Doctor, rename .ND and .TLG, open a sample file, copy the file to the Desktop, then restore a backup or use Auto Data Recovery.
Published by TechBrot.
The 6000-series, in five questions.
What are 6000-series errors?
QuickBooks Desktop errors that, in Intuit’s words, come with a message that says you can’t open your company file. They usually carry 3 or 4 more digits — for example -6000, -77, -6000, -83, -6000, -301, 6189, 816 and 6190, 816 — and can happen on local or network setups.
Three buckets, three responses.
Grouped by what Intuit’s own articles say: file access (-6000, -77 — QuickBooks can’t access the file; -6000, -83 — backup, restore or server situations); multi-user network (6189 / 6190, 816 — “not with your data file”); possible file damage (-6000, -301 — damaged support files, a damaged company file, or encryption software).
The universal first-pass?
Intuit’s general -6000 steps: (1) update QuickBooks to the latest release; (2) run File Doctor from the Tool Hub; then for a local file, rename .ND and .TLG, open a sample company file, copy the file to the Desktop, and restore a backup or use Auto Data Recovery. Hosted files add hosting, Database Server Manager, permission and firewall checks.
When self-fix won’t be enough?
When Intuit’s steps for your code haven’t cleared it; the error comes back; File Doctor finds damage it can’t repair; restoring a backup would lose work you can’t re-enter; or several different codes appear together.
Desktop or Online?
6000-series errors are QuickBooks Desktop, Premier, and Enterprise errors — Intuit’s articles are all QuickBooks Desktop articles. QuickBooks Online has no company file for QuickBooks to open.
The 6000-series, plainly.
Intuit describes -6000 errors this way: they “can happen on both local and network setup,” usually carry “3 or 4 more digits,” and come with a message that says you can’t open your company file. Intuit’s own articles for specific codes point in different directions. -6000, -77 means QuickBooks Desktop can’t access the company file. -6000, -83 is handled by situation — creating a backup, restoring one, or a file on a Windows or Linux server. 6189, 816 and 6190, 816 are, in Intuit’s words, “an issue with your multi-user network, not with your data file.” -6000, -301 can come from damaged support files (.TLG, .ND, .DSN), a damaged company file, or encryption software.
Intuit’s general fix for -6000 errors starts with updating QuickBooks and running File Doctor from the Tool Hub, then works through renaming the .ND and .TLG files, opening a sample file, copying the file to the Desktop, and restoring a backup or using Auto Data Recovery — with extra network steps for hosted files. Some codes people search for, such as -6000, -80, have no current Intuit article at all. 6000-series errors are QuickBooks Desktop, Premier, and Enterprise errors; QuickBooks Online has no company file to open. When Intuit’s steps have run out, a focused diagnostic is from $1,200 — a fixed fee, set after scoping.
Identify which 6000 bucket you’re in.
These groupings follow what Intuit’s own articles say about each code. Knowing the group tells you which Intuit article to follow. Each code gets dedicated detail below.
Bucket 1 · File access
-6000, -77 and -6000, -83. Intuit says -6000, -77 happens when QuickBooks Desktop can’t access the company file; its steps deal with administrator rights, external storage, mapped drives, firewalls and folder permissions. Intuit handles -6000, -83 by situation — creating a backup, restoring a backup, or a company file on a Windows or Linux server.
Bucket 2 · Multi-user network
6189, 816 and 6190, 816. Intuit calls these “an issue with your multi-user network, not with your data file.” Its steps: Quick Fix my Program, restart the server and every workstation, run the Database Server Manager, and keep company files on the server’s local hard drive.
Bucket 3 · Possible file damage
-6000, -301. Intuit lists three causes: damaged QuickBooks support files (.TLG, .ND or .DSN), a damaged company file, or installed encryption software. Its steps: update QuickBooks, rename the support files, run File Doctor, and deal with any encryption software through its vendor.
Other codes · Intuit’s general -6000 table
Codes such as -6147, 0 and -6000, -832 appear only in the table in Intuit’s general -6000 article, with no separate definition. Use the general steps below. We found no current Intuit article for -6000, -80.
The general fix Intuit gives for -6000 errors.
These are the steps in Intuit’s general -6000 article (updated August 5, 2026), in Intuit’s order. If they don’t clear it, follow your code’s own Intuit article; if that doesn’t either, self-fix has reached its limit.
Update QuickBooks to the latest release
Intuit’s first step for any -6000 error: make sure QuickBooks Desktop is updated to the latest release.
Run QuickBooks File Doctor
Download the latest QuickBooks Tool Hub from Intuit. Open Tool Hub → Company File Issues → Run QuickBooks File Doctor, select your company file, choose Check your file, and continue.
Rename the .ND and .TLG files
In the folder with your company file (.QBW), find the .ND and .TLG files with the same name and add .OLD to the end of each — e.g., company.qbw.nd becomes company.qbw.nd.OLD. QuickBooks creates fresh ones. If the file is hosted on a server, run the Database Server Manager afterward.
Open a sample company file
Open one of QuickBooks’ sample company files. If the sample opens, QuickBooks itself is working and the problem is with your file or its location; if it doesn’t, the problem is with the QuickBooks installation.
Copy the company file to the Desktop
Copy the company file to the Desktop and open it from there. Intuit uses this to test whether the location is the problem: if the file opens from the Desktop, the folder where you normally keep it may be damaged.
Restore a backup, or use Auto Data Recovery
Restore a recent backup to check whether the current file is damaged, or use Auto Data Recovery to recover it. Restoring means you’ll need to re-enter anything done since that backup.
If the file is on a network, check the network steps
For a hosted file, Intuit adds: check the hosting setting on every workstation (turn off Host Multi-User Access on workstations), close all QuickBooks processes, check the folder permissions, and configure firewall ports and anti-virus software for QuickBooks. For 6189 / 6190, 816 follow Intuit’s multi-user article; cross-reference our H202 reference for multi-user depth.
If the error persists, check your code’s own article & escalate
If Intuit’s general steps didn’t resolve it, look up your exact code — -6000, -77, -6000, -83, -6000, -301 and 6189 / 6190, 816 each have their own Intuit article and steps. If those don’t clear it either, or File Doctor finds damage it can’t fix, a QuickBooks ProAdvisor diagnostic is the appropriate next step.
Each 6000 variant, explained.
If the general steps didn’t resolve your error, the specific code determines next steps. Find yours below for what Intuit says about it.
6000-77 · Error 6000-77
Bucket 1 · File access. Intuit says QuickBooks Desktop can’t access the company file. Its solutions, in order: run QuickBooks as Administrator; move the file off external storage to your computer; run File Doctor; rename the .ND and .TLG files; open the file by its network (UNC) path instead of a mapped drive; adjust firewall and security settings; and create a new folder on C:, set its Windows permissions, and open the file from there.
6000-80 · Error 6000-80
No Intuit article. We found no current Intuit article for -6000, -80, and it isn’t in the code table in Intuit’s general -6000 article. Use the general -6000 steps above; be wary of code-specific explanations for it that Intuit doesn’t publish.
6000-83 · Error 6000-83
Bucket 1 · File access. Intuit’s article is organised by situation. Creating a backup: save it to a new folder on C: and restore from it. Restoring a backup: remove symbols, special characters and spaces from the backup’s name and folder, try a portable file, or move the backup to a local drive. File on a Windows server: turn off Host Multi-User Access on workstations, run File Doctor, restore a backup, set up the Database Server Manager, and test from the desktop. A Linux server has its own steps.
6189 · Error 6189
Bucket 2 · Multi-user network. Intuit covers 6189, 816 together with 6190, 816: “an issue with your multi-user network, not with your data file.” Its steps: run Quick Fix my Program from the Tool Hub; restart the server and each workstation, opening QuickBooks on the server first; run the Database Server Manager; and move company files to the server’s local hard drive. See the H202 reference for multi-user depth.
6190 · Error 6190 (often paired with -816)
Bucket 2 · Multi-user network. Same Intuit article and steps as 6189, 816. Intuit also says to keep company files off Dropbox, Google Drive, external drives, USB flash drives and NAS devices — on the server’s local hard drive instead.
6000-301 · Error 6000-301
Bucket 3 · Possible file damage. Intuit lists damaged support files (.TLG, .ND, .DSN), a damaged company file, or installed encryption software. Its steps: update QuickBooks; rename the .TLG, .ND and .DSN files by adding .OLD; run File Doctor; and if encryption software is installed, work with its vendor to disable it. See the dedicated 6000-301 page.
6147 · Error 6147
Intuit’s general table. Intuit lists -6147, 0 in the code table of its general -6000 article and gives no separate definition. Follow the general steps above — update QuickBooks, File Doctor, then the local or network solutions.
6000-832 · Error 6000-832
Intuit’s general table. Intuit lists -6000, -832 in the code table of its general -6000 article and gives no separate definition. Follow the general steps above, including the network steps if the file is hosted.
Where the 6000-series steps come from.
The causes and steps above follow Intuit’s own support articles, linked below so you can check them at the source. Where this page and Intuit’s articles ever differ, follow Intuit.
- Fix error -6000 when opening a company file in QuickBooks — Intuit QuickBooks support
- Error: -6000, -77 when opening a company file — Intuit QuickBooks support
- How to fix Error 6000, -83 — Intuit QuickBooks support
- Error -6000, -301: An error occurred when QuickBooks tried to access the company file — Intuit QuickBooks support
- Fix error 6189, 816 and 6190, 816 in QuickBooks Desktop — Intuit QuickBooks support
Three signals you’re past self-fix.
Intuit points to a damaged file
File Doctor reports damage it can’t repair, or Intuit’s -6000, -301 steps leave “a damaged company file” as the remaining cause. Restoring a backup means re-entering everything since — a diagnostic sets out the best file to work from and what it will take.
The error persists after the first-pass
You updated QuickBooks, ran File Doctor, renamed the .ND and .TLG files, tried a sample file and the Desktop copy, and followed your code’s own Intuit article — and the error is still appearing. The next step isn’t more guessing; it’s a diagnostic that identifies the actual root cause.
Multiple 6000-variants, or with other errors
If you’re seeing different 6000 codes at different times, or 6000-series alongside H-series, unrecoverable, or C-series errors, each has its own Intuit steps and the pattern matters more than any one code. A single diagnostic — or a full QuickBooks file cleanup — beats iterative single-error troubleshooting.
When a 6000-series error is no longer a software problem.
Every 6000-series error is about reaching or opening the company file. When the file opens, that part is solved — what is inside it is a separate question.
- You got in by restoring a backup or switching to a copy.
- Work from the days around the error is missing or duplicated.
- Reconciled months no longer tie to the statements.
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.
First-pass didn’t clear the 6000 error?
A QuickBooks ProAdvisor finds the real 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
- The 6000-series spans file-location, multi-user network and file-damage problems — matching the exact code to the right Intuit article, and knowing when those steps have run out, is the experience that matters here.
- The firm is led by TechBrot’s founder with active QuickBooks Online (Level 2) and Payroll certifications who works in Desktop and Enterprise files; Intuit’s public ProAdvisor directory lists active ProAdvisors for verification.
- When Intuit’s steps point to a damaged company file, we work from the backups and records you have against a written scope — not a script-reading queue.
When Intuit’s steps have run out.
Intuit’s articles take you a long way: update, File Doctor, rename the helper files, test with a sample file and a Desktop copy, then restore a backup or use Auto Data Recovery. When those steps don’t clear the error — or they point to a damaged company file and restoring would lose work you can’t easily re-enter — the right move is a QuickBooks ProAdvisor diagnostic that identifies the actual state of the file and scopes the work in writing.
The firm is led by TechBrot’s founder with active QuickBooks Online (Level 2) and Payroll certifications who works in Desktop and Enterprise files. A focused diagnostic is from $1,200 — a fixed fee, set after scoping; written scope, no hourly billing. When multiple variants point to broader integrity issues, a QuickBooks file cleanup is the right engagement.
ProAdvisor
certified in Online (Level 2) and Payroll
Diagnostic
30-minute call, scheduled within one business day
What people ask about 6000-series errors.
Is this official QuickBooks support?
What are QuickBooks 6000-series errors?
What causes QuickBooks Error 6000-77?
What causes QuickBooks Error 6000-301?
What’s the difference between Error 6189 and Error 6190?
Can I fix QuickBooks 6000-series errors myself?
.ND and .TLG files, opening a sample company file, copying the file to the Desktop, and restoring a backup or using Auto Data Recovery — with hosting, Database Server Manager, permission and firewall checks for networked files. Specific codes (-6000, -77, -6000, -83, -6000, -301, 6189 / 6190, 816) have their own Intuit articles. If those steps don’t clear it, the error comes back, or File Doctor finds damage it can’t repair, that’s the point to bring in a QuickBooks ProAdvisor.When does a 6000-series error require a ProAdvisor?
Do 6000-series errors occur in QuickBooks Online?
6000-series resolution starts here
Intuit’s steps didn’t clear it? Book a diagnostic.
If Intuit’s general steps and your code’s own article didn’t resolve your 6000-series error, or File Doctor found damage it couldn’t repair, book a 30-minute QuickBooks ProAdvisor call. We identify the actual state of the file and scope the work in writing. A focused diagnostic is from $1,200 — a fixed fee, set after scoping.