Fix QuickBooks Error -6000 -832: Company File Access Troubleshooting

Last reviewed 2026-07-03 4 min read

Resolve QuickBooks Desktop error -6000 -832. Our guide covers what this company-file family error means, common causes, and step-by-step fixes to keep your

When QuickBooks Desktop throws an error in the -6000 family, it means the software is struggling to open, access, or communicate with your company file. Error -6000 -832 is a specific variation that typically points to a breakdown in network hosting or a problem with the network data (.ND) files that allow multiple computers to share the same company file. If you are committed to running QuickBooks Desktop for the long haul—including on older, unsupported versions—understanding how to resolve these file-access blocks is essential.

Understanding the -6000 Error Family

Errors beginning with -6000 (such as -6000, -77, -80, -82, or -832) all share a common theme: QuickBooks cannot reach the company file (.qbw). While the exact last few digits indicate the specific trigger, the underlying mechanics are usually the same. In the case of -6000 -832, the issue is almost always tied to multi-user hosting configuration, damaged network descriptor files, or temporary communication glitches between your workstation and the server.

Common Causes of Error -6000 -832

Before making changes, it helps to know why this happens. The usual culprits include:

Incorrect hosting configuration: Multi-user mode is enabled on a workstation rather than just the server.
Damaged .ND or .TLG files: The Network Data (.ND) and Transaction Log (.TLG) files act as maps for QuickBooks. If they are corrupted, QuickBooks gets lost trying to find the file.
Firewall or antivirus blocking: Security software is blocking incoming QuickBooks traffic.
Database Server Manager issues: The QuickBooks Database Server Manager is not running, or the folder containing your company file hasn't been scanned recently.

How to Fix Error -6000 -832

We recommend working through these steps in order. These fixes rely entirely on built-in tools and manual adjustments, meaning they work perfectly for unsupported or discontinued versions of QuickBooks Desktop.

1. Test the File Locally

First, determine if the problem is the network or the file itself. Copy the company file (.qbw) to your local Desktop. Open QuickBooks while holding down the Ctrl key (to force it into "No Company Open" mode), then browse to the Desktop and open the copied file.

If it opens: The file is healthy. The issue is your network, hosting setup, or .ND files. Proceed to Step 2.
If it still shows an error: The company file itself is damaged. Skip to Step 5.

2. Rename the .ND and .TLG Files

If the file opened locally, go back to the original folder where your company file is stored. You will see files with the same name as your company file but ending in .ND and .TLG.

Right-click the .ND file and select Rename. Add the word OLD to the end (e.g., CompanyFile.ND.OLD). Do the same for the .TLG file. QuickBooks will automatically recreate these files the next time it opens in multi-user mode. Do not delete them, and never rename or move the .QBW file itself.

3. Verify Hosting Mode

QuickBooks should only be hosted on the server computer (the machine where the physical file lives), not on the workstations accessing it.

Open QuickBooks on the server computer.
Go to File > Utilities.
If you see Stop Hosting Multi-User Access, it is already hosting correctly. Click it, then re-select Host Multi-User Access to reset the feature.
Check your workstations. On those computers, Host Multi-User Access should not be visible in the Utilities menu—only Stop Hosting should be visible if it is incorrectly enabled.

4. Run the Database Server Manager

If the .ND files are intact and hosting is correct, the database service might just need to re-map the folder.

On the server computer, open the Windows Start menu.
Search for and open QuickBooks Database Server Manager.
Go to the Scan Folders tab.
Click Add Folder, select the folder containing your company file, and click Scan.
Once the scan finishes, try opening the file on your workstation again.

5. Run Verify and Rebuild

If your local test in Step 1 failed, your company file has structural damage. Go to File > Utilities > Verify Data. If QuickBooks finds an issue, run Rebuild Data from the same menu. You may need to run the Rebuild tool multiple times to clear all errors.

Preventing Future Access Errors

To keep your Desktop setup stable, ensure your firewall exceptions are permanently set for the specific QuickBooks version you are running. Additionally, make a habit of running the Database Server Manager scan any time you update your QuickBooks version, move the company file to a new folder, or introduce a new computer to your network.

When to Suspect Severe File Damage

If the Verify/Rebuild utility fails to fix the local copy of your file, or if the file simply will not open regardless of what you do, the .QBW file itself is likely severely corrupted. At this stage, you will need to restore from a recent backup or seek out a dedicated company file repair service to extract and rebuild the damaged data structures so you can get back to work.