QuickBooks Error 6000, 83: causes & how to fix it.
Error 6000, 83 appears when you open, restore, or back up a QuickBooks Desktop company file. Intuit’s fixes depend on what you were doing and where the file lives — backing up, restoring, a Windows server, or a Linux server. Below: the situations Intuit covers, Intuit’s steps for each, and when to call a QuickBooks ProAdvisor.
Error 6000, 83 appears when you open, restore, or back up a company file in QuickBooks Desktop. Intuit’s current article (updated 8/5/2026) gives fixes by situation: when backing up, back up to a new test folder on C: and restore from it; when restoring, remove special characters from the file and folder names, use a portable company file (.QBM), or move the backup to your local drive; on a Windows server, make the server the only host, run File Doctor, and set up sharing, folder permissions, firewall settings and Database Server Manager. Error 6000, 83 is a QuickBooks Desktop and Enterprise error — it does not appear in QuickBooks Online.
Published by TechBrot.
Error 6000, 83, in five questions.
What is QuickBooks Error 6000, 83?
A QuickBooks company-file error (a 6000-series code, shown as “Error -6000, -83”). Intuit’s article (updated 8/5/2026) says you might see it when you open, restore, or back up your company file, and organises the fixes by what you were doing and where the file is stored. A QuickBooks Desktop and Enterprise error — it does not occur in QuickBooks Online.
What causes Error 6000, 83?
Intuit organises it by situation rather than a single cause: (1) backing up the company file; (2) a backup file or folder name with special characters, symbols or spaces; (3) restoring a backup that sits on a server rather than the local drive; (4) a company file on a Windows server with workstations also set to host, or with sharing, permissions, firewall or Database Server Manager not set up; (5) a Linux server that isn’t configured; (6) a file that isn’t on a server — where Intuit says to contact its support team.
Can I fix Error 6000, 83 myself?
Often, yes — follow Intuit’s steps for your situation: when backing up, back up to a new test folder on C: and restore from it; when restoring, remove special characters from the file and folder names, use a portable company file (.QBM), or move the backup to your local drive; on a Windows server, turn off hosting on the workstations, run File Doctor, then work through Intuit’s sharing, permissions, firewall and Database Server Manager steps.
When does Error 6000, 83 need a ProAdvisor?
When Intuit’s steps for your situation don’t resolve it, the error comes back, your multi-user setup won’t stabilize, or the company file is genuinely damaged — a signal the file or its hosting needs careful repair against a written scope. For a file that isn’t on a server, Intuit says to contact its support team.
How is Error 6000, 83 related to other 6000-series codes?
The 6000-series are all company-file errors — QuickBooks can’t open or access the file. 6000, 83 is tied, in Intuit’s article, to backing up, restoring, and server hosting setup. Intuit’s general -6000 article lists related codes such as -6189, -83 and -6190, -83, which it ties to a company file hosted by a computer that isn’t the server.
Error 6000, 83, plainly.
Error 6000, 83 appears when QuickBooks Desktop can’t complete an open, a restore, or a backup of the company file. Intuit’s current article (updated 8/5/2026) doesn’t give one cause; it sorts the fixes by what you were doing and where the file is stored — backing up, restoring, a company file on a Windows server, or one on a Linux server. If your file isn’t on a server and the error persists, Intuit says to reach out to its support team.
Work through Intuit’s steps for your situation below. If they don’t resolve it, the error comes back, or a multi-user setup won’t stabilize, a QuickBooks ProAdvisor diagnostic looks at what’s left — often the server setup or the company file itself. Error 6000, 83 is a QuickBooks Desktop and Enterprise error; it does not appear in QuickBooks Online.
Six situations Intuit covers.
From Intuit’s current -6000, -83 article (updated 8/5/2026). Intuit doesn’t rank them — find the one that matches what you were doing.
Cause 01 · Backing up the company file
Intuit’s article covers -6000, -83 appearing while you create a backup. Its fix: close QuickBooks Desktop on the server, create a new test folder on the C: drive, back up to that folder, and restore from the new backup.
Cause 02 · Special characters in the backup file or folder name
When restoring, Intuit’s first solution is to check the backup’s file name: remove any special characters, symbols or spaces from the file name, and rename the folder that holds it the same way.
Cause 03 · Restoring a backup from a server or network location
Intuit’s restore solutions include moving the backup from the server to your local hard drive and restoring from there, or creating a portable company file (.QBM) from the original file and restoring that instead.
Cause 04 · Windows server setup: hosting, sharing, permissions
When the company file is on a Windows server, Intuit’s steps are: make the server the only host (turn off Host Multi-User Access on workstations), run File Doctor, restore a backup, and set up the server properly — update QuickBooks, check firewall and internet settings, set folder permissions, and scan the folder with QuickBooks Database Server Manager so the .ND file is present.
Cause 05 · Linux server or network name setup
For a Linux server, Intuit says to configure the Linux Database Server Manager and add the server’s IP address and name to the Windows hosts file on the workstations (Intuit notes Linux file names are case sensitive). Intuit’s Windows-server steps also end with editing the hosts file on a workstation.
Cause 06 · Company file not on a server
If your company file isn’t on a server and you still see -6000, -83, Intuit’s article says to reach out to its support team. That’s the right path; we can help independently if Intuit’s support doesn’t resolve it.
How to fix Error 6000, 83 yourself.
Six steps, in the order Intuit’s article presents them. Start with the step that matches what you were doing; if none resolves it, stop and book a diagnostic.
If you were backing up: back up to a new local folder
Close QuickBooks Desktop on the server (File → Quit QuickBooks Desktop). In File Explorer, create a new test folder on the C: drive, create your backup in that folder, then restore from the new backup. If the error is still there, follow the server steps below.
If you were restoring: fix the backup’s file and folder names
Remove any special characters, symbols or spaces from the backup’s file name, and rename the folder that holds it the same way. Then try the restore again.
If you were restoring: use a portable file or restore from the local drive
Create a portable company file (.QBM) from the original company file and restore from it. Or move the backup from the server to your local hard drive and restore from there.
If the file is on a Windows server: make the server the only host, then run File Doctor
On each workstation, turn off Host Multi-User Access — the server should be the only host. Then run QuickBooks File Doctor (Tool Hub → Company File Issues). If that doesn’t clear it, Intuit’s next solution is restoring a backup.
Set up the Windows server by hand
Intuit’s manual steps: update QuickBooks to the latest release; check firewall and internet settings on the server and workstations; set folder permissions to share the company-file folder; install and open QuickBooks Database Server Manager on the server, scan the folder, and confirm an .ND file appears; turn hosting off on the workstations again; then copy the company file to the desktop, open it, and if it works, rename the original and move the copy back. If it still fails, Intuit says to edit the Windows hosts file on a workstation.
Linux server, or not on a server: follow Intuit, then escalate
For a Linux server, configure the Linux Database Server Manager and add the server’s IP address and name to the Windows hosts file. If your file isn’t on a server, Intuit says to contact its support team. If Error 6000, 83 still persists, stop and book a diagnostic; continued retries can mask deeper damage.
Where the Error 6000, 83 steps come from.
The causes and steps above follow Intuit’s own support article, linked below so you can check them at the source. Where this page and Intuit’s article ever differ, follow Intuit.
- How to fix Error 6000,-83 — Intuit QuickBooks support
Three signals it’s a ProAdvisor call.
It persists after every step
You’ve worked Intuit’s steps for your situation and Error 6000, 83 still blocks the file. What’s left can be the server setup or the company file itself.
It keeps coming back
Error 6000, 83 clears, then returns — or the multi-user setup won’t stay stable. A repeat means something in the hosting, permissions, or file keeps breaking, and a one-time fix only masks it.
The company file looks damaged
Error 6000, 83 alongside other 6000-series codes, or a file that won’t open even from a local copy, points to possible company-file damage — the moment to stop self-fixing and have the file assessed.
When Error 6000, 83 is no longer a software problem.
Error 6000, 83 stops QuickBooks Desktop completing an open, a restore or a backup of the company file. When the file opens again, the next question is whether the books inside it are the ones you expect.
- You worked from an older backup or copy to get past the error.
- Transactions entered around the time of the error are missing or doubled.
- Account balances no longer agree with the bank 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.
Self-fix didn’t clear Error 6000, 83?
A QuickBooks ProAdvisor diagnoses the deeper 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
- Error 6000, 83 is a Desktop/Enterprise company-file error — resolving it takes fluency in backup and restore, folder permissions, network shares, hosting, Database Server Manager and .ND files.
- We work in Desktop and Enterprise files, led by TechBrot’s founder; Intuit’s public ProAdvisor directory lists active ProAdvisors for verification.
- Operational experience to diagnose Error 6000, 83 past Intuit’s documented steps — not a script-reading queue.
A QuickBooks ProAdvisor diagnoses past the surface.
When Intuit’s steps don’t hold, what’s left is past the surface — folder or share permissions, hosting that isn’t set up right across machines, a Database Server Manager or .ND file that won’t stay healthy, a backup that won’t restore, or damage to the company file. A QuickBooks ProAdvisor who works in Desktop and Enterprise files diagnoses the actual root cause, fixes it against a written scope, and verifies the file opens cleanly before closing.
Diagnostic
30-minute diagnostic, scheduled within one business day
What people ask about Error 6000, 83.
What is QuickBooks Error 6000, 83?
What causes QuickBooks Error 6000, 83?
Can I fix QuickBooks Error 6000, 83 myself?
When does Error 6000, 83 require a ProAdvisor?
Why does Error 6000, 83 happen when I restore a backup?
Does Error 6000, 83 appear in QuickBooks Online?
Self-fix didn’t resolve it?
Self-fix didn’t work? Book a diagnostic.
If Error 6000, 83 persists after Intuit’s steps, comes back, or your multi-user setup won’t stabilize, a 30-minute call scopes the real cause — a focused diagnostic is from $1,200 — a fixed fee, set after scoping. Written scope before any work begins.