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

October 26, 2026 5 min read

QuickBooks Error 6189, 816 occurs when QuickBooks Desktop tries to open a company file that the operating system or database engine considers locked by another process, user, or temporary transaction file. This error typically surfaces in multi-user setups when a network connection drops mid-session, leaving a ghost connection behind, or when support files become desynchronized.

Fast-Fix: How to Resolve Error 6189, 816

To resolve Error 6189, 816, restart the host server or main computer hosting the company file to clear stranded file locks. Next, open the folder containing the company file on the host, locate the corresponding .ND and .TLG configuration files, and rename them to .ND.OLD and .TLG.OLD. Restart QuickBooks Database Server Manager to regenerate fresh connection files.

Quick Status & Triage Snapshot

  • Data Risk Tier: Low to Moderate (the company file is typically intact; the error usually reflects lock-file conflicts).
  • Multi-User Impact: High (all workstations or specific users are prevented from opening the file).
  • Common Trigger: Sudden network interruptions, workstation sleep states, active third-party cloud sync services, or mismatched file permissions.
  • Estimated Fix Time: 10 to 15 minutes.

Diagnostic Flowchart: Error 6189, 816 Decision Path

  1. Is the company file stored on a cloud folder (Dropbox, OneDrive, Box, Google Drive)?
    • Yes: Move the company file to a local drive or dedicated server folder immediately. Cloud sync engines lock .QBW and .TLG files during background synchronization.
    • No: Proceed to Step 2.
  2. Does the error happen on all computers or only one workstation?
    • All computers: The file lock is held at the server level. Restart the host database services and inspect server-side files.
    • One workstation: The issue is isolated to that workstation’s local QuickBooks cache, mapped drive path, or active processes.
  3. Does the error persist after restarting the host machine?
    • Yes: Corrupt network descriptor (.ND) or transaction log (.TLG) files are locking the database. Proceed to manual file renaming.
    • No: The issue was a stranded network session that cleared on reboot.

Technical Anatomy: What Causes the 6189, 816 Lockout?

QuickBooks Desktop maintains database state through two complementary mechanisms:

  1. The Transaction Log (.TLG): Tracks changes made to the database before they are permanently written to the .QBW file.
  2. The Network Descriptor (.ND): A text file containing the IP address, port, and hosting status of the database server manager.

When a user logs in, QuickBooks creates a temporary lock entry. If a workstation disconnects abruptly—due to a loose Ethernet cable, Wi-Fi stutter, or power loss—the host server’s operating system may continue to hold that user’s session open. When anyone tries to access the file again, the server reports that the file is in an exclusive-use state, generating Error 6189, 816.

Additionally, if a secondary workstation mistakenly has multi-user hosting turned on, it competes with the actual server for control of the file. For instructions on diagnosing this conflict, see Hosting Conflicts: Resolving Errors When Multiple PCs Act as the Server.

Step-by-Step Repair Guide

Step 1: Close Stranded Processes on Workstations

  1. On all client workstations, close QuickBooks.
  2. Press Ctrl + Shift + Esc to open Task Manager.
  3. Under the Processes or Details tab, locate any instances of:
    • QBW32.exe
    • qbupdate.exe
    • QBDBMgrN.exe
  4. Select each process and click End Task.

Step 2: Restart Host Services

  1. Log in to the server or host computer holding the company file.
  2. Press Windows Key + R, type services.msc, and press Enter.
  3. Scroll down and locate your version-specific QuickBooks database service:
    • QuickBooks 2026: QuickBooksDB36
    • QuickBooks 2025: QuickBooksDB35
    • QuickBooks 2024: QuickBooksDB34
  4. Right-click the service and select Restart.
  5. Also locate QBCFMonitorService, right-click it, and select Restart.

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

Step 3: Rename Damaged .ND and .TLG Files

Renaming these files forces QuickBooks to create clean connection records:

  1. On the host computer, navigate to the folder containing the .qbw file.
  2. Locate the files sharing the same name as your company file but ending in .ND and .TLG:
    • Example: CompanyFile.qbw.nd
    • Example: CompanyFile.qbw.tlg
  3. Right-click CompanyFile.qbw.nd and select Rename. Add .OLD to the end: CompanyFile.qbw.nd.old.
  4. Right-click CompanyFile.qbw.tlg and select Rename. Add .OLD to the end: CompanyFile.qbw.tlg.old.
  5. Open QuickBooks Database Server Manager from your Windows Start Menu, click Scan Folders, and scan the folder holding your company file. This recreates the .ND file.

For detailed background on how these support files operate, see Manual Fix: Renaming .ND and .TLG Files to Resolve 6000 Errors.

Step 4: Verify File Location and Network Path

Make sure the company file is not stored in an encrypted folder, an external USB hard drive prone to sleep states, or a non-standard network location. Workstations should access the file via a mapped drive letter rather than raw browsing. To confirm your drive setup, follow File Access: How to Map a Network Drive for QuickBooks Company Files.

Hard Stop: When to Call an Expert

Stop troubleshooting and evaluate your backup status if:

  • The .QBW file size suddenly displays as 0 KB.
  • Renaming the .TLG file fails because Windows reports continuous disk I/O hardware read errors.
  • The company file fails to open even when copied directly to the local desktop of the host computer.

Error 6189, 816 often appears alongside other network communication breakdowns:

Closing the Books

Error 6189, 816 is almost always a symptom of stranded network handles or file lock discrepancies rather than permanent database corruption. By systematically stopping orphaned background tasks, restarting the host database manager, and regenerating the .ND file, you can safely restore multi-user access without risking your company records.

Fix: QuickBooks in Multi-User Mode But Cannot Open the Company File

October 25, 2026

Troubleshoot: Fixing Greyed Out “Switch to Multi-User Mode” Menu

October 25, 2026

Hosting Guide: “Host Multi-User Access” vs. “Switch to Multi-User Mode”

October 25, 2026