Quick answer

QuickBooks error 6000 means QuickBooks located the company file but could not open it. The usual causes are a locked file, a damaged .ND or .TLG support file, multi-user hosting pointed at the wrong computer, or genuine data damage. Work through the fixes below in order: close every QuickBooks process, test a local copy of the file, rename the support files, then run Verify and Rebuild. Do not restore a backup until you have tried those steps.

What error 6000 actually means

Error 6000 is not a single failure. It is a family: QuickBooks found the file, tried to open it, and was blocked. The dialog wording tells you which variant you have, and each variant points at a different cause.

Message you seeWhat it usually meansStart with
Error codes: (-6000, -77)The path to the file is not reachable — external drive disconnected, mapped drive letter changed, or folder permissions deniedStep 2
Error (-6000, -82) or (-6000, -106)Multi-user hosting is enabled on the wrong computer, or the file name has a trailing space before .qbwStep 3
Error codes: (-6000, -301)Damaged .TLG, .ND or .DSN support files, or third-party encryption on the folderStep 4
Error 6000,-83The file cannot be opened, restored or backed up — often a network/server path or hosting problemStep 5
Error 6000 with no suffixGeneric open failure — usually a lock, permissions or data damageStep 1

The important detail is that in almost every case, your data is still in the file. The repair steps below are designed to get QuickBooks opening it again without deleting transactions. The one exception is severe data damage, which is why we take a backup before anything else.

Symptoms that come with error 6000

  • The error appears immediately after selecting the company file, sometimes after QuickBooks has shown the file name in the No Company Open window.
  • The same error may appear when creating a backup or restoring one — not just when opening a file.
  • On a network, one workstation fails while others work, or the error follows the computer rather than the file.
  • QuickBooks may stay open but no company file loads, and the window title still reads No Company Open.
  • After the error, a .QBW file may show a companion lock file named .QBW.ND or a .TLG file with today's timestamp.

Common causes, ranked by how often we see them

  1. A background QuickBooks process still holds the file. QBW32.exe, QBDBMgrN.exe or QBUpdate.exe can survive a normal close, especially after a crash. QuickBooks then refuses to reopen the file.
  2. Multi-user hosting enabled on a workstation. When more than one computer hosts multi-user access, connections break with a 6000 variant. Only the server should host.
  3. Damaged .ND, .TLG or .DSN support files. These are regenerated automatically, so renaming them is safe and often fixes the error instantly.
  4. The company file path changed. The drive letter changed, the external drive was unplugged, the folder was renamed, or the file is on OneDrive, Dropbox or a similar sync folder that locks it intermittently.
  5. Folder permissions. The Windows account running QuickBooks lost modify rights to the folder after a domain change, a new user profile, or a Windows update.
  6. Genuine data damage. If the file is physically damaged, QuickBooks reports a 6000 variant no matter where the file lives.
  7. Third-party encryption or aggressive antivirus. Encryption tools and some endpoint security products block the file I/O QuickBooks needs.

Back up before you repair. Copy the entire company-file folder — not just the .QBW — to an external drive or another computer. If a repair goes wrong, that folder copy is your recovery point. Also note the exact error code and suffix; it tells you which step matters most.

How to fix QuickBooks error 6000

1

Close every QuickBooks process and reopen as administrator

Open Task Manager with Ctrl + Shift + Esc and check the Details tab for QBW32.exe, QBDBMgr.exe, QBDBMgrN.exe, QBCFMonitorService.exe and QBUpdate.exe. End any instance you find. Then right-click the QuickBooks desktop icon and choose Run as administrator before opening the company file.

Running elevated also clears the most common -6000, -77 case, where the app simply cannot reach the file location under the current account permissions.

2

Confirm the file path and test a local copy

Locate the .QBW file in File Explorer. The default location is C:\Users\Public\Public Documents\Intuit\QuickBooks\Company Files, but yours may differ. If the file is on an external drive, network share or cloud-sync folder, copy the .QBW file to a plain folder on your local C: drive and open that copy.

If the local copy opens, the problem is the location — not the data. Move the file to a local folder or, for networks, use the UNC path (\\Server\Share\CompanyFile.qbw) instead of a mapped drive letter, which Windows can reassign.

3

Make sure only one computer hosts multi-user access

On every computer except your designated server, open QuickBooks, go to File → Utilities and choose Stop Hosting Multi-User Access if that option appears. On the server, the same menu should show Host Multi-User Access or be intentionally off for single-user work.

To confirm the setting, open QuickBooks and press F2. In the Product Information window, the Local Server Information section shows whether hosting is active. This is the fix for most -6000, -82 and -6000, -106 errors.

4

Rename the .ND, .TLG and .DSN support files

Open the folder that contains your company file. Find every file with the same base name but the extensions .ND, .TLG and .DSN — for example company.qbw.nd. Rename each by adding .old to the end of the extension (company.qbw.nd.old).

These are configuration files, not your data. QuickBooks recreates them the next time the file opens or Database Server Manager scans the folder. This single step resolves a large share of -6000, -301 reports.

5

Run Verify Data, then Rebuild Data

Open the company file (or a local copy). Go to Window → Close All, then File → Utilities → Verify Data. Read the result carefully:

  • "QuickBooks detected no problems with your data" — the file is healthy; the 6000 error was environmental. Go back to the location or hosting step.
  • "Your data has lost integrity" — there is data damage. Continue to Rebuild.

Then run File → Utilities → Rebuild Data. QuickBooks requires a backup before rebuilding; save it to a new file name. Rebuild can appear frozen while it works — as long as the mouse pointer moves, it is still running. When it finishes, run Verify again. It is normal to rebuild two or three times before the file comes back clean.

6

Run QuickBooks File Doctor from Tool Hub

Download the current QuickBooks Tool Hub, install it, and open Company File Issues. Run Quick Fix my File first, then Run QuickBooks File Doctor. Select your company file, choose Check your file (add network checks if you work in multi-user mode), and enter your QuickBooks admin password.

A scan can take 10–15 minutes on a large file, and it sometimes reports "unsuccessful" even when it repaired the problem. Close the tool and try opening the file anyway. File Doctor is especially effective for the 6000 series and network errors like H202.

7

Check folder permissions, encryption and antivirus

Right-click the company-file folder, open Properties → Security, and confirm your Windows account has Modify or Full control. If the folder is shared, the Sharing tab must grant the same rights over the network. Avoid whole-drive encryption tools on the folder that holds your .QBW; QuickBooks and encryption filters frequently conflict.

If antivirus has a "protected folders" feature, add the company-file folder and the QuickBooks program folder as exclusions — using the vendor's documented method, not by disabling protection entirely.

8

Restore a recent backup (only after the steps above)

If Verify and Rebuild cannot repair the file, restore the newest backup that opens cleanly: File → Open or Restore Company → Restore a backup copy. Do this as a separate workflow — do not overwrite the damaged file. Rename the damaged copy so nobody opens it by accident, and keep it: it may still be recoverable by Intuit Data Services or a data-recovery specialist.

Verify the fix

  1. Close and reopen QuickBooks as a standard user, not as administrator, and open the company file.
  2. Press F2 and confirm the file, version and hosting status are what you expect.
  3. Run File → Utilities → Verify Data one more time and confirm it reports no problems.
  4. If you use multi-user mode, open the same file from a second computer and post a test transaction, then delete it.
  5. Create a fresh backup and store it off the machine.

If error 6000 comes back

Recurring 6000 errors usually mean one of three things. First, the file lives in a cloud-sync folder (OneDrive, Dropbox, Google Drive) that periodically locks it — move it out. Second, the host computer is going to sleep or losing its IP address — set a static IP for the server and disable sleep on the host. Third, the file has damage that rebuild cannot reach, in which case professional company-file repair or Intuit Data Services is the right next step. If you cannot open the file at all or rebuilding fails repeatedly, do not keep retrying the same rebuild — escalate, and keep the original file untouched for recovery.

Prevention

  • Keep company files on a local drive or a properly shared server folder — never in a consumer sync folder.
  • Rebuild and verify the file at least twice a year, and always before a version upgrade.
  • Back up on a schedule and test a restore at least once a quarter. An untested backup is a guess.
  • Before moving to a new computer, follow a documented migration procedure and verify the file before retiring the old machine.
  • Keep QuickBooks updated, but schedule updates for a day you can spend 20 minutes verifying the company file afterward.

Frequently asked questions

Will renaming .ND and .TLG files delete my data?

No. The .ND, .TLG and .DSN files only describe how QuickBooks connects to the company file. Your transactions live in the .QBW file. QuickBooks automatically recreates the support files, which is exactly why renaming them fixes many connection-related 6000 errors.

Can I fix error 6000 without a backup?

You can try the non-destructive steps — closing processes, running as administrator, renaming support files and checking hosting — without a backup. Do not run Rebuild, restore, or any file-level repair without a copy first. If the file is already damaged, an untested repair can reduce what a data-recovery service can salvage.

Why does error 6000 appear only on one workstation?

That points at the workstation, not the file: permissions, a stale mapped drive, antivirus, or multi-user hosting accidentally enabled on that PC. Re-map the drive using the UNC path, confirm hosting is off, and re-run the Network Diagnostic tool in Tool Hub.

Does error 6000 mean the company file is corrupt?

Not necessarily. Corruption is only one of several causes. If the same file opens from another computer or from a local copy, the data is fine and the problem is the path, lock or hosting configuration. Verify Data is the fastest way to tell the difference.

What if Rebuild runs for hours?

Large files legitimately take 30–90 minutes. If a single rebuild passes two hours and the progress indicator has not changed, let it finish if the mouse still moves; if the machine is unresponsive, it has hung. Restore the pre-rebuild backup and try File Doctor instead, then follow the data damage recovery order.

Sources & further reading