Error -6000, -83
QuickBooks error 6000 83
Open, backup or restore failed? What you were doing tells you where to start.
QuickBooks error -6000, -83 appears when you open, back up or restore a company file and QuickBooks can't finish. What you were doing tells you where to start: a backup or restore points to the backup's file name and to restoring from the local drive; a file kept on a server points to hosting — Intuit's first server fix is turning hosting off on every workstation. If a local copy still fails, the cause is not yet established: finish Intuit's steps before deciding whether company-file repair is needed.
Last reviewed October 2026 by a Certified QuickBooks ProAdvisor
What this page is based on: Intuit’s own help article for this error (checked October 2026)
- Intuit sorts the fix by what failed
- Open a local copy first
- Repair only after Intuit's steps
Who this affects
This is about opening the file, not what is inside it
You will usually see -6000, -83 in one of three moments: creating a backup, restoring one, or opening a company file that a Windows or Linux server hosts. Intuit does not tie it to one cause; its article sorts the fixes by which of those you were doing, and notes that the Database Server Manager can sometimes reset the hosting settings on your workstations. In practice it lands on a short list: a folder locked down by Windows permissions, hosting set the wrong way in a multi-user setup, a network share that will not give QuickBooks full access, or damaged .ND and .TLG files sitting beside the .QBW. It also turns up when restoring a backup to a folder QuickBooks cannot fully write to. The data inside the file is usually fine — the problem is the door, not the room. Fix how and where the file is served, and the error typically disappears.
Start here
-6000, -83 — a setup fix, or a damaged file?
A BACKUP, A RESTORE, OR A SERVER
A setup fix
Fix the backup's name and path, or turn hosting off on the workstations and rescan the folder — this clears most -6000, -83 messages.
LOCAL COPY STILL FAILS
Continue diagnosis
A failed local test alone does not prove file damage. Finish Intuit's steps before deciding whether company-file repair is needed.
See file repair
Read this as text
- A BACKUP, A RESTORE, OR A SERVER: A setup fix — Fix the backup's name and path, or turn hosting off on the workstations and rescan the folder — this clears most -6000, -83 messages.
- LOCAL COPY STILL FAILS: Continue diagnosis — A failed local test alone does not prove file damage. Finish Intuit's steps before deciding whether company-file repair is needed.
Fix it yourself
The DIY fix for error -6000, -83, step by step
Follow one route: Intuit's, sorted by what you were doing when the error appeared, below. A local copy is a quick test of the location: if it opens, the path or the hosting was the problem. If a local copy still fails, the cause is not yet established. Continue the relevant Intuit troubleshooting steps before deciding whether company-file repair is needed.
Intuit's fix, in order
Read this as text
Four stages, left to right, in Intuit's order: a backup or restore starts with the backup's file name and a restore from the local hard drive; a server-hosted file starts with hosting turned off on every workstation; then File Doctor, a restore from backup and the manual fix; then the file opens and -6000, -83 clears, marked with a tick. An illustrative sequence.
Intuit's own fix for -6000, -83, in Intuit's order
Intuit's own article (updated 8/5/2026, checked November 2026) splits the fix by what you were doing and, if none of that applies, by where you keep the company file:
- Creating a backup: if the file is on a server, move it to your local hard drive first. Make a new folder on the C: drive, save a backup there, then restore from that backup. If the error is gone, use the restored file as your main company file. If it persists, go to the steps for your server below; if the file isn't on a server, Intuit says to contact its support team.
- Restoring a backup: check the backup's file name, create a portable company file, and restore the backup from your local hard drive.
- A company file on a Windows server: turn off hosting on your workstations; run QuickBooks File Doctor; restore from a backup; then the manual fix — share the company-file folder, scan it with the Database Server Manager, check the hosting settings, reset the Database Server Manager and move the company file — and, last, edit the Windows hosts file.
- A company file on a Linux server: configure the Linux server, then the host file.
Intuit's -6000, -83 article does not include renaming the .ND and .TLG files. That step belongs to the sibling error -6000, -77, where Intuit says both files are recreated automatically when you open the company file.
When to call us
When error -6000, -83 is not just setup
When the backup path is clean, hosting is off on every workstation and the server has rescanned the folder, and the file still won't open even as a local copy, the cause is still not established: work through the rest of Intuit's steps first. When they are exhausted and the file still won't open, the job becomes a file repair, or a rescue if data is already missing, always worked on a copy. If the error appears only when opening a file from an external or mapped drive — never during a backup or restore — compare error -6000, -77, which Intuit treats as a location problem. If the code you are actually seeing is -6189, -816 — the file held by another session or a stale transaction log — that guide walks its own fix path.
Some -6000, -83 cases are not a QuickBooks problem at all. When the block traces to your operating system, a firewall, server permissions, or failing network hardware, changing QuickBooks settings will not help — that is work for your IT or network support, not a bookkeeping fix. For Intuit's own documentation on the -6000 series and the Tool Hub, see QuickBooks official help. We will tell you plainly which side the cause sits on so you spend your time on the right one.
What the local test tells you
Read this as text
On the left, a file that opens from the local C: drive has a setup problem — permissions, hosting, or the .ND and .TLG helpers — and the file itself is fine. On the right, a local copy still fails: the cause is not yet established, so Intuit's remaining steps come before any decision about company-file repair, worked from a copy, never the original. A comparison of the two outcomes.
How the -6000, -83 diagnosis is written up
Who’s responsible for your file
A Certified QuickBooks ProAdvisor handles your file from the review through the corrections to the hand-back — the same person throughout, never a rotating pool.
About QBSpecialist
Illustrative example — not a client file.Sample diagnostic summary
The written read-out that tells you whether it is setup, damaged support files, or genuine file damage.
How we work
Every diagnosis runs on a copy first; the original changes only after the cause is confirmed.
See QuickBooks file repairResponse commitment
A written reply within one business day.
Questions about error -6000, -83
What does error -6000, -83 actually mean?
It appears when QuickBooks can't finish opening, backing up or restoring a company file, per Intuit's article for this error. Intuit doesn't name one cause; it sorts the fixes by the operation — the backup's file name and where it is restored from for a backup or restore, the hosting settings for a file kept on a Windows or Linux server. Intuit's article never treats it as file damage by itself.
How do I fix -6000, -83 quickly?
Start from what you were doing. For a failed restore, check the backup's file name and restore from the local hard drive. For a file on a server, turn hosting off on every workstation and have the server rescan the folder with the Database Server Manager. If a local copy then opens, the file is fine and the fault was the path or the hosting; renaming the .ND and .TLG files lets QuickBooks rebuild them. Most -6000, -83 cases end there.
What are the .ND and .TLG files, and is it safe to rename them?
The .ND (network descriptor) and .TLG (transaction log) files sit beside your .QBW company file and help QuickBooks find and serve it. Renaming them is safe and reversible — QuickBooks rebuilds a fresh .ND when you rescan the folder, and a fresh .TLG when you open the file. You are not touching the data in the .QBW itself.
Can -6000, -83 mean my file is corrupt?
It can, but a failed local test alone does not prove it. If a local copy still fails, the cause is not yet established. Continue the relevant Intuit troubleshooting steps before deciding whether company-file repair is needed. If Intuit's steps are exhausted and the file still won't open, a file repair on a copy — or a rescue if data is already missing — is the next step.
Why do I get -6000, -83 when restoring a backup?
Restoring writes a brand-new company file, so it needs a folder QuickBooks can fully write to. Restoring onto a network drive or USB stick, into a protected folder, or with special characters in the file name can all trigger -6000, -83. Restore to the local C: drive with a plain file name first, then move the file where it belongs.
When is -6000, -83 not something I should fix myself?
When it traces to your operating system, your network hardware, or server permissions beyond QuickBooks, it stops being a bookkeeping fix. A blocked share, a firewall, or a failing drive is IT territory. We will tell you honestly when the cause sits outside the file so you call the right person and do not keep changing QuickBooks settings that were never wrong.
- Error 3371— when QuickBooks itself won't start, not the company file
- Error 15271— when a payroll or product update fails instead
Not sure how bad it is?
Talk to a QuickBooks specialist.
Describe the file and a specialist will tell you which of these you are dealing with — including when the answer is that you don't need us.