QuickBooks Error 6000 Series (-6000 -82, -301, -77, -83): Fix Company File Errors

You go to open your company file and QuickBooks throws a -6000 error — usually a pair of numbers like -6000, -82 or -6000, -301. It looks scary, but the whole 6000 series means one thing: QuickBooks can’t properly access the company file. The data is almost always fine — the path to it is what’s broken.

Here’s what each common variant points to, and the fix order that resolves the most cases with the least risk.

What the second number tells you

Code	Usual cause
-6000, -82 / -6000, -106	Damaged .ND/.TLG config files, or a space in the file name
-6000, -301	Company file or its network path is damaged
-6000, -77	File is on an external/mapped network drive QuickBooks can’t reach correctly
-6000, -83	Hosting/permissions problem on the server folder
-6123, 0	Network connection to the company file was lost (often after an update)

The fixes below are ordered safest-first. Stop as soon as your file opens.

Fix 1: Rename the .ND and .TLG files (fixes most -82 / -106)

These two helper files (same name as your company file, but ending in .ND and .TLG) tell QuickBooks how to reach the file on a network. When they corrupt, you get 6000 errors — and QuickBooks rebuilds them automatically, so renaming them is safe.

1. Open the folder that holds your company file (the .qbw).
2. Find the files with the same name but extensions .ND and .TLG.
3. Right-click each → Rename → add .OLD to the end (e.g. MyCompany.qbw.ND.OLD).
4. Reopen QuickBooks and try your file. QuickBooks recreates the files fresh.

For -6000, -82 specifically: also check the company file name itself for a space between the name and the .qbw extension (e.g. MyCompany .qbw). Remove it.

Fix 2: QuickBooks File Doctor (via Tool Hub)

If renaming didn’t do it, run Intuit’s repair tool. (Full walkthrough: QuickBooks Tool Hub guide.)

1. Close QuickBooks → install the QuickBooks Tool Hub.
2. Open it → Company File Issues → Run QuickBooks File Doctor.
3. Pick your company file from the drop-down (or Browse) → Check your file → Continue.
4. Enter your admin password. The scan runs 10–20 minutes on large files.

Fix 3: Move the file locally (fixes -6000, -77)

The -77 variant almost always means the file lives on an external drive or mapped network drive. Copy the .qbw to your local C:\ drive (e.g. C:\QuickBooks\), open it from there, and confirm the error clears. If it does, the problem was the drive path or its permissions — not your data.

Fix 4: Multi-user setups — check the server

If the error only appears on workstations (not the computer hosting the file), this is really a hosting/connectivity issue. The fix sequence is the same one used for Error H202: run Database Server Manager on the server, confirm only the server is hosting, and check firewall permissions.

Fix 5: Restore a backup (last resort)

If File Doctor reports damage it can’t repair, restore your most recent .qbb backup (File → Open or Restore Company → Restore a backup copy). This is why daily backups matter — keep them on a separate drive.

A note for 2023-and-older users

If you’re on QuickBooks Desktop 2023 or earlier, remember the software was discontinued on May 31, 2026. 6000 errors are still fixable with the steps above (they’re local file issues, not service issues), but you’ll no longer get Intuit support for them.

FAQ

Did I lose my data? Almost certainly not. 6000 errors are about access to the file, not the contents. Renaming .ND/.TLG and running File Doctor recover the file in most cases.

It worked yesterday and nothing changed. A Windows or QuickBooks update commonly resets network permissions or breaks the .ND file — that’s “something changed” even if you didn’t change it.

Should I just reinstall QuickBooks? Not first — reinstalling rarely fixes 6000 errors because the problem is the file path, not the program. Try Fixes 1–3 first.

Sources: Intuit — Fix error -6000 when opening a company file, Intuit — Error -6000, -82 or -6000, -106