QuickBooks Error 6000-816
Single-User Lock Conflict
Let’s Dive in to see…
How to fix QuickBooks Error=6000-816
on Workstations — Single-User Lock Conflict
QuickBooks Error 6000,-816 · On Workstations · Single-User Lock
QuickBooks Error 6000-816 on Workstations — Single-User Lock Conflict
QuickBooks displays: "An error occurred when QuickBooks tried to access the company file (-6000, -816)" — specifically on a workstation when another user is in single-user mode on a different machine.
The -816 sub-code always means an exclusive lock. On workstations specifically, this almost always means: another user switched to single-user mode for a task (payroll, reconciliation) and hasn't switched back — or their QB crashed before they could release the single-user lock. At QuickFix Bookkeeping, the workstation fix is different from the server fix: you need to find who holds the lock and either wait for them or clear it.
Workstation 6000-816 — Find Who Holds the Lock First
Before clearing anything, find who holds the lock. QB → Company → Users → View Users → look at who's logged in and their mode. Or: navigate to the company file folder on the server → look for CompanyName.QBW.lock — this file only exists when someone is in single-user mode. If you see the .lock file: someone is genuinely in single-user mode. Message them to switch back (File → Switch to Multi-user Mode) and wait. Only clear the .lock file manually if you've confirmed no user is actively in QB — a stale .lock from a crash is safe to delete; a live .lock must be released properly or data could be lost.
What Causes 6000-816 on Workstations?
Another User Actively in Single-User Mode
Most common workstation 6000-816 cause — a colleague is legitimately using single-user mode for a task. This isn't an error — it's QB working correctly. The workstation must wait. Ask the single-user mode holder to complete their task and switch back: File → Switch to Multi-user Mode.
Stale Lock from Crashed Single-User Session
A user was in single-user mode and QB crashed before they could switch back. The .lock file persists on the server, and all workstations see 6000-816. After confirming no QB is actually running anywhere: delete the stale .lock file from the company file folder → workstations can connect again.
Network Drop During Single-User Mode
A network interruption cut off the single-user session without cleanly releasing the lock. The user's QB shows an error or disconnects, but the .lock file on the server remains. Confirm that user's QB is closed → delete the stale .lock file → other workstations can connect.
Server Restart While Single-User Lock Was Active
The server or file host was restarted while a user was in single-user mode. The restart cleared the QB process but the .lock file persisted in the file system. After server restart: check for and delete any remaining .lock files before users try to reconnect.
Backup Software Holding Exclusive Lock
A backup application acquired an exclusive read lock on the company file during a scheduled backup, producing the same -816 behaviour as a single-user lock. The lock releases when the backup completes. Schedule backups for after hours when no users are in QB to prevent this.
Workstation Itself in Single-User Mode
The workstation showing 6000-816 is itself currently in single-user mode — QB on that machine can't switch to multi-user because it holds the lock. File → Switch to Multi-user Mode on that same workstation, then retry.
How to Fix 6000-816 on Workstations
Related QuickBooks Errors
6000-816 on Workstation After Deleting .lock and Full Restart?
Let QuickFix Bookkeeping Find What's Re-Creating the Lock.
Persistent 6000-816 after full restart and .lock deletion means a system service (backup agent, AV, VSS) is immediately re-acquiring an exclusive lock — we use Process Monitor to identify and stop it.
Book a Free 30-Minute ConsultationNo obligation. Same-day response.