What the -816 sub-code specifically means: The -816 suffix across all 6000-series errors means the file is exclusively locked — QuickBooks found the file but a lock is preventing any other session from opening it. In 6189-816, the lock is from a live single-user mode session. In 6000-82 the lock is from a stale .lock file. Both use -816, but the cause is different. Always check whether someone is genuinely in single-user mode before looking for stale files.

Error code

6189, -816

6xxx Series · Exclusive Lock

Related: -6190 -816 · -6000 -82 · -6177

What it means

Error 6189-816 means QuickBooks reached the company file but found it exclusively locked — another user has the file open in single-user mode, or a previous session that was in single-user mode did not close cleanly. The -816 sub-code is the specific indicator of an exclusive lock in the 6000-series family.

Your data is safe. Error 6189-816 is an access conflict — the file is not damaged. Once the lock is released, the company file opens normally.

Another User in Single-User Mode

Most common cause — a user on another computer has the company file open in single-user mode. Single-user mode locks the file exclusively, blocking every other user. They must either switch to multi-user mode or close QB before others can connect.

Stale Lock File from Abnormal Close

A previous QB session that was in single-user mode ended without a clean close (power failure, crash, force-quit). The lock file (.QBW.lock) remains on disk telling QB the file is still exclusively open. Deleting the stale lock file resolves this immediately.

.QBW and .TLG Out of Sync

The Transaction Log (.TLG) file records are newer than the company file (.QBW) records — a sign of an incomplete write during the last session. QB returns -816 to prevent opening a potentially inconsistent file. Renaming the .TLG forces QB to recreate it cleanly.

Old QBDSM Running After Version Upgrade

After upgrading to a new QB version, the previous year's Database Server Manager service sometimes continues running alongside the new one. Two competing QBDSM versions create file access conflicts that produce recurring 6189-816 even when no users are in single-user mode.

File in Cloud-Synced Folder

OneDrive, Dropbox, or Google Drive sync processes can lock a company file mid-sync, causing QB to see it as exclusively locked by another process. Moving the company file out of any synced folder permanently resolves this variant.

Workstation Hosting Conflict

A workstation has "Host Multi-User Access" incorrectly enabled, causing it to intercept and hold the file lock. The workstation acts as a competing host, blocking all other access to the file.

METHOD 1 Check Whether Anyone Is in Single-User Mode 60 seconds — do this first

The simplest and most common resolution — someone on another computer has the file open in single-user mode. Ask them to switch back to multi-user or close QuickBooks.

METHOD 2 End All QB Processes and Delete the Lock File No one in QB — stale lock from abnormal close

If nobody is in QuickBooks but the error persists, a stale lock file is holding the exclusive lock. End all QB processes across all computers, then delete the lock file.

METHOD 3 Rename the .TLG File If seeing 6190-816 or .QBW/.TLG out of sync

A Transaction Log file that is out of sync with the company file causes QB to refuse the open with -816. Renaming the .TLG forces QB to create a fresh one — it does not delete any transaction data, as the .QBW file contains all the actual data.

METHOD 4 Stop the Old QBDSM Service After a QB Version Upgrade Recurring 6189-816 after upgrading QuickBooks — missed by most guides

After upgrading QuickBooks to a new year version (e.g. from QB 2022 to QB 2023), the previous year's Database Server Manager service often keeps running alongside the new one. Two competing QBDSM versions both trying to manage the same company file create the exclusive lock condition that produces 6189-816 repeatedly.

METHOD 5 Fix Hosting and Run QBDSM Scan Workstation hosting conflict

A workstation with hosting enabled can hold an exclusive lock on the file, producing 6189-816. Check all computers — only the server should host.

METHOD 6 Run QuickBooks File Doctor All methods tried — possible deeper issue

If all lock and hosting fixes have failed, File Doctor addresses deeper network configuration and minor file issues that can produce persistent 6189-816.

How is Error 6189-816 different from Error 6000-82? Both involve -816.

Both errors use the -816 sub-code, which means "exclusive lock" across all 6000-series errors — but they represent different lock types. Error 6000-82 is primarily a stale lock file (.QBW.lock) left over from a session that ended abnormally, with no live session holding the file. Error 6189-816 specifically indicates that the file is locked by a live single-user mode session — either a user is genuinely in single-user mode, or the previous single-user session did not release cleanly. The first diagnostic question for 6189-816 is always "is anyone currently in QB?" For 6000-82 the first check is the lock file. The fixes for both overlap (ending processes, deleting the lock file) but 6189-816 should always start with a live session check before looking for stale files.

Why does this error keep recurring daily even after we fix it?

Recurring daily 6189-816 almost always traces to one of three patterns. A user regularly leaves QB open in single-user mode overnight — their session locks the file every night and other users hit 6189-816 every morning. Train this user to always switch back to multi-user before leaving. The old QBDSM service from a previous QB version is still running and intermittently competing for the file lock (Method 4 resolves this permanently). Or the company file is in a cloud-synced folder — OneDrive or Dropbox sync processes periodically lock the file, producing 6189-816 at unpredictable times. Moving the file to a non-synced local or server path resolves this permanently.

When do I actually need to use single-user mode, and how do I switch back properly?

Single-user mode is required for specific administrative tasks: year-end close procedures, certain payroll setup steps, cleaning up transactions, merging list items, and some data rebuild operations. It should never be left on during normal daily use. To switch back to multi-user correctly: go to File → Switch to Multi-User Mode, click Yes when prompted, and wait for QB to confirm the switch before allowing other users back in. Never force-quit QB while in single-user mode — this leaves the stale lock file that produces 6189-816 for other users the next time they try to connect. If you must exit unexpectedly while in single-user mode, use File → Close Company first, then close QB.