QuickBooks Error -6000, -305 -- Multi-User Network or Damaged File

QuickBooks error -6000, -305 blocks company file access in multi-user mode; our engineers identify the network and file-damage causes and walk through the fix.

QuickBooks Error -6000, -305 is a 6000-series company file access error that surfaces when a workstation tries to open a QuickBooks Desktop file stored on another machine or in a multi-user environment. The error blocks access to the file entirely and, in most cases, points to a breakdown in the network path between the workstation and the host or to structural damage inside the company file itself. Our engineers have resolved this error across single-server and multi-workstation deployments, and the fix is almost always traceable to one of a handful of root causes.

What the Error Message Says

The full message displayed by QuickBooks Desktop reads:

"An error occurred when QuickBooks tried to access the company file. Error codes: (-6000, -305)"

In some environments the message is preceded by a brief pause or a "Connecting to server" dialog before the error dialog appears. The error code pair is returned by the QuickBooks database server manager when it cannot complete the file-open request.

What the Code Means

The -6000 prefix indicates a company file access failure. The -305 sub-code narrows the failure to a network communication or file-handling layer — QuickBooks located the file path but could not establish a stable read/write connection to the database hosted by the server manager. This distinguishes it from -6000, -77 (folder permissions) and -6000, -82 (file locked by another process), though all three share the same 6000-series family.

What Triggers It

The most common triggers, ordered by frequency in our case history, are:

1. The QuickBooks Database Server Manager is not running or is scanning the wrong folder on the host machine.
2. Network data file (.ND) is stale, corrupted, or points to an IP address or hostname that no longer matches the host.
3. The company file (.QBW) has sustained structural damage — typically in the transaction list or a list table — that prevents the database engine from mounting it.
4. Windows firewall or antivirus software is blocking inbound connections on the ports QuickBooks uses for multi-user access.
5. The host machine has multiple network adapters active (wired and wireless), causing QuickBooks to bind to the wrong IP.

How to Fix It

Scenario 1 — Database Server Manager is misconfigured or stopped (most common)

1. On the host machine, close QuickBooks.
2. Open the Windows Start menu, search for QuickBooks Database Server Manager, and open it.
3. If the service shows as stopped, click Start. If it is running, click Stop, wait ten seconds, then click Start.
4. Go to the Folders or Monitored Drives tab. Verify that the folder containing the company file is listed and checked. If it is not, click Add Folder, browse to the folder holding the .QBW file, and save.
5. Click Scan and allow the scan to complete fully. A confirmation should list the company file by name.
6. On the workstation, attempt to open the file in multi-user mode again.

Scenario 2 — The .ND file is stale or corrupted

1. On the workstation, navigate to the folder where the company file is stored (or the mapped network drive).
2. Locate the file ending in .ND that shares the company file name (for example, CompanyFile.QBW.ND).
3. Right-click the .ND file and select Rename. Add .OLD to the end so it becomes CompanyFile.QBW.ND.OLD.
4. Repeat this on the host machine if a copy of the .ND file exists there.
5. On the host machine, open QuickBooks Database Server Manager and run a folder scan as described in Scenario 1. This regenerates a fresh .ND file.
6. Open the company file on the workstation using the Open a company file option and browse to the network path rather than using a recent-file shortcut.

Scenario 3 — The company file itself is damaged

1. On the host machine, open QuickBooks and switch to Single-User Mode.
2. From the File menu, select Utilities, then Verify Data.
3. If Verify reports damage, run Rebuild Data from the same menu. You will be prompted to create a backup first — allow this.
4. After Rebuild completes, run Verify Data a second time. If it still reports problems, run Rebuild again.
5. If damage persists after a second Rebuild, the file has structural corruption that the built-in tools cannot resolve. At that point our engineers perform a manual database repair, which involves extracting the intact tables and rebuilding the damaged segments directly. In files with extensive transaction history, we often recommend pairing the repair with a supercondense in the same service window — this removes transactions before a cutoff date, reduces the overall file size, and improves long-term stability. List items such as accounts, customers, and vendors are preserved unless you explicitly request their removal.

Scenario 4 — Firewall or multi-adapter interference

1. On the host machine, open Windows Defender Firewall (or the third-party firewall in use).
2. Confirm that QuickBooks and QuickBooks Database Server Manager appear in the allowed apps list for both private and public networks.
3. If the host has both a wired and wireless adapter connected, temporarily disable the wireless adapter, then test file access from the workstation. If access succeeds, the dual-adapter configuration was the cause.

How to Prevent It Recurring

Keep the QuickBooks Database Server Manager set to start automatically with Windows on the host machine. After any server reboot, confirm the service is running before workstations connect. Avoid mapping drives with IP addresses that change — use the host computer name instead. Run Verify Data monthly on large or high-transaction files to catch structural issues before they escalate into access-blocking errors. Finally, ensure only one machine is configured as the host for the company file; conflicting hosting settings across workstations are a frequent contributor to 6000-series errors.