QuickBooks Error 6120, 816
Let’s Dive in to see…
How to Fix QuickBooks Error 6120, 816
QuickBooks Company File Error · 6xxx Series · Multi-User Exclusive Lock
How to Fix QuickBooks Error 6120, 816
QuickBooks displays: "QuickBooks cannot open this company file. Error code: -6120, -816" — typically when a workstation tries to open or access the company file in a multi-user environment.
At QuickFix Bookkeeping, the -816 suffix is the diagnostic key: -816 always means an exclusive lock — either a user has the file open in single-user mode, or a stale lock remains from a session that ended abnormally. Error 6120, -816 combines this exclusive lock with a network communication failure: the workstation can't reach the file AND finds it locked. Fix both: clear the lock and fix the network path.
6120, -816 vs 6120, 0 vs 6189, -816 — The Distinctions
6120, -816 — this page
Network communication failure PLUS exclusive lock. Both layers need fixing: clear the lock AND fix network/QBDSM. Often appears when a user crashes during single-user mode on a multi-user network.
6120, 0
.ND file corrupted or hosting mismatch. No lock component — purely a network descriptor file issue. Fix: rename .ND + QBDSM rescan.
6189, -816
Transaction log mismatch causing an exclusive lock. .TLG doesn't match .QBW after a session ended abnormally. Fix: rename .TLG first, then address hosting.
What Causes QuickBooks Error 6120, 816?
User Crashed During Single-User Mode
Primary 6120-816 cause — a user switched to single-user mode (for reconciliation, payroll, etc.) and then QB crashed or the network dropped. The file is now exclusively locked (from single-user mode) AND the network path shows an error (6120 component). Find and clear the lock first, then verify QBDSM is running.
Stale .lock File + QBDSM Not Running
A stale .QBW.lock file persists from a crashed session AND the QuickBooksDB service on the host has stopped. Both conditions simultaneously produce 6120, -816. Delete the .lock file and restart the QuickBooksDB service to resolve both.
Firewall Change After Single-User Lock
A Windows Update changed firewall rules while a user was in single-user mode. When they exited, the lock persisted (the exit didn't complete cleanly through the new firewall) AND workstations now can't communicate with the host through the changed rules. Fix the firewall rules AND clear the stale lock.
Network Outage During Active Session
A network switch, router, or server restarted while users were active in QB. Sessions didn't close cleanly — leaving locks — and now the network path is also changed. All affected workstations see 6120, -816 until locks are cleared and QBDSM rescans the updated network path.
Wrong QB Version on One Machine
A workstation running a different QB version tries to access the file. It gets the 6120 network error (version mismatch prevents proper communication) and also sees -816 if the file is in single-user mode from another machine. Update all machines to the same QB version.
Hosting Misconfigured After Workstation Restart
After a workstation restart, that machine's QB re-enables multi-user hosting (a known QB bug with some versions). It now competes with the server, causing network confusion (6120) and showing the file as locked (-816).
How to Fix QuickBooks Error 6120, 816
Related QuickBooks Errors
Error 6120, 816 After Full Host Restart and QBDSM Rescan?
Let QuickFix Bookkeeping Resolve the Combined Lock and Network Issue.
Persistent 6120, -816 after a full host restart means either a third-party security product is re-blocking QBDSM's ports or a version mismatch is preventing the lock from releasing properly — we diagnose both layers simultaneously.
Book a Free 30-Minute ConsultationNo obligation. Same-day response.