Fix QuickBooks Error -6000 -305: Company File Access Guide

Last reviewed 2026-07-03 4 min read

Resolve QuickBooks Desktop error -6000 -305 when opening a company file. Learn the common causes and how to fix network issues and file damage.

When you try to open your QuickBooks company file and hit error -6000 -305, it usually means the software cannot read the file properly. This is almost always tied to a network configuration glitch, a damaged configuration file, or corruption within the company file itself. Fortunately, you can resolve this without upgrading or replacing your software.

Understanding the -6000 Error Family

Error -6000 -305 belongs to the broader -6000 series of QuickBooks errors. Whenever you see a code starting with -6000, it indicates that QuickBooks Desktop is having trouble accessing your company file (.qbw). Because these codes share common triggers, the troubleshooting steps for -6000 -305 will also resolve many neighboring codes (such as -6000, -6000 -77, or -6000 -816).

Common Causes

Before making changes, it helps to know what triggers the error. The most frequent culprits are:

Network folder permissions: The computer trying to open the file lacks the correct Windows permissions to read the folder where the file is stored.
Damaged network data files: QuickBooks uses .ND (Network Data) files to communicate across computers. If these are corrupted, the database server cannot locate the company file.
Firewall or antivirus blocking: Security software is mistakenly blocking QuickBooks from communicating with the server.
Company file corruption: The .qbw file itself is damaged or deteriorating.

How to Fix Error -6000 -305

Follow these steps in order. They apply to QuickBooks Desktop Pro, Premier, and Enterprise, whether you are on a currently supported version or running an older, discontinued installation.

1. Test with a Local Copy

First, determine if the problem is your network or your company file.

Copy the company file (.qbw) from its network or server location.
Paste it directly onto your local Desktop.
Open QuickBooks while holding down the Ctrl key (this opens the application without loading a file), then use "Open or Restore Company" to open the file from your Desktop.

If the file opens successfully, the issue is your network setup, folder permissions, or firewall. If it still throws the -6000 error, the company file itself is damaged.

2. Rename the .ND and .TLG Files

If the local test worked, return to the original folder where your company file is stored. QuickBooks uses .ND and .TLG (Transaction Log) files to manage multi-user access and network routing. If these become corrupted, QuickBooks cannot find your company file.

Locate the files that share the exact same name as your company file but end in .ND and .TLG.
Right-click each one and select Rename.
Add the word OLD to the end of the filename (for example, change CompanyFile.ND to CompanyFile.ND.OLD).
Open QuickBooks again. The software will automatically generate fresh, uncorrupted versions of these files.

3. Rescan with Database Server Manager

If renaming the network files does not work, the server needs to be reconfigured to host the file.

On the computer acting as your server, close QuickBooks.
Open the Windows Start menu, find the QuickBooks folder, and open QuickBooks Database Server Manager.
Select Scan Folders and choose the specific folder where your company file is stored.
Click Scan and let the process finish. This rebuilds the network descriptors and ensures the server is properly configured to share the file.

4. Run Verify and Rebuild

If your local copy test in Step 1 failed, your company file is damaged. You need to repair the data structure.

Go to the File menu, select Utilities, and click Verify Data.
If QuickBooks detects a problem, select Rebuild Data.
QuickBooks will prompt you to create a backup before it attempts to repair the file. Let the Rebuild utility run completely.

Preventing Future -6000 Errors

To keep your Desktop installation stable, avoid mapping network drives; instead, use universal naming convention (UNC) paths (e.g., \\ServerName\QuickBooks\Company.qbw) when mapping your company file. Additionally, configure your Windows firewall and antivirus to automatically allow QuickBooks executables through, and periodically run the Verify Data utility to catch minor data glitches before they turn into access errors.

When to Seek File Repair

If the Rebuild Data utility fails to fix the error, or if it freezes entirely, your company file has sustained structural damage that QuickBooks' built-in tools cannot fix. At this stage, do not attempt manual database edits. If your company file is corrupt and needs repair, reaching out to a dedicated file repair service is the safest way to extract your data and restore it to a working state so you can get back to your books.