QuickBooks Error 6144, 816
Let’s Dive in to see…
How to Fix QuickBooks Error=6144, 816
QuickBooks Error 6144, -816 · Permission Denied + Exclusive Lock
How to Fix QuickBooks Error 6144, 816
QuickBooks displays: "Error codes: -6144, -816" when opening a company file — two simultaneous problems combining a permission failure and an exclusive lock.
At QuickFix Bookkeeping, Error 6144, -816 is a compound error: the -6144 component means QB was denied access to the file (permission issue), and the -816 component means the file is also exclusively locked. Both must be resolved — clearing only the lock leaves the permission issue, and fixing only the permission leaves the lock. The sequence matters: clear the lock first, then fix the permissions.
Fix Sequence for 6144, -816 — Lock First, Then Permissions
Step 1 — Clear the lock (-816)
Kill all QB processes → delete .lock file → rename .ND → restart QuickBooksDB service. The lock must be cleared before permission changes take effect because the file is exclusively held.
Step 2 — Fix the permissions (-6144)
After lock is cleared: right-click company file → Properties → uncheck Read-only → Security → add QBDataServiceUser[XX] and current user with Full Control → check Advanced for Deny entries → remove any Deny rows. Then retry opening QB. If it still fails with 6144, 0 or just 6144: check for EFS encryption and move file to the default QB folder.
What Causes QuickBooks Error 6144, -816?
Backup Software Holding Lock + Permission Issue
Common combined cause — backup software holds an exclusive read lock on the file (-816) while simultaneously the backup service account doesn't release the read permission cleanly, leaving QB unable to get a write lock (-6144). The backup completes but the compound error persists until the backup service releases the file and permissions are corrected.
QB Upgraded Without Updating Service Account
QB was upgraded (QBDataServiceUser23 → QBDataServiceUser24) while another session was still open. The old service account holds the -816 lock, and the new service account doesn't have permissions (-6144). Clear the stale session lock, then add the new QBDataServiceUser[XX] to the folder ACL.
Crash During Permission-Restricted Operation
QB crashed while running a permission-restricted operation (payroll, some admin tasks). The crash left an exclusive lock (-816) and the permission state incomplete (-6144). Restarting the machine clears both simultaneously in most cases.
Windows Update Reset Permissions During Active Session
A Windows Update that ran while QB was open reset folder permissions (removing QBDataServiceUser) while also triggering a session close that left a stale lock. After restart: -816 persists from the stale lock, and -6144 appears because QBDataServiceUser was removed from the ACL.
Network Drop During Single-User Mode
User was in single-user mode (exclusive lock = -816) and the network dropped. The session didn't close cleanly — leaving the lock. When another user tries to access from a machine without write permissions on the share, they get both -816 (lock) and -6144 (insufficient share permissions).
EFS Encryption on a Locked File
File is both EFS-encrypted (producing the -6144 component for any user except the encrypting account) and has a stale lock from a previous session (-816). Both issues must be resolved — remove EFS encryption first, then clear the lock.
How to Fix QuickBooks Error 6144, -816
Related QuickBooks Errors
Error 6144, -816 Persisting After Restart and Permissions Fix?
Let QuickFix Bookkeeping Resolve Both Error Components.
When both error components persist after restart, there's usually a system service (backup agent, AV, or VSS) re-acquiring the lock immediately after reboot — we use Process Monitor to identify the specific service and resolve it.
Book a Free 30-Minute ConsultationNo obligation. Same-day response.