QuickBooks Error 6189, 816: How to Fix “Company File is Already in Use”

November 9, 2026 7 min read

QuickBooks Error 6189, 816 occurs when QuickBooks Desktop attempts to open a company file, displaying the message: “An error occurred when QuickBooks tried to access the company file… The file is already in use.” This error triggers when another user has the file open in single-user mode, a background process locked the database file, or network support files (.ND and .TLG) are holding stale lock states. You can resolve Error 6189, 816 by closing hung background QuickBooks processes, restarting the host server’s database service, and renaming the .ND and .TLG files.

Fast-Fix: The 45-Second Solution

To fix QuickBooks Error 6189, 816, restart the host server and all client workstations to release active file locks. If restarting is not immediately possible, close QuickBooks on all computers, open Task Manager on the host, terminate any running qbw32.exe or qbupdate.exe processes, and restart the QuickBooksDB## service in services.msc. Finally, rename the .ND and .TLG files in the company folder to .ND.old and .TLG.old.

Quick Status & Triage Snapshot

  • Error Code Pair: 6189, 816 (Indicates an active file-lock conflict between two or more processes).
  • Data Risk Tier: Low. This is an operational file-access block, not corruption of your company records.
  • Multi-User Impact: High. Workstations are locked out of the company file until the hanging process or stale lock token is cleared.
  • Common Triggers: A user opening the file in Single-User Mode, automated cloud backup tools (such as OneDrive or Dropbox) scanning the file, or a crashed QuickBooks process remaining active in Windows Task Manager.
  • Estimated Fix Time: 5 to 15 minutes.

Technical Anatomy: How File Lock Contention Triggers Error 6189, 816

When QuickBooks Desktop opens a company file, it negotiates access permissions through the Sybase database engine (qbdbmgrn.exe):

  1. Shared vs. Exclusive File Locks: In Multi-User Mode, QuickBooks allows multiple client connections by placing shared read/write locks on the .QBW file. If a single user chooses Switch to Single-User Mode, QuickBooks requests an exclusive file lock. If another user is already logged in, or if a background utility has touched the file, the exclusive lock fails.
  2. Ghost Processes: When a workstation crashes or loses network connectivity, the Windows operating system on the server may not immediately register that the client disconnected. The server’s file system continues to maintain an active open-file handle for that ghost session.
  3. Third-Party File Interception: If automated cloud backup services or real-time antivirus scanners inspect the .QBW, .TLG, or .ND files while QuickBooks is running, the scanner places a temporary read lock on the file. When another user attempts to open the file during this millisecond window, the database engine returns Error 6189, 816.

Diagnostic Flowchart: Error 6189, 816 Decision Path

Start: Error 6189, 816 appears
 │
 ├──> Is a user logged in using Single-User Mode?
 │     ├── YES ──> Switch that workstation to Multi-User Mode (File > Switch to Multi-User Mode).
 │     └── NO  ──> Proceed to process check.
 │
 ├──> Check Task Manager on all workstations and server
 │     ├── Are lingering qbw32.exe or qbupdate.exe processes active?
 │     │     └── YES ──> End processes across all computers.
 │     └── No lingering processes found?
 │
 ├──> Is the company file stored in a cloud-synced folder (Dropbox, OneDrive, Box)?
 │     ├── YES ──> Move file to a standard local/server directory (e.g., C:\QBData\).
 │     └── NO  ──> Proceed to network support file reset.
 │
 └──> Rename .ND and .TLG files and restart QuickBooksDB## service on host.

Step-by-Step Repair Guide

Work through these steps in order. Test company file access after each step.

Step 1: Check for Active Single-User Mode Access

The most straightforward cause of Error 6189, 816 is a colleague performing an exclusive task (such as rebuilding data, paying payroll taxes, or running financial year-end routines).

  1. Ask all users on the network to check their current QuickBooks status.
  2. If any user has opened the file in Single-User Mode, have them complete their work, click File, and select Switch to Multi-User Mode.
  3. If no user is intentionally in Single-User Mode, have every user log out and close QuickBooks Desktop completely.

Step 2: Terminate Ghost QuickBooks Processes via Task Manager

When QuickBooks freezes or closes unexpectedly, the qbw32.exe process can stay running in the background, keeping the .QBW database handle locked.

  1. On each client workstation, press Ctrl + Shift + Esc to open Task Manager.
  2. Click More details if you are in compact view, then select the Details tab.
  3. Sort by Name and look for:
    • qbw32.exe
    • qbupdate.exe
    • QBDBMgr.exe
  4. If found, right-click each process and select End task.
  5. Repeat this check on the host server hosting the company file.

Step 3: Restart the QuickBooks Database Server Manager on the Host

Restarting the host service clears open file handles maintained by the operating system.

  1. On the host server, press Windows Key + R, type services.msc, and press Enter.
  2. Locate the service matching your version of QuickBooks Desktop (e.g., QuickBooksDB34 for 2024 or QuickBooksDB35 for 2025).
  3. Right-click the service and select Restart.
  4. Locate QBCFMonitorService, right-click it, and select Restart.

If the database service refuses to start or crashes, review Service Fix: Troubleshooting “QuickBooks Database Server Manager Stopped”.

Step 4: Rename the .ND and .TLG Support Files

Corrupted Network Data (.ND) files store outdated network connection flags that report the company file as busy when it is actually idle.

  1. Open Windows File Explorer on the host computer or server.
  2. Navigate to your company file directory (for example, C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
  3. Locate the files with the matching name of your company file ending in .ND and .TLG:
    • YourCompanyFile.qbw.nd
    • YourCompanyFile.qbw.tlg
  4. Right-click YourCompanyFile.qbw.nd and rename it to YourCompanyFile.qbw.nd.old.
  5. Right-click YourCompanyFile.qbw.tlg and rename it to YourCompanyFile.qbw.tlg.old.
  6. Open QuickBooks Database Server Manager on the server, go to the Scan Folders tab, and rescan the directory to create clean files.

For full manual file renaming instructions, consult Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors.

Step 5: Check and Disable Cloud Storage Syncing

Storing an active QuickBooks company file inside a cloud-synced directory will cause recurring 6189, 816 errors.

  1. Check the path where your company file resides. If it contains words like OneDrive, Dropbox, Google Drive, Box, or iCloud, the cloud software is constantly locking the file during sync intervals.
  2. Move the company file directory to a dedicated, un-synced folder on your primary drive (e.g., C:\QuickBooks Data\).
  3. If hosting in a multi-user environment, share that un-synced folder across the local network using standard Windows share permissions.

Hard Stop: Persistent File Locks and Server Reboot

If you have terminated all background processes, renamed the support files, and verified no cloud storage is active, yet Windows reports the file is still in use, the server operating system is holding an unreleased Opportunistic Lock (OpLock) on the disk.

Perform a clean reboot of the host server. A server reboot forces the operating system kernel to release all locked network handles, flushing the system memory and clearing hung database threads. If the error returns immediately upon restarting, run The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor.

QuickBooks Error 6129, 0: Fixing Database Connection Verification Failures

November 7, 2026

QuickBooks Error 6130: Resolving Database Server Connection Problems

November 7, 2026

QuickBooks Error 6123, 0: Troubleshooting Lost Connections to Company Files

November 7, 2026