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

QuickBooks Error 6189, 816 occurs when QuickBooks Desktop cannot open a company file because the database engine believes the file is already opened exclusively by another process, user, or application. You will typically see the message: “An error occurred when QuickBooks tried to access the company file… The company file is already in use.” To fix Error 6189, 816, close active QuickBooks sessions across all workstations, restart the host server’s database services, and rename the .ND and .TLG configuration files to release the locked database state.

Fast-Fix: The 45-Second Solution

To resolve Error 6189, 816, restart the host server or run services.msc to restart the QuickBooksDBXX service, then rename the .ND and .TLG files in your company folder. Error 6189, 816 occurs when an orphaned process or background backup program locks the database in Single-User Mode. Clearing these temporary support files and restarting the host database service releases the lock immediately.

Quick Status & Triage Snapshot

• Data Risk Tier: Low. This is a process-lock issue; the underlying company data is intact.
• Multi-User Impact: High. Blocks everyone from accessing the file until the exclusive lock is cleared.
• Common Trigger: A workstation crashing while a file was open in Single-User Mode, a background backup process (like OneDrive or Carbonite) locking the .qbw file, or an orphaned QBW32.exe process running in Windows Task Manager.
• Estimated Fix Time: 5 to 15 minutes.

Diagnostic Flowchart: Error 6189, 816 Decision Path

[Start: "Company File is Already in Use" Error 6189, 816 appears]
   │
   ▼
Is another user currently logged in under Single-User Mode?
   ├─► Yes ──► Have that user switch to Multi-User Mode (File > Switch to Multi-User Mode).
   └─► No ───► Check active Windows processes across machines.
          │
          ▼
Are there orphaned QBW32.exe processes running in Task Manager?
   ├─► Yes ──► End Task on all workstations, then reopen QuickBooks.
   └─► No ───► Proceed to server/host lock clearing.
                 │
                 ▼
              Is third-party backup software actively scanning the folder?
                 ├─► Yes ──► Exclude .QBW/.TLG from live scans; pause sync.
                 └─► No ───► Rename .ND and .TLG files and restart QuickBooksDB service.

Is Your Data at Risk?

Your data is safe. Error 6189, 816 is a protection mechanism built into the Sybase database engine. When a program or user performs an operation requiring exclusive access (such as rebuilding data or adjusting inventory values in single-user mode), the engine locks out all other connections to prevent data collisions. The error simply means the lock was not released properly when the session ended.

Technical Anatomy: What This Error Means

When a workstation connects to a .qbw file, the database engine creates locks using the Server Message Block (SMB) leasing mechanism and the local .ND (Network Data) file. If a workstation disconnects improperly, such as during a Windows crash, network timeout, or force-close—the server may not receive the disconnect packet.

As a result, the server marks the file as “checked out” in an exclusive single-user state. When a second user or workstation tries to open the file, the server reads the active lock flag and rejects the incoming connection with codes 6189 and 816. The same lock is triggered if automated backup or cloud synchronization software locks the file header while transferring data to the cloud.

Differential Diagnosis: Don’t Confuse This With…

• QuickBooks Error 6190, -816: While often occurring in tandem, Error 6190 specifically indicates that the transaction log (.tlg) pointer does not match the company file (.qbw), rather than a general process lock.
• QuickBooks Error H202: Indicates that the workstation cannot reach the server’s IP address across the network. With 6189, 816, the workstation can reach the server, but the file is locked.
• QuickBooks Error 6000, -83: A hosting configuration error where the server itself cannot access its own file storage system.

Step-by-Step Repair Guide

Follow these steps in sequence to locate and clear the process holding the file open.

Step 1: Terminate Orphaned QuickBooks Processes

An unclosed background process can hold an exclusive file lock even when QuickBooks looks closed on your screen.

1. On all client workstations, press Ctrl + Shift + Esc to open Task Manager.
2. Go to the Details or Processes tab.
3. Look for any instance of QBW32.exe, QBDBMgr.exe, or QBUpdate.exe.
4. Select each process and click End Task.
5. Repeat this check on every workstation that accesses the file.

Step 2: Restart the Host Server and Database Services

Restarting the host service breaks any stale locks maintained by the operating system.

1. On the host server, press Windows Key + R, type services.msc, and press Enter.
2. Locate the service corresponding to your QuickBooks version (for example, QuickBooksDB34 for 2024 or QuickBooksDB36 for 2026).
3. Right-click the service and select Restart.
4. Locate QBCFMonitorService, right-click it, and select Restart.
   (If you are running QuickBooks in a peer-to-peer setup without a dedicated server, simply restart the host computer).

Step 3: Rename .ND and .TLG Support Files

Stale lock flags are often cached in the support files sitting next to your company data.

1. Open File Explorer and browse to the folder where your company file is stored.
2. Locate the two files matching your company file name:
   • [YourCompanyName].qbw.ND
   • [YourCompanyName].qbw.TLG
3. Right-click each file and rename them:
   • Rename to [YourCompanyName].qbw.ND.old
   • Rename to [YourCompanyName].qbw.TLG.old
4. Do not delete or rename the main .qbw file.
5. Reopen QuickBooks Desktop on the host computer first, then open it on client workstations. Fresh support files will be created automatically without locks.

Step 4: Check for Conflicting Cloud Sync and Backup Utilities

If Error 6189, 816 returns repeatedly, a background program is likely scanning the database.

1. Check the system tray on the host machine for active sync applications:
   • Dropbox, Microsoft OneDrive, Google Drive, Box, or Carbonite.
2. Ensure your active company file folder is excluded from live, real-time cloud synchronization.
3. If cloud backups are required, schedule them to run outside of business hours when all users have logged out of QuickBooks.

Hard Stop: When to Call an Expert

Cease troubleshooting and seek technical support if:

• Windows Server reports persistent file lock handles on the .qbw file that cannot be closed through Computer Management (fsmgmt.msc) even after restarting server services.
• The company file is hosted on a non-Windows storage system (such as a Linux SAMBA share or proprietary NAS) that lacks support for opportunistic locking controls.
• The error appeared during a file encryption or ransomware event.

Related Errors

If you continue to experience file lock or hosting issues, consult these guides:

• QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies
• Manual Fix: Renaming .ND and .TLG Files to Resolve 6000 Errors
• Multi-User Fix: How to Turn Off Hosting on All QuickBooks Workstations
• Service Fix: Troubleshooting “QuickBooks Database Server Manager Stopped”
• The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor

Closing the Books

Error 6189, 816 is a temporary operational roadblock, not a sign of damaged ledgers. The error exists to prevent multiple users from corrupting records when a single-user task is running. Once background processes are closed, the host database services are restarted, and temporary lock files are renamed, your team will be able to access the company file without issue.