QuickBooks Company File Error Guide
QuickBooks 6000 Series Errors — Complete Guide
You tried to open, restore, or back up your company file — and QuickBooks returned a message that looked something like: Error -6000, -77 or Error -6000, -83 or any other combination with a 6000-series prefix. QuickBooks cannot access your company file.
The 6000 series is the largest single family of errors in QuickBooks Desktop — there are over 27 documented variants. At QuickFix Bookkeeping, we see these errors regularly across client files. This guide does what no other guide does: it tells you exactly what each suffix means so you go straight to the right fix rather than running every method hoping one works.
The QuickFix Bookkeeping Distinction
The suffix after the 6000 is not decoration — it tells you exactly what broke and why.
,
-77
The suffix — this is your diagnostic
Every 6000-series error follows this format. The first number (6000, 6147, 6150, 6189 etc.) identifies the error family. The suffix (-77, -83, -304, -816 etc.) identifies the specific cause. Find your suffix in the decoder table below and you will know exactly which fix to run first.
Note your full error code — both the primary number and the suffix — before reading further. If you only see "-6000" with no suffix, scroll to the general fixes section below.
What All 6000-Series Errors Have in Common
They all mean
QuickBooks cannot access the company file
Whether opening, restoring, backing up, or switching modes — 6000 series errors are all company file access failures.
Three root causes behind the entire family
A
File access problem — wrong location, corrupted file path, file on external or network drive that cannot be reached, or the company file itself is damaged.
B
Network or hosting problem — firewall blocking QuickBooks, incorrect multi-user hosting configuration, QuickBooks Database Server Manager not running, or multiple machines hosting the same file.
C
Permissions problem — the Windows user account does not have sufficient rights to open or modify the company file folder, or the folder sharing permissions are incorrectly set.
6000-Series Error Decoder — Find Your Code
Locate your full error code in the table below. The suffix column is your starting point for the right fix.
| Error Code |
What it specifically means |
Root cause |
Start with |
| -6000, -77 |
Company file not found — stored on external or network drive that QuickBooks cannot reach, or file path has changed |
File access (A) |
Copy file locally and open from C:\ |
| -6000, -80 |
Company file is damaged or too large — QuickBooks encounters an error when reading the file content |
File access (A) |
Rename .ND/.TLG, then Verify & Rebuild |
| -6000, -82 |
File access failed in multi-user mode — QuickBooks cannot communicate with the file on another computer |
Network (B) |
Run Database Server Manager, check firewall |
| -6000, -83 |
Insufficient permissions — user account does not have full rights to the network server or company file folder |
Permissions (C) |
Set folder permissions to Full Control |
| -6000, -301 |
Encryption software conflict — company file is stored in same location as third-party encryption software |
File access (A) |
Move company file to unencrypted folder |
| -6000, -304 |
File in use or locked — another user or process has an exclusive lock on the company file |
Network (B) |
Have all users log out, restart QuickBooks |
| -6000, -816 |
File already open — QuickBooks is trying to open a file that is already in use by another instance or user |
Network (B) |
Restart server, kill QuickBooks processes |
| -6000, -832 |
Transaction log / .TLG file mismatch — the .TLG file does not match the .QBW company file |
File access (A) |
Rename .ND and .TLG files to .OLD |
| -6147, 0 |
Backup file damaged — restoring from a backup that is incomplete or corrupted |
File access (A) |
Use a different backup; run File Doctor |
| -6150, -1006 |
Company file infected or corrupted — damaged file or QuickBooks installation conflict |
File access (A) |
Run File Doctor; malware scan |
| -6189, -77 |
Single-user mode conflict — another user is accessing the file while single-user mode is active |
Network (B) |
Have all users log out completely |
| -6073, -816 |
File already open on another machine — multi-user session not properly closed |
Network (B) |
Restart QuickBooks Database Server Manager |
| -6123, 0 |
Disconnected from server during operation — network connection dropped mid-session |
Network (B) |
Check network stability; restart server |
Universal Fixes — Works Across the Entire 6000 Family
These five methods resolve the majority of 6000-series errors regardless of which specific code you are seeing. Work through them in order after identifying your root cause from the decoder table.
FIX 1
Copy the Company File to a Local Drive and Open It
Try first — diagnoses in 2 minutes
This is the fastest diagnostic step. If your company file opens when copied locally but not from its normal location, the issue is network or path-related — not the file itself. This rules out file damage and points directly to Fix 3 or Fix 4.
1
Navigate to your company file location. Right-click the .QBW file and select Copy. Paste it directly to your Desktop or C:\Users\Public\Documents.
2
Open QuickBooks, hold Ctrl while double-clicking the icon to get to No Company Open. Select Open or restore an existing company → Open a company file and navigate to the Desktop copy.
3
Opens cleanly? → The original location has a path, network, or permissions issue. Move the file to the recommended location: C:\Users\Public\Documents\Intuit\QuickBooks\Company Files.
Still errors? → The file itself has damage. Move to Fix 2.
FIX 2
Rename .ND and .TLG Files to Force Recreation
Safe — no data lost
The .ND and .TLG files are configuration and transaction log files that sit alongside your company file. When corrupted or mismatched, they cause 6000-series errors consistently. Renaming them forces QuickBooks to recreate them fresh. This is one of the most reliable fixes in the entire 6000 family.
1
Navigate to the folder containing your company file. Look for files with the same name as your .QBW file but with .ND and .TLG extensions.
2
Right-click each file → Rename → add .OLD to the end of each filename. Example: CompanyName.ND becomes CompanyName.ND.OLD.
3
Reopen QuickBooks and open the company file. QuickBooks will recreate both files automatically. If the error clears — the old files were corrupted or mismatched.
FIX 3
Run QuickBooks File Doctor
Covers file damage + network issues
QuickBooks File Doctor is Intuit's primary diagnostic tool for 6000-series errors — it checks both company file integrity and network connectivity simultaneously, repairing what it can automatically.
1
Download and install QuickBooks Tool Hub from Intuit's official website. Open it and go to Company File Issues.
2
Select Run QuickBooks File Doctor. Find your company file in the dropdown or browse to it. Select Check your file and network and enter the admin password when prompted.
3
Wait for the scan to complete — 10 to 20 minutes depending on file size. Restart your computer afterwards and test. As with other QB tools, even an "unsuccessful" result sometimes resolves the error — always test after running regardless of the outcome message.
FIX 4
Fix Network Hosting and QuickBooks Database Server Manager
For multi-user -82, -304, -816 errors
Network-related 6000 errors (-82, -816, -304, -6123) are almost always caused by hosting misconfiguration or the QuickBooks Database Server Manager not running correctly on the host computer. This fix addresses both.
1
Check hosting: On every workstation (not the server), open QuickBooks → File → Utilities. Confirm it says Host Multi-User Access — not Stop Hosting Multi-User Access. If any workstation shows Stop Hosting, click it to disable hosting on that machine. Only the server should host.
2
Restart Database Server Manager: On the host server, open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager. Click Start Scan. Let it complete.
3
Ensure the QuickBooksDBXX Windows service is running on the host. Go to Windows Services (services.msc), find QuickBooksDB and set it to Automatic start. Restart it if it is stopped.
QuickFix tip: Multiple machines hosting the same company file simultaneously is the single most common cause of -6000 -82 and -816 errors in multi-user setups. Even one workstation accidentally set to host can cause persistent 6000 errors for every other user. Check all machines — not just the server.
FIX 5
Set Correct Folder Permissions and Disable Firewall Temporarily
For -83, permissions errors
Permissions errors (-6000 -83) require setting the company file folder to Full Control for all relevant user accounts — and temporarily disabling the firewall to determine if it is blocking QuickBooks' network communication.
1
Right-click the folder containing your company file → Properties → Security → Edit. For each user account listed, ensure Full Control is ticked. Click Apply → OK.
2
Also ensure the QBDataServiceUserXX account (created by QuickBooks) has Full Control on the folder. This is the account the Database Server Manager uses — if it lacks permission, multi-user access will always fail.
3
To test firewall: temporarily disable Windows Firewall and attempt to open the file. If it opens — add QuickBooks exceptions to the firewall permanently (ports 8019, 56728, 55378-55382) rather than leaving it disabled.
Frequently Asked Questions About 6000-Series Errors
Is my company file data at risk when I get a 6000 error?
In most cases, no. The majority of 6000-series errors are access failures — QuickBooks cannot reach or open the file, but the file itself is intact. The exceptions are errors like -6000 -80 and -6150 -1006 which specifically indicate file damage, and -6147 which means the backup file you are trying to restore is corrupted. For these, the underlying data may need repair. Back up before troubleshooting and use QuickBooks File Doctor before any data repair steps.
Why am I getting a 6000 error on a file stored locally — not on a network?
Local 6000 errors are less common but do occur. The most frequent causes are: the company file name contains special characters or extra spaces, the file path is too long (Windows has a 260-character path limit), the file is stored in a folder synced by OneDrive or Dropbox (these create conflicts with QuickBooks' lock file mechanism), or the .ND and .TLG files are corrupted. The fix is almost always to rename the .ND and .TLG files and move the company file to the standard QuickBooks company files folder.
Can I store my QuickBooks company file in OneDrive or Dropbox?
No — and this is one of the most common causes of 6000-series errors we see at QuickFix Bookkeeping. OneDrive, Dropbox, and Google Drive continuously sync files in the background. QuickBooks uses a file locking mechanism that conflicts with cloud sync clients — producing 6000 errors, data corruption, and in some cases silent data loss. Store your company file locally and use QuickBooks' own backup feature to maintain copies. If remote access is needed, use a proper QuickBooks hosting solution.
How do I prevent 6000-series errors from recurring?
Three practices eliminate most recurring 6000 errors. First, store the company file in the standard QuickBooks location — not on external drives, network shares with mapped drive letters, or cloud sync folders. Use UNC paths (\\ServerName\ShareName\) rather than mapped drive letters for network access. Second, in a multi-user setup, ensure only one machine — the server — has hosting enabled, and that the QuickBooksDB service is set to start automatically. Third, close QuickBooks properly rather than force-closing it — an improper shutdown is a frequent cause of .TLG file mismatches that trigger -832 errors.
Specific 6000-Series Error Guides
Need a deep-dive on a specific variant? These pages cover the most commonly searched 6000-series codes in detail:
Company File Locked Out?
Can't Get Into QuickBooks.
Let's Fix That Today.
Certified Intuit ProAdvisors · QuickBooks Desktop Specialists
A 6000-series error that persists after the standard fixes almost always points to a network configuration or file integrity issue that needs hands-on diagnosis. At QuickFix Bookkeeping, we resolve company file access errors for businesses across the US in a single session — identifying the exact cause and applying the right fix without putting your financial data at risk.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Your company file accessible today.
