ErrorVaultHQ

Solved Error

How to Fix: QuickBooks Error 6000 (Can't Open Company File)

Quick Fix

Try this first, it fixes the majority of Error 6000 cases in under a minute: 1. Close QuickBooks on every computer that has it open. 2. Open the folder containing your company file, find the files with the same name as your company file but ending in .ND and .TLG, right-click each and choose Rename, then add .OLD to the end of each file name. This does not delete any data. these files are automatically recreated. 3. Reopen QuickBooks and try to open your company file again. If that does not work, download and run the QuickBooks Tool Hub and use the 'Run QuickBooks File Doctor' option under Company File Issues, this is Intuit's official repair tool for exactly this error.

What QuickBooks Error 6000 Means

Error 6000 is a QuickBooks Desktop company file error that means QuickBooks can't open or properly access the company file, and it's usually caused by file corruption, permission issues, or problems with the file location such as a network drive, external drive, or cloud-synced folder. This error can arise in both local and network setups, and its specific cause often depends on the extra digits that follow the error code, for example -6000, -77 or -6000, -301, each of which points to a slightly different underlying cause such as a firewall block, another computer hosting the file incorrectly, or a mismatch between the company file and its transaction log. Note: This error is specific to QuickBooks Desktop (Windows and Mac versions), not QuickBooks Online.

Step-by-Step Guide

Fix 1: Rename the .ND and .TLG Configuration Files

  1. 1Close QuickBooks on every workstation. The .ND and .TLG files are configuration files that allow QuickBooks Desktop to access a company file in a network or multi-user environment, and if these files are damaged you will see 6000-series errors when opening your file. Close QuickBooks completely on every workstation.
  2. 2Open the company file folder. Open the folder that has your company file (the default location on Windows is typically C:\Users\Public\Public Documents\Intuit\QuickBooks\Company Files).
  3. 3Find the .ND and .TLG configuration files. Find the files with the same name as your company file but with extensions .ND and .TLG.
  4. 4Rename files by adding OLD to the end. Right-click each one, select Rename, and add the word OLD to the end (for example, company_file.qbw.nd.OLD).
  5. 5Reopen QuickBooks and try to sign in to your company file. Renaming these files causes no data loss since QuickBooks automatically recreates them.

Fix 2: Update QuickBooks to the Latest Release

  1. 1Before trying anything more advanced, make sure you update QuickBooks to the latest release, since Intuit regularly patches known causes of the 6000-series errors. On Windows, go to Help, then Update QuickBooks Desktop, then Update Now, then Get Updates, and restart the program to install.

Fix 3: Run the QuickBooks Tool Hub and File Doctor

  1. 1If renaming the files and updating did not help, Intuit's official Tool Hub can help fix common errors, install issues, company file issues, and networking errors. Close QuickBooks Desktop entirely.
  2. 2Download the QuickBooks Tool Hub. Download the latest version of the QuickBooks Tool Hub from Intuit's site and save it somewhere easy to find, like your Downloads folder.
  3. 3Install the QuickBooksToolHub.exe file. Open the downloaded QuickBooksToolHub.exe file and follow the on-screen install steps (Windows only; if Windows Defender blocks it, select More info, then Run anyway).
  4. 4Run QuickBooks File Doctor from Tool Hub. Open the Tool Hub, go to the Company File Issues tab, and select Run QuickBooks File Doctor. You can also try 'Quick Fix my File' first, which is faster.
  5. 5Scan your company file in File Doctor. In File Doctor, select your company file from the dropdown (or Browse to find it), choose 'Check your file' only, and enter your QuickBooks admin password. The scan can take up to 10 to 15 minutes depending on file size, and it may say it was unsuccessful even when it actually fixed the issue, so try reopening your file afterward regardless.

Fix 4: Test With a Sample Company File

  1. 1Open a sample company file to test. This step tells you whether the problem is with QuickBooks itself or with your specific company file. In the No Company Open window, select Open a Sample File and pick any file from the list.
  2. 2Repair QuickBooks if sample file fails. If the sample file also fails to open with the same error, your QuickBooks installation itself is damaged and needs to be repaired (on Windows, via Control Panel > Programs > QuickBooks > Repair; on Mac, by reinstalling).
  3. 3Continue troubleshooting if sample file opens. If the sample file opens fine, the problem lies with your specific company file or its location, continue to the next steps.

Fix 5: Test the File Location

  1. 1Copy the company file to your desktop. Copying the file to your desktop and opening it tests whether there's a problem with the folder it normally lives in. Go to the folder with your company file, right-click the .qbw file, and select Copy.
  2. 2Paste the file onto your desktop. Paste it onto your desktop.
  3. 3Open the desktop copy in QuickBooks. Hold the Ctrl key while opening QuickBooks to get the No Company Open window, then choose Open or restore an existing company and open the copy from your desktop.
  4. 4Check file path length and location. If it opens fine from the desktop, the original folder location may be damaged, or the path may be too long. Make sure the path to your company file is not longer than 210 characters, since overly long or deeply nested folder paths can trigger this error.

Fix 6: Check Multi-User Hosting Settings (Network Setups)

  1. 1Verify hosting is set to local files only. Error 6000 often shows up when a computer that shouldn't be hosting the file is set to Host Multi-User Access, or when multiple computers are hosting the same file simultaneously. On every workstation except the actual file server, open QuickBooks, press F2 to open the Product Information window, and check that under Local Server Information, Hosting is set to 'local files only' (i.e., off).
  2. 2Stop hosting multi-user access if enabled. If a workstation shows hosting is on, open the file, go to File > Utilities, and select Stop Hosting Multi-User Access, then confirm Yes on both prompts.
  3. 3Enable hosting only on the host server. Only the actual host computer/server should have hosting enabled.

Fix 7: Check Firewall and Folder Permissions

  1. 1A firewall blocking the connection between computers, or incorrect folder/user permissions, are common causes of the 6000-series errors on networks. Temporarily check that your antivirus or firewall isn't blocking QuickBooks processes, and confirm your Windows user account has full read/write access to the folder containing the company file (right-click the folder, Properties, Security tab).

Fix 8: Restore a Backup or Use Auto Data Recovery

  1. 1Restore a backup company file to test. If none of the above works, the company file itself may be corrupted. Restore a recent backup copy of your company file (.QBB) to a test location to confirm whether the current file is the problem.
  2. 2Look for Auto Data Recovery files. If you don't have a backup, look for QuickBooks' Auto Data Recovery (ADR) feature, which keeps automatic recovery copies (named with .adr added to the file name) in the same folder as your company file.

When to Seek Further Help

If you've gone through all these steps and the file still won't open, or the error keeps recurring, this points to logical corruption in the company file rather than a simple configuration issue. At this point, restoring a clean backup, using a specialized third-party file repair tool, or contacting official QuickBooks/Intuit support directly for account- or file-specific help is the recommended next step, since deeper data damage usually requires tools beyond basic troubleshooting.

Sources:

Heads up: this guide was drafted with AI assistance from the real sources listed below, and structured by our team for clarity. It may not cover every possible cause — if it doesn't fix your issue, let us know and we'll take a closer look. See how we create our fixes.

Was this fix helpful?

Related Error Fixes