QuickBooks Company File Error Guide · 6xxx Series
How to Fix QuickBooks Error 6000 83
QuickBooks cannot access the company file and displays: "An error occurred when QuickBooks tried to access the company file. Error codes: (-6000, -83)"
The -83 sub-code means QuickBooks found the file but cannot read it — either the path is wrong or inaccessible, the file has a bad extension or special characters in the name, or the file data itself is damaged. At QuickFix Bookkeeping, the first step is always checking the path and filename — this costs 30 seconds and resolves a significant portion of -83 errors immediately.
The QuickFix Bookkeeping Distinction
Error 6000-83 fires in three different scenarios — and the fix priority is different for each. Most guides ignore the scenario and send everyone through the same steps.
Opening a File
Can't open company file. Most common.
Check path, then hosting settings, then File Doctor.
Creating a Backup
Backup fails with -83.
Save backup to local C: drive first — not network. Fixes this in most cases.
Restoring a Backup
Restore fails with -83.
Check .QBB filename for special characters and spaces before restoring.
How -83 differs from -82 and -77: The three most common 6000 sub-codes each mean a different access failure. -82 = file is locked (single-user conflict or stale lock file — file is fine, access is blocked). -83 = file found but unreadable (wrong path, bad filename, wrong extension, or file is damaged). -77 = network permission failure (file is on the server but QB can't reach it). Apply the -83 fixes in this order: path/filename → local test → hosting → File Doctor → Verify/Rebuild. Applying -82 fixes (lock file, hosting) to a -83 error wastes time because the problem is not a lock — it's the file itself.
What Is QuickBooks Error 6000 83?
Error code
6000, -83
6xxx Series · Company File
Related: -6000 -82 · -6000 -77 · -6150
What it means
Error 6000-83 means QuickBooks located the company file but cannot open or read it. The -83 sub-code points to a file accessibility or data problem — either the file path is too long or contains unsupported characters, the file is stored somewhere QB can't reliably access (network share, NAS, cloud sync folder), the file extension is wrong, or the file data is damaged.
Your data is likely recoverable. In most -83 cases, the file exists and is not destroyed — it's a path or accessibility issue, not catastrophic data loss. Work through the methods below before concluding the file is unrecoverable.
What Causes QuickBooks Error 6000 83?
📁
Wrong or Inaccessible File Path
Most common cause — the company file is on a network share that has become disconnected, a mapped drive that changed, or a NAS/cloud sync folder that QB cannot reliably access. Copy the file to a local C: drive path and try opening it there first.
✏️
Special Characters or Spaces in Filename
The company file name or the folder path contains symbols (&, #, @, %), spaces adjacent to the extension, or non-English characters. QuickBooks cannot reliably parse these paths and returns -83. Rename the file removing all special characters.
💾
Damaged Company File
The .QBW file has internal data damage — common after a power failure mid-write, a failed update, or a file that grew very large without regular Verify/Rebuild maintenance. File Doctor and Verify/Rebuild address this.
🔗
Wrong File Extension
File is .QBB (backup), .QBM (portable), or .QBW.adr (auto-backup version) but QB is trying to open it as a .QBW company file. Backup files must be restored, not opened directly. Portable files must be converted.
🖥️
Multiple Computers Hosting
More than one computer has "Host Multi-User Access" enabled, creating conflicting file access. Each workstation competing to host the file produces -83 because the file's authoritative location becomes ambiguous.
🔐
Insufficient Folder Permissions
The QBDataServiceUser account or the logged-in Windows user does not have Read/Write/Create/Delete permissions on the folder containing the company file. Common after a server migration or OS reinstall.
How to Fix QuickBooks Error 6000 83 — Step by Step
Start with Method 1 — verifying the path and filename costs 30 seconds and resolves many -83 errors before any tools are needed.
METHOD 1
Verify the File Path and Filename
30 seconds — do this before anything else
A large proportion of -83 errors trace back to the file path or name. Check both before running any diagnostic tools.
1
Open File Explorer and navigate to the folder containing the company file. Check the full path — it should be simple (e.g. C:\QB\CompanyName.QBW). If the path is a long UNC network path, a mapped drive letter, or goes through a NAS or cloud sync folder — move the file to a local path first.
2
Check the filename — right-click the .QBW file → Rename. Look for: special characters (&, #, @, %), spaces between the name and .QBW, or non-English characters. Remove anything other than letters, numbers, hyphens, and underscores. Press Enter to save.
3
Check the file extension — it must be .QBW for a company file. If it's .QBB (backup) or .QBM (portable), you cannot open it directly — use File → Open or Restore Company → Restore a backup instead.
QuickFix tip: If Windows is hiding file extensions, you won't see the .QBW — this makes it impossible to check the extension. In File Explorer → View → check File name extensions to show extensions for all files. This also helps spot .QBW.adr files (auto-backup versions) that look like .QBW but cannot be opened the same way.
METHOD 2
Copy the File to a Local Drive and Test
Fastest way to isolate path vs. file damage
If the file is stored on a network share, NAS, or cloud-synced folder — copy it to C:\QB\ on the local computer and try opening it from there. This immediately tells you whether the problem is the file itself or the network path. If it opens locally, the network path is the issue. If it still fails locally, the file data is damaged.
1
Create a folder: C:\QB\. Copy the .QBW file into it.
2
In QuickBooks → File → Open or Restore Company → Open a company file → browse to C:\QB\YourFile.QBW.
3
File opens locally? The network path was the problem — fix the network share permissions or move the file to a supported location permanently. Still -83 locally? The file data is damaged — proceed to Method 4 (File Doctor).
METHOD 3
Fix Hosting — Ensure Only Server is Hosting
Multi-user environment
If you are in a multi-user environment and the file is genuinely on the server, conflicting hosting settings can produce -83. Only the server should host — all workstations should have hosting turned off.
1
On each workstation: File → Utilities. If you see "Stop Hosting Multi-User Access" — click it. If you see "Host Multi-User Access" — the workstation is correctly off, leave it.
2
On the server: File → Utilities → confirm "Stop Hosting Multi-User Access" is shown (hosting is ON). Then run QuickBooks Database Server Manager → Scan Folders on the company file location to regenerate the .ND file.
METHOD 4
Run QuickBooks File Doctor
If file still fails after local test
File Doctor diagnoses and repairs both network configuration issues and minor file data damage. Run it against the local copy of the file (from Method 2's C:\QB\ location) for the most reliable results.
1
Open QuickBooks Tool Hub → Company File Issues → Run QuickBooks File Doctor. Select your company file → Check your file and network → enter admin password → Next.
2
Allow up to 15 minutes. After the scan, try opening the company file. If it opens — immediately run File → Utilities → Verify Data to check for remaining data integrity issues.
QuickFix tip: File Doctor may report "No problems detected" even when it has fixed issues — this is a known quirk of the tool. Always try to open the company file after File Doctor completes regardless of what it reports.
METHOD 5
Verify Data and Rebuild
File opens but data errors remain
If File Doctor allows the file to open but QB shows data warnings or the file still behaves incorrectly, run Verify and Rebuild to address internal data damage that File Doctor cannot repair.
1
File → Utilities → Verify Data. Allow it to complete. Note any errors reported.
2
If Verify reports issues → File → Utilities → Rebuild Data. QB will take a backup before rebuilding. Allow it to complete fully — do not interrupt. Run Verify again after Rebuild to confirm issues are resolved.
METHOD 6
Fix Backup and Restore Specific -83 Errors
If error appears during backup or restore only
If -83 appears when creating a backup:
→
Save the backup to a simple local path — create C:\QBTestFolder\ and save the backup there. Never save directly to a network share, USB drive, or cloud-synced folder during the initial backup attempt. Once the local backup succeeds, copy it to your preferred backup location.
If -83 appears when restoring a backup:
→
Check the .QBB backup filename for special characters, symbols, or spaces. Rename it to a clean name (e.g. CompanyBackup.QBB) before restoring. Also confirm the restore destination folder path is short and local — not a long network path.
Quick Reference — Match Your Situation to the Fix
| Your situation |
Most likely cause |
Start with |
| File stored on network share or NAS |
Inaccessible network path |
Method 2 — copy to local drive first |
| Filename has symbols, spaces, or special characters |
Unsupported filename characters |
Method 1 — clean filename first |
| Multi-user, multiple computers showing error |
Hosting conflict |
Method 3 — fix hosting |
| Fails locally too — file may be damaged |
File data damage |
Method 4 — File Doctor |
| -83 only during backup creation |
Backup destination path issue |
Method 6 — save to C:\QBTestFolder |
| All methods tried — still -83 |
Severe file damage or permissions |
Method 5 + restore from backup |
Frequently Asked Questions
How is Error 6000-83 different from 6000-82?
The sub-code identifies the specific failure point. Error -82 means the file is locked — QB found it and knows where it is, but another session (real or phantom) has it open exclusively. The file data itself is fine. Fix -82 by removing the lock file or ending the blocking session. Error -83 means QB found the file but cannot read it — either the path is inaccessible, the filename is invalid, the extension is wrong, or the file data is damaged. Fix -83 by checking the path, copying locally, and running File Doctor. Applying -82 fixes to a -83 error (looking for lock files) will find nothing because locking is not the problem.
Can I store my QuickBooks company file on a NAS or cloud-synced folder?
Intuit officially does not support storing .QBW files on NAS devices, non-Windows file shares, or cloud-synced folders (Dropbox, OneDrive, Google Drive). These storage locations use non-standard file locking and write-caching mechanisms that conflict with how QuickBooks writes data — producing errors including -83, -6154, and data corruption over time. The supported configuration is a Windows server or a local Windows drive. If you need remote access, Intuit recommends QuickBooks Online or a properly configured Remote Desktop/VPN setup where the file remains on a local Windows drive.
File Doctor says "No problems detected" but the file still won't open — what now?
File Doctor's "no problems detected" message is notoriously unreliable — it reports this even when it has fixed issues, and sometimes when it has failed to identify damage. If the file still won't open after File Doctor, try Verify Data directly (File → Utilities → Verify Data) which has a more granular damage detection engine. If Verify finds errors, run Rebuild. If Verify passes but the file still won't open, the damage is likely structural and beyond what the built-in tools can address — at this point, restore from your most recent backup. If no backup is available, contact a QuickBooks data recovery specialist — do not attempt to manually edit the .QBW file.
Related QuickBooks Company File Errors
Company File Won't Open After All Methods?
Error 6000-83 Persisting?
Let's Recover Your Company File Today.
Certified Intuit ProAdvisors · QuickBooks Data Recovery Specialists
Persistent -83 errors after File Doctor and Verify/Rebuild point to structural file damage that needs specialist recovery. At QuickFix Bookkeeping, our certified ProAdvisors diagnose and recover damaged company files — and get your books back in order.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Company file recovered fast.
