QuickBooks Error -6000, -95 -- Stale Network Lock on Company File

QuickBooks Error -6000, -95 blocks company file access when a stale lock remains active; our engineers walk through clearing it and restoring multi-user connectivity.

QuickBooks Error -6000, -95 is a 6000-series company file access error that occurs when QuickBooks Desktop cannot open a company file because another process retains a lock on it. The lock may be held by a legitimate active session, a crashed workstation that did not release the file cleanly, or a stale .tlg (transaction log) or .nd (network descriptor) file pointing to a session that no longer exists. Our engineers encounter this most often in multi-user environments where one workstation has frozen or lost its network connection mid-session, leaving behind lock artifacts that block subsequent open attempts.

What the Error Message Says

When the error fires, QuickBooks displays a dialog containing text similar to:

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

The message may also reference the specific file path and filename that QuickBooks attempted to open.

What the Code Means

The -6000 prefix indicates a company-file-level access failure — QuickBooks reached the file but could not complete the open sequence. The -95 sub-code specifically points to a lock conflict: the database service manager detected that a .tlg or .nd lock is already held, preventing the current session from acquiring exclusive or shared access. In most cases the process holding the lock is not genuinely active; it is a remnant from a prior session.

What Triggers It

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

1. A workstation crashed or lost network connectivity while the company file was open, leaving behind a stale transaction log lock.
2. Multiple users attempted to open the file simultaneously and the database manager could not serialize the requests cleanly.
3. The QuickBooks Database Server Manager service stopped or restarted while sessions were active.
4. The .nd file is corrupted or references an old server name or IP, causing QuickBooks to attempt a connection to a non-existent host and leaving a partial lock.
5. A backup, sync, or third-party application (such as a reporting tool or CRM integration) holds a silent ODBC connection to the file.
6. The server rebooted unexpectedly due to a Windows update or power event while users were logged in.

How to Fix It

Scenario 1: A Stale Lock From a Crashed or Disconnected Workstation (Most Common)

1. On every workstation, close QuickBooks completely. Verify in Task Manager that no QBW32.exe process is running.
2. On the server hosting the company file, open Services (press Win + R, type services.msc, press Enter).
3. Locate QuickBooksDBXX (where XX is your version number, e.g., QuickBooksDB33 for 2023). Right-click and select Stop.
4. Wait 10 seconds, then right-click and select Start.
5. Attempt to open the company file on the server first, then on each workstation.

If the error persists after restarting the database service, the .tlg file itself is holding the stale lock:

6. On the server, navigate to the folder containing the .QBW company file.
7. Locate the .TLG file with the same base name as your company file (e.g., CompanyFile.QBW.TLG).
8. Rename it to CompanyFile.QBW.TLG.OLD.
9. Attempt to open the company file again.

Scenario 2: Corrupted Network Descriptor (.ND) File

1. On the server, navigate to the company file folder.
2. Locate the .ND file with the same base name as your company file.
3. Rename it to CompanyFile.QBW.ND.OLD.
4. Open QuickBooks Database Server Manager on the server.
5. Run the Scan Folders function on the directory containing the company file. This generates a fresh .ND file.
6. Attempt to open the company file from a workstation.

Scenario 3: A Third-Party Application Holds a Silent Connection

1. Close all third-party applications that integrate with QuickBooks (reporting tools, CRM connectors, document managers).
2. On the server, open Computer Management → Shared Folders → Open Files.
3. Look for any open handle on the .QBW file that is not from a QuickBooks process.
4. Right-click that handle and select Close Open File.
5. Attempt to open the company file in QuickBooks.

Scenario 4: Database Server Manager Service Misconfiguration

1. On the server, open Services.
2. Confirm that QuickBooksDBXX is set to Automatic startup and is currently Running.
3. Confirm that QBCFMonitorService is also set to Automatic and Running.
4. If either service is stopped or set to Manual, correct the startup type, start the service, and retry.

How to Prevent It Recurring

• Train users to close QuickBooks before shutting down or docking/undocking laptops, as an abrupt disconnect is the leading cause of stale locks.
• Configure the server to install Windows updates on a schedule and reboot automatically during a maintenance window, not during business hours.
• Run QuickBooks Database Server Manager's folder scan after any server name, IP address, or folder path change so the .ND file stays current.
• Periodically verify that no third-party integrations are configured to maintain persistent connections to the company file outside of active use sessions.
• Ensure all workstations are on the same QuickBooks version and release, as version mismatches can cause the database manager to handle locks inconsistently.