Common symptoms
- Error -6000, -77 appears when opening a company file
- Error -6000, -83 appears while opening, restoring, or backing up
- The file opens locally but fails from a network workstation
Before you begin
- Record the full error number, including the second number after -6000
- Confirm whether you were opening, restoring, or backing up
- Protect the original .QBW file and make a backup before changing companion files
Back up your data before changing company-file components, services, firewall rules, or permissions. Never delete the .QBW company file as a troubleshooting step.
1. Match the fix to the exact error and action
The -6000 family does not have one universal cause. The second number—and whether you were opening, restoring, or backing up—changes the safest troubleshooting path.
- Take a screenshot of the complete error.
- Note the current company-file location.
- If the file is on external or removable storage, copy it to a local Windows folder before testing.
2. Test a short local path
A local copy helps distinguish damage inside the file from a path, share, or permission problem.
- Create a folder such as C:\QBTest on a computer with QuickBooks installed.
- Copy—not move—the .QBW file into it.
- Open QuickBooks, choose Open or Restore Company, and browse to the copied file.
- If the copy opens, focus on the original network location and permissions rather than rebuilding the file.
3. Use File Doctor before manual changes
Intuit recommends QuickBooks File Doctor, included with QuickBooks Tool Hub, for many file and network issues.
- Install or update QuickBooks Tool Hub from Intuit.
- Run Company File Issues → QuickBooks File Doctor.
- Select the affected company file and follow the prompts.
- Save the result or error details for the next step.
4. Re-create .ND and .TLG companion files
For errors such as -6000, -77, Intuit includes renaming the .ND and .TLG companion files among its troubleshooting steps. QuickBooks can recreate them.
- Close QuickBooks for all users.
- In the company-file folder, find files with the same name as the .QBW file ending in .ND and .TLG.
- Rename each by adding .OLD to the end. Do not rename the .QBW file.
- Open QuickBooks and test. On a server, rescan the folder in Database Server Manager.
Rename the .TLG file instead of deleting it. It can be important for assisted data recovery.
5. Check Windows folder permissions
The signed-in Windows user and the QuickBooks Database Server Manager account need appropriate access to the folder that stores the company file.
- Test whether the user can create and delete a harmless text file in the shared folder.
- Confirm the appropriate QBDataServiceUserXX account has access.
- On domain controllers or managed servers, have the administrator apply the change; do not broaden permissions to Everyone as a shortcut.
Verify the result
Test one workstation before bringing everyone back in.
- Open the company file from its normal network path.
- Switch to multi-user mode and sign in with a separate QuickBooks user.
- Close and reopen the file once to confirm the repair survives a fresh connection.
- Record what changed and keep a current backup.
Sources and review notes
This guide is independently written and reviewed against the official references below. Product behavior can vary by version and network environment.
Want an expert to take over?
We’ll diagnose, repair, and verify it remotely.
Tell us what you are seeing. We’ll start with the work you have already completed and explain any changes before making them.