QuickBooks Error -6000, -816 -- Company File Won't Open

QuickBooks error -6000, -816 blocks access to your company file on open; our engineers walk through each trigger and the steps to restore access.

QuickBooks Desktop error -6000, -816 appears when a user attempts to open a company file stored in multi-user mode or on a network location. The error halts the open routine before the file fully loads, leaving users locked out of their books. Our engineers treat this as one of the more common 6000-series failures because it can stem from several independent causes — file locking, folder permissions, hosting configuration, or structural data damage — and the correct fix depends entirely on which trigger is in play.

What the Error Message Says

The full dialog typically reads:

"QuickBooks is unable to open this company file. An error occurred when QuickBooks tried to access the company file. Error codes: (-6000, -816)."

In some environments the message is preceded by a brief delay; in others it appears immediately after selecting the company file.

What the Code Means

The -6000 prefix identifies a company-file-access failure. The -816 sub-code narrows the failure point to the file-open handshake — QuickBooks located the file but could not complete the read sequence required to load it into memory. That handshake can break because another process holds a lock on the file, because the Windows folder permissions deny QuickBooks the access it needs, or because internal structural elements inside the .QBW file are damaged.

What Triggers It

Our engineers see four trigger scenarios, listed here from most to least common:

1. File in use by another process — a second QuickBooks instance, a backup job, an antivirus scan, or a sync tool has a handle on the .QBW or any of its companion files (.ND, .TLG, .DSN).
2. Windows folder permissions — the user account launching QuickBooks lacks full-control rights on the folder where the company file lives.
3. Hosting configuration mismatch — the server is not configured as the host, or a workstation has hosting turned on when it should not.
4. Structural data damage — one or more internal lists or transaction blocks inside the .QBW are corrupted, preventing the file from completing its open sequence.

How to Fix It

Scenario 1 — File in use by another process

1. Close QuickBooks on every machine that can reach the file.
2. Open Task Manager (Ctrl+Shift+Esc) and end any lingering QBW32.exe, QBDBMgrN.exe, or QBUpdate.exe processes.
3. Temporarily pause real-time antivirus scanning on the folder holding the company file.
4. Confirm no Windows Backup, OneDrive, or third-party sync tool is actively writing to that folder.
5. Reopen the company file.

Scenario 2 — Windows folder permissions

1. Right-click the folder containing the .QWB file and choose Properties.
2. Go to the Security tab and click Edit.
3. Select the user (or the Everyone group if recommended by your network setup) and grant Full Control.
4. Click Apply, then OK, and close the properties dialog.
5. Apply the same permissions to the folder on the server if the file is network-hosted.
6. Reopen the file.

Scenario 3 — Hosting configuration mismatch

1. On the server, open QuickBooks and go to File → Utilities.
2. Verify that Host Multi-User Access is listed (if Stop Hosting Multi-User Access appears instead, hosting is already on).
3. On each workstation, confirm the same menu shows Host Multi-User Access — meaning hosting is off locally.
4. Restart the QuickBooksDBXX service (where XX matches your version) in Windows Services.
5. Switch the workstation to Multi-User mode and open the file.

Scenario 4 — Structural data damage

1. From the No Company Open window, click the drop-down and select Open — do not select the file from the recent list.
2. Hold Alt while clicking Open, and keep it held until the file fully loads or the error reappears.
3. If the file opens, immediately run File → Utilities → Verify Data.
4. If Verify reports damage, run Rebuild Data from the same menu.
5. If Rebuild does not resolve the error, restore the most recent backup and run Verify on the restored copy.
6. If neither Rebuild nor a restore resolves the issue, the .QBW has damage that the built-in tools cannot address and our engineers can perform a deeper structural repair.

How to Prevent It Recurring

• Set a folder exclusion for the company-file directory in your antivirus real-time scanner.
• Ensure only the server hosts multi-user access; workstations should have hosting off.
• Schedule automated backups for off-hours so they never overlap with active QuickBooks sessions.
• Run Verify Data at month-end close to catch structural issues before they block file access.
• Keep QuickBooks Desktop updated to the latest release, as Intuit patches file-handling routines in maintenance updates.