QuickBooks Error 6189, 816: Expert Fix for Multi-User File Lock
Introduction
You open QuickBooks Desktop on a workstation, ready to process payroll or send invoices. Instead of your company file, you see: "An error occurred when QuickBooks tried to access the company file (-6189, -816)"
The software refuses to open. Your team is locked out. Payroll is due.
As a QuickBooks ProAdvisor, I have resolved QuickBooks Error 6189, 816 for businesses of every size. The good news: 6189 is almost always a file lock or .TLG desync issue, not data loss.
The error is part of the 6000-series company file errors, and it has well-documented, reliable fixes. This guide explains exactly what Error 6189, 816 is, why it happens, and the proven steps to eliminate it.
What Is QuickBooks Error 6189, 816?
QuickBooks Error 6189, 816 is a company file access error that occurs when QuickBooks cannot open the company file in multi-user mode because an exclusive lock is held . The error typically appears with a message like:
"An error occurred when QuickBooks tried to access the company file (-6189, -816)"
Critical distinction: Per Intuit's own documentation, there is an issue with your multi-user network, not with your data file . The -816 suffix specifically means the company file is exclusively locked—QuickBooks found the file but another process holds a lock preventing access .
Your financial data is safe. The lock blocks access, not damages data. In Error 6189, that lock comes from either a live single-user mode session or a desynchronized .TLG transaction log .
Error 6189 belongs to the broader 6000-series of company file errors, which all relate to file access, network configuration, and multi-user hosting problems .
Quick Summary
Aspect
Error Type
Affected Software
Common Triggers
Primary Risk
Data Safety
Fix Difficulty
Details
Multi-user file lock / .TLG desync
QuickBooks Desktop (Pro, Premier, Enterprise)
Live single-user session, .TLG desync after crash, stale .lock file, QBDSM not running
Company file cannot be opened in multi-user mode
File data intact; access is blocked, not damaged
Low to Moderate — server-first restart and .TLG rename resolve most cases
Why QuickBooks Error 6189, 816 Occurs
Understanding the root cause helps you fix it correctly the first time. Error 6189, 816 stems from an exclusive lock on the company file. Common causes include :
1. Active Single-User Mode Session (Most Common)
Another user has the company file open in single-user mode, which places an exclusive lock. No workstation can switch to multi-user while this lock is held. The fix is to find that user, have them switch to multi-user mode (File → Switch to Multi-user Mode), or close QuickBooks entirely.
2. .TLG Desync After Abnormal Shutdown
A power failure, forced shutdown, or network interruption mid-session leaves the .TLG transaction log out of sync with the .QBW file. QuickBooks detects the mismatch and refuses to open the file to prevent data damage. Renaming the .TLG forces QuickBooks to create a clean one—no data is lost through this process.
3. Stale .QBW.lock File
When QuickBooks exits cleanly, it deletes its lock file. When it crashes or is force-closed, the .QBW.lock file remains on disk. The next time someone tries to open the file, QuickBooks sees the orphaned lock, interprets it as an active session, and produces 6189, 816. Deleting the stale .lock file resolves this.
4. Old QBDSM Version After QuickBooks Upgrade
After upgrading QuickBooks (e.g., from QB 2022 to QB 2023), the old QuickBooksDB32 service may keep running alongside the new one. Two QBDSM versions competing for the same company file can produce lock conflicts and 6189 errors .
How Error 6189, 816 Shows Up: Symptoms to Recognize
Before applying fixes, confirm you are dealing with Error 6189, 816. The symptoms typically include :
Error message on screen: "An error occurred when QuickBooks tried to access the company file (-6189, -816)"
Company file fails to open: QuickBooks cannot access the file in multi-user mode
Only one user can open the file: The file is locked by a single-user session
Error appears after a crash or power outage: The .TLG is likely desynced
Multi-user mode fails: Workstations cannot connect to the hosted company file
QuickBooks Error 6189, 816: Expert Troubleshooting Steps
Follow these steps in order. Method 1 (Server-First Restart) resolves many 6189 cases. Start there before running other tools .
Method 1: Server-First Restart (Primary Fix for Lock Issues)
This is the fastest and most effective fix for Error 6189. The critical rule is to restart the server before the workstations .
Steps:
Close QuickBooks completely on ALL computers (server and workstations).
Restart the server computer (the one hosting the company file) .
Wait for the QuickBooksDBXX service to show "Running" in Windows Services (services.msc) .
Restart each workstation one at a time .
Open QuickBooks on the server first, then on workstations.
Why this order matters: If workstations restart first, they reconnect to the server before it has cleared the old session state—perpetuating the error .
Method 2: Rename the .TLG and .ND Files
If the server-first restart does not resolve the error, the .TLG file is likely desynced. Renaming it forces QuickBooks to create a fresh copy .
Steps:
Close QuickBooks completely on all computers.
Navigate to the folder containing your company file (typically C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
Find the files with the same name as your company file but with .TLG and .ND extensions (e.g., CompanyName.qbw.TLG and CompanyName.qbw.ND) .
Right-click each file and select Rename.
Add .OLD to the end of the filename (e.g., CompanyName.qbw.TLG.OLD) .
Do not delete the original files—renaming preserves them as backups.
Reopen QuickBooks. It creates fresh .TLG and .ND files automatically .
Important: Renaming the .TLG loses only uncommitted transactions. All committed data in the .QBW file is safe.
Method 3: Delete the Stale .QBW.lock File
If a .QBW.lock file remains from a crashed session, QuickBooks interprets it as an active lock .
Steps:
Close QuickBooks on all computers.
Navigate to the folder containing your company file.
Look for a file named CompanyName.qbw.lock (or similar).
Delete the .lock file.
Reopen QuickBooks and try opening the company file.
Method 4: Run Quick Fix My Program via Tool Hub
QuickBooks Tool Hub provides automated repair utilities for program and network issues.
Steps:
Close QuickBooks Desktop.
Download and open QuickBooks Tool Hub from Intuit's official site .
Select the Program Problems tab.
Click Quick Fix My Program .
Once complete, reopen QuickBooks and retry.
Method 5: Run QuickBooks Database Server Manager
The QuickBooks Database Server Manager on the server must be running and scanning the company file folder .
Steps:
On the server computer, open QuickBooks Tool Hub.
Select Network Issues .
Click QuickBooks Database Server Manager .
Select Start Scan if you see your company files. If not, browse to the company file location and select Start Scan .
The tool automatically repairs firewall permissions.
Click Close, then open QuickBooks on the server and workstations.
Method 6: Move Company File to Local Drive
If the company file is stored on a removable drive or cloud-synced folder (Dropbox, Google Drive, OneDrive), move it to a local hard drive .
Steps:
Copy the company file (and its .ND/.TLG files) to a local drive on the server (e.g., C:\Company Files\) .
Open QuickBooks and select Open or Restore Existing Company.
Browse to the new location and open the file.
If it opens successfully, the original storage location was the issue.
Important: QuickBooks best practices explicitly state: do not store files on removable drives, external drives, or cloud-synced folders. They are not designed for QuickBooks or multi-user networks .
Method 7: Check for Old QBDSM Versions
After a QuickBooks upgrade, old Database Server Manager services may compete with the new one .
Steps:
Open Services (services.msc) on the server.
Look for multiple QuickBooksDBXX services (e.g., QuickBooksDB32 and QuickBooksDB33).
Disable the old version's service (set Startup type to Disabled) .
Restart the server and retry.
Real-World Example: Fixing Error 6189, 816 Before Month-End Close
A manufacturing company contacted me on the last day of the month. Their QuickBooks Desktop Enterprise displayed Error 6189, 816 every time a workstation tried to open the company file. Three accounting staff were locked out.
Diagnosis: A power outage had crashed QuickBooks mid-session. The .TLG file was desynced, and a stale .QBW.lock file remained. The hosting layer was stuck in a single-user state .
Steps Taken:
Closed QuickBooks on all computers.
Restarted the server first, waited for QuickBooksDBXX to show "Running" .
Renamed the .TLG and .ND files to force fresh recreation .
Deleted the stale .QBW.lock file .
Restarted workstations one at a time .
All workstations reconnected successfully.
Result: Total resolution time: 18 minutes. The client completed the month-end close on schedule.
Lesson: Error 6189, 816 often has multiple contributing causes. The server-first restart combined with .TLG rename resolves most cases quickly .
How to Prevent QuickBooks Error 6189, 816
Prevention is simpler than repair. Follow these maintenance practices:
Close QuickBooks properly on all machines—use File > Exit, not the X button
Avoid abrupt system shutdowns during QuickBooks sessions
Restart the server first when clearing network issues
Store company files on a local drive, not cloud-synced or removable storage
Disable old QBDSM services after QuickBooks upgrades
Run QuickBooks Database Server Manager scans after Windows updates
Back up company files regularly
Frequently Asked Questions
What does QuickBooks Error 6189, 816 mean?
Error 6189, 816 means QuickBooks cannot access your company file because an exclusive lock is held—either by a live single-user session or a desynced .TLG file. The -816 suffix means "file exclusively locked" .
Will I lose company data because of Error 6189, 816?
No. Error 6189 is a file lock error. Your company file data remains intact. Only uncommitted transactions in the .TLG file may be lost when you rename it .
What is the fastest way to fix QuickBooks Error 6189, 816?
A server-first restart—closing QuickBooks everywhere, restarting the server, then restarting workstations—is the fastest fix. If that fails, rename the .TLG and .ND files .
What is the difference between Error 6189 and Error 6190?
Error 6189 has a live-lock cause (someone is actually in single-user mode). Error 6190 is a stale desync where no one is actively in single-user mode. Both are fixed by renaming the .TLG .
Can QuickBooks Tool Hub fix Error 6189, 816?
Yes. QuickBooks Tool Hub includes Quick Fix My Program and QuickBooks Database Server Manager, both of which can resolve program and network issues contributing to 6189 .
Why does Error 6189, 816 keep coming back?
Recurring 6189 may indicate persistent hosting misconfiguration, an old QBDSM version conflicting with the new one, or company file storage on a cloud-synced folder .
What is the difference between Error 6189 and Error 6175?
Error 6189 is a file lock issue (.TLG desync or single-user session). Error 6175 is a database service issue (QBDBMgrN not running). Different root causes require different fixes .
When should I seek professional help for Error 6189, 816?
If you have tried all solutions above and Error 6189 persists, or if the error affects multiple users across a network, professional support can diagnose underlying issues.
Conclusion
QuickBooks Error 6189, 816 is frustrating, but it is rarely permanent. The error signals a multi-user file lock—a live single-user session, a desynced .TLG file, or a stale .lock file—not data loss. By following the server-first restart rule, renaming the .TLG and .ND files, and clearing stale lock files, you can resolve Error 6189 and restore multi-user access quickly .
When month-end close or payroll deadlines approach and the error blocks your team, expert help saves time and protects your business.
Stuck on QuickBooks Error 6189, 816 and need it fixed now? Call our Data Service Team at +1-(888)-718-7888 for fast, expert resolution and get your team back to work.