QuickBooks Error -6000, -82 and -6000, -83: What Blocks Company File Access
QuickBooks Desktop reports Error -6000, -82 or -6000, -83 when it finds the company file but cannot open it — here is what users are doing to resolve it.
QuickBooks Desktop users are reporting a familiar wall when launching their company files: Error -6000, -82 or -6000, -83. The message appears at the moment the file is supposed to open, and in most cases the file itself is visible to QuickBooks — the application simply cannot get inside it. Community threads and accepted fixes point to a handful of root causes, most of which involve where the file lives, how multi-user hosting is configured, or minor damage to the support files that sit alongside the main company data.
What the Error Actually Means
The -6000 series with a -82 or -83 suffix is fundamentally an access error. QuickBooks has located the company file on the drive or network path, but something is preventing it from opening the file. That distinction matters: the file is not necessarily lost or destroyed, but the pathway to reading it is blocked.
The most common triggers fall into four categories:
- Folder or file permissions — the Windows user account running QuickBooks does not have full read and write access to the folder containing the company file.
- Improper storage location — the file sits on a USB drive, external hard disk, or a mapped network drive where connectivity or permissions are unreliable.
- Hosting turned on in the wrong place — more than one computer on the network is set to host multi-user access, creating a conflict over who controls the file.
- Damage to configuration or companion files — the
.ND(network descriptor) and.TLG(transaction log) files that QuickBooks creates next to the company file can become corrupted and block access even when the data file is intact.
The Recommended Fix Sequence
The accepted community approach is to work through these steps in order, starting with the least invasive.
Run the QuickBooks Tool Hub and File Doctor
The first stop is the QuickBooks Tool Hub, specifically the File Doctor utility inside it. File Doctor checks hosting settings, tests folder permissions, and attempts to repair many -6000 conditions automatically. For a significant share of users, this single step clears the error without any manual intervention.
Move the File to a Local Drive
If the company file currently lives on a USB stick, external drive, or mapped network location, copy it — along with its companion .ND and .TLG files — to a local folder such as the Documents directory on the workstation, then attempt to open it from there. This rules out network connectivity hiccups and permission mismatches on the original storage location. If the file opens locally without error, the problem lies with the network path or external drive, not the data itself.
Verify Hosting on Only the Server
In a multi-user setup, only the computer acting as the server should have hosting turned on. Every workstation should have it off. When two or more machines both try to host, QuickBooks can throw a -6000, -82 or -83 error because the file-access negotiation fails. Check the hosting status on each machine and confirm that exactly one — the server — is set to host multi-user access.
Rename the .ND and .TLG Companion Files
As a targeted step, users can rename the .ND and .TLG files that sit next to the company file. These are configuration and log files that QuickBooks regenerates automatically the next time it opens the company file. Renaming them clears corrupted network and transaction-log data without touching the actual company file contents. Simply append a word like “old” or “backup” to each filename, then try opening the company file again.
When the Company File Itself Is Damaged
If the error persists after File Doctor, a local-drive test, and the companion-file rename, the company file may have sustained structural damage. Running Verify and Rebuild Data from within QuickBooks can confirm whether the file has integrity problems. When Verify reports errors that Rebuild cannot fix, or when the file still will not open, professional data recovery becomes the next consideration.
A critical precaution applies throughout this process: always work on a copy of the company file, and keep a current backup before attempting any repair. Renaming companion files is safe, but deeper interventions — especially on a file that may already be damaged — carry risk if something goes sideways mid-repair.
For files that fail Verify/Rebuild or remain locked behind the -6000 error after every community step has been exhausted, the data inside is often still recoverable through a dedicated file repair service that can open and reconstruct the damaged structure directly.