QuickBooks Error 6000, 80

Let’s Dive in to see…

How to Fix QuickBooks Error=6000, 80

Schedule a call to fix QuickBooks Errors
QuickBooks Payroll Error PS060

QuickBooks Company File Error · 6000 Series

How to Fix QuickBooks Error 6000, 80

QuickBooks displays: "Error -6000, -80: An error occurred when QuickBooks tried to access the company file"

The -80 sub-code in the 6000 series points to a company file data problem — the file itself is damaged, unreadable, or hosted incorrectly. At QuickFix Bookkeeping, the first diagnostic question is: can you open the file on the server locally? If yes — it's a network or hosting issue. If not — the file itself has damage that needs repair.

The QuickFix Bookkeeping Distinction — What -80 Specifically Means vs Other 6000 Sub-Codes

The 6000 series sub-code tells you which layer failed. Applying the wrong fix wastes time — the sub-code is the diagnostic.

-80 — this page

Company file data is damaged or unreadable, or multiple computers are hosting simultaneously. File Doctor + Verify/Rebuild.

-77

Network path issue — file accessed via mapped drive instead of UNC path. Fix: use UNC path (\\server\share\file.qbw).

-82

File open in single-user while others try multi-user. Fix: have that user switch to multi-user mode.

-83

File permissions or deeper file damage. Fix: folder permissions + File Doctor + Rebuild.

Two causes specific to -80:

1. Company file name too long or contains special characters: QB Desktop has a 32-character limit on company file names. If the name exceeds this or contains unsupported characters (%, #, &, etc.), QB cannot reliably read the file and reports -80. Renaming the file to under 32 characters with only letters, numbers, and underscores resolves this immediately.

2. Multiple computers configured as hosts: If more than one machine has "Host Multi-User Access" enabled, they compete to manage the company file — producing -80 as the file appears locked and damaged from each machine's perspective. Only the server should host.

What Causes QuickBooks Error 6000, 80?

Damaged or Corrupted Company File

Primary cause — the .QBW company file has internal data damage. This can result from an abrupt QB shutdown, a disk write error, a power failure during a save, or a disk drive with bad sectors. QB detects the damage when it tries to read the file and reports -80. File Doctor and Verify/Rebuild are the remedies.

Multiple Hosts Competing for the Company File

More than one computer has "Host Multi-User Access" enabled. Each tries to manage the file simultaneously — they block each other's access and the file appears inaccessible. The fix is to disable hosting on all workstations and leave it enabled only on the designated server.

Company File Name Too Long or Has Special Characters

QB Desktop enforces a 32-character limit on company file names. Names with special characters (%, #, &, @, spaces, etc.) also cause access failures. If the name violates these rules, QB reports -80 when trying to read it. Renaming the file within limits resolves this without any other troubleshooting.

File Restored or Converted Over a Network

QB requires that company files be restored or upgraded on a local drive — not directly over a network share. Restoring a backup (.QBB) or converting to a newer QB version while the file is on a network location causes data inconsistency and produces -80. Always restore/convert locally first, then move the file to the server.

QB Cannot Communicate with the Server

Network interruptions — firewall blocking QB ports, QBDSM not running, or an unstable connection — prevent QB from maintaining a reliable connection to the company file. The intermittent read failures register as -80. Firewall exceptions for QB and a QBDSM scan resolve the network layer.

Damaged .ND or .TLG Support Files

The .ND (network descriptor) and .TLG (transaction log) companion files for the company file are corrupted. QB tries to use these files to access the main .QBW and fails with -80. Renaming both to .OLD forces QB to rebuild them on the next successful open.

How to Fix QuickBooks Error 6000, 80

Check the file name first — if it's over 32 characters or has special characters, that's the fix. Otherwise start with File Doctor.

METHOD 1 Check File Name + Fix Hosting Settings Quick checks — resolve the -80-specific causes first
1

Check file name: navigate to the company file folder. Right-click the .QBW file → Rename. Count the characters. If it exceeds 32 or contains special characters (%, #, &, @, spaces, parentheses), rename it to something short and clean (e.g., CompanyName2024.QBW). Retry opening.

2

Fix hosting: On every workstation — QB → File → Utilities. If "Stop Hosting Multi-User Access" shows → click it (disables hosting on that machine). Repeat until all workstations show "Host Multi-User Access" (hosting off). On the server only — confirm "Stop Hosting Multi-User Access" shows (hosting on). Restart QB on all machines and retry.

METHOD 2 Rename .ND and .TLG Files + Run QBDSM Scan Damaged support files
1

Navigate to the company file folder. Find YourFile.QBW.ND → right-click → Rename → add .OLD. Find YourFile.QBW.TLG → rename → add .OLD. Open QuickBooks Database Server Manager (Start → type Database) → Scan Folders → add the company file folder → Start Scan. QBDSM rebuilds both files with correct current data. Retry opening the company file.

METHOD 3 Copy File to Local Drive + Run File Doctor File damage diagnosis and repair
1

Copy to local drive: Copy the .QBW file to C:\QB\ on the server. Try opening from there. If it opens locally but not from the server — the network path has the problem. If it won't open locally either — the file has data damage.

2

Run File Doctor: Tool Hub → Company File Issues → Run QuickBooks File Doctor → select company file → Check your file and network → Continue → enter admin password → run (10–15 min). File Doctor repairs both file damage and network configuration issues. If it detects damage it cannot repair, restore from your most recent backup.

METHOD 4 Run Verify Data + Rebuild Data File opens but shows errors — data damage repair
1

QB → File → Utilities → Verify Data → wait for completion. If issues found → File → Utilities → Rebuild Data → OK (QB will prompt a backup — do it) → let run → click OK when done → run Verify Data again to confirm. If Verify still reports damage after Rebuild, the corruption is too severe for Rebuild to fix — restore from backup.

METHOD 5 Restore from Backup or Use Auto Data Recovery File Doctor and Rebuild unable to repair damage
1

Restore backup: File → Open or Restore Company → Restore a backup copy → Local backup → browse to your .QBB file → restore to local drive → recheck. Auto Data Recovery (ADR): QB automatically creates an ADR copy of the company file. Navigate to C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\ and look for a folder named QuickBooks Auto Data Recovery. Follow Intuit's ADR guide to recover transactions from the ADR copy into a healthy restored backup. ADR can recover up to 12 hours of transactions that were not in the last backup.

Quick Reference

Your situation Likely cause Start with
File name has special characters or is over 32 characters File name violation Method 1 — rename the file
Multiple workstations all have hosting enabled Hosting conflict Method 1 — fix hosting settings
File won't open — first occurrence after normal use Damaged .ND/.TLG or file data Methods 2 + 3 — rename support files + File Doctor
File Doctor can't repair — severe data damage Corrupted company file data Method 5 — restore from backup

Frequently Asked Questions

Why does the company file name length cause Error 6000, 80?
QuickBooks Desktop has an internal limitation on file name lengths and character sets inherited from its database engine. The 32-character limit applies to the file name portion only (not the full path). File names exceeding this length or containing special characters cause the QB database engine to fail when constructing internal file references — producing error -80. This is separate from the Windows file system limit (260 characters for the full path). The fix is simply renaming the file to comply with QB's internal limit.
Can I restore a company file over a network or must it be done locally?
It must be done locally. Intuit explicitly requires that company file restoration (.QBB to .QBW) and version upgrades be performed on the local hard drive, not over a network share. The restoration process writes large amounts of data rapidly and requires direct disk access — over a network, packet loss or write delays cause data inconsistency in the restored file, often producing error -80 on first open. The correct process: copy the .QBB to the local C: drive, restore there, verify the file opens correctly, then move the restored .QBW to the server and run a QBDSM scan.
What is Auto Data Recovery and when should I use it?
QuickBooks Auto Data Recovery (ADR) is a built-in feature that automatically creates a copy of your company file and a transaction log file in the QuickBooks Auto Data Recovery folder. QB updates the ADR copy periodically. If your main company file becomes corrupted and you don't have a recent backup, ADR can help you recover data that occurred after your last manual backup — typically up to 12 hours of transactions. ADR is not a replacement for regular backups — it's an emergency last resort. You should use it when File Doctor cannot repair the damage and your most recent backup is outdated. Intuit's support site has the specific ADR recovery steps, as the process involves combining ADR files in a specific way.

Related QuickBooks 6000 Series Errors

Error 6000, 80 Persisting After File Doctor and Rebuild?

Let QuickFix Bookkeeping Repair Your Company File.

Certified Intuit ProAdvisors — Company File Repair Specialists

Persistent Error 6000, 80 after File Doctor, Rebuild Data, and hosting fix typically points to severe company file data corruption requiring specialist-level data recovery tools beyond Intuit's standard utilities.

Book a Free 30-Minute Consultation

No obligation. Same-day response. Company file repaired fast.