QuickBooks Error 6000-85 -- Network Company File Access Failure

QuickBooks error 6000-85 blocks opening a company file stored on a network share. Learn what causes it and how our engineers restore access.

When you try to open a company file that sits on another computer or a network drive, QuickBooks Desktop can stop with error 6000-85. The file itself is usually fine. The failure is in the connection between your workstation and the folder that holds the file. Our engineers treat this as a path and permissions problem first, and only a data problem if the connection checks out.

What does the error message say?

The message typically reads:

"An error occurred when QuickBooks tried to access the company file. Please try again. If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6000, -85)."

Some installations show a shorter form: "Error -6000,-85: An error occurred when QuickBooks tried to access the company file." Either way, QuickBooks refuses to open the file and does not offer a retry path that works.

What does error 6000-85 mean?

The 6000 series covers company file access and data integrity failures. The -85 suffix points specifically at a failure to reach or read the file across the network path. QuickBooks asked the operating system for the file, and the operating system could not deliver it. That distinguishes it from codes like 6000-83, where the database server connection itself is the fault line. Here, the share, the mapped drive, or the permissions on the folder are the usual suspects.

What triggers error 6000-85?

The most common triggers we see are:

1. The mapped drive letter or network path has changed, often after a reboot, a server rename, or an IP address change.
2. The Windows user account on the workstation lacks read and write permissions on the shared folder.
3. The folder hosting the file is not shared correctly, or the share was removed during server maintenance.
4. A VPN or network connection dropped mid-session, leaving QuickBooks with a stale path.
5. Another process, such as a backup job or sync tool, is holding the file open with an exclusive lock.
6. The QuickBooks Database Server Manager is not running or has not scanned the folder, so hosted-mode access fails.

How to fix it

Work through these scenarios in order. The first resolves most cases.

Scenario 1: The network path or mapped drive is stale.

1. On the computer hosting the file, confirm the folder is shared and note the exact share name.
2. On the workstation, press the Windows key, type the UNC path directly (two backslashes, the host computer name, then the share name), and press Enter.
3. If the folder opens, browse to the company file inside it and double-click the file directly. Opening the file through the UNC path bypasses a broken mapped drive.
4. If that works, remap the drive or update your shortcut to use the UNC path permanently.

Scenario 2: Windows permissions are blocking access.

1. On the host computer, right-click the folder holding the company file and open Properties, then the Sharing tab.
2. Confirm the user on the workstation has access at both the share level and the Security tab. Windows checks both, and either one can block you.
3. Grant full control to the user (or to a group the user belongs to) at both levels, then apply.
4. Sign out of Windows on the workstation and sign back in so the new permissions take effect, then open the file again.

Scenario 3: The Database Server Manager has not scanned the folder.

1. On the host computer, open QuickBooks Database Server Manager.
2. Add the folder that contains the company file to the scan list.
3. Run a full scan and wait for it to finish.
4. Return to the workstation and open the company file through the File menu, choosing Open or Restore, then the network path.

Scenario 4: Another process is locking the file.

1. Check whether a backup, sync, or antivirus scan is running against the folder. Pause or reschedule it.
2. Restart the host computer to release any stuck file handles.
3. Open the file in single-user mode first. If it opens, switch back to multi-user mode.

Scenario 5: The connection itself is unstable.

1. Ping the host computer by name from the workstation to confirm name resolution works.
2. If pings fail, check the VPN, firewall, and network profile on both machines.
3. Once the ping succeeds, open the file through the UNC path.

How do you prevent error 6000-85 from coming back?

Use the UNC path rather than a mapped drive letter wherever possible; drive letters break, host names rarely do. Keep the sharing and security permissions aligned on the host folder. Run Database Server Manager scans after any folder move. Finally, exclude the company file folder from real-time antivirus scans and schedule backups for hours when nobody has the file open.