QuickBooks Error 6189 816

Let’s Dive in to see…

How to fix QuickBooks Error= 6189 816

Get ProAdvisor Help Now!
QuickBooks Online

QuickBooks Company File Error · 6000 Series

How to Fix QuickBooks Error 6189, 816

QuickBooks displays: "An error occurred when QuickBooks tried to access the company file (-6189, -816)"

Per Intuit's own documentation: there's an issue with your multi-user network, not with your data file. At QuickFix Bookkeeping, the -816 suffix means the company file is exclusively locked. In 6189, that lock comes from either a live single-user mode session or a desynchronised .TLG transaction log. Your accounting data is safe — access is blocked, not damaged.

The QuickFix Bookkeeping Distinction — 6189 vs 6190 vs 6175 vs 6176

All four errors block company file access in multi-user mode — but they fail at different layers. The -816 sub-code means "file exclusively locked." The error number tells you who is holding the lock.

Error 6189, -816 — this page

File is locked by a live single-user mode session OR the .TLG transaction log is out of sync with the .QBW after an abnormal shutdown. File data is intact.

First check: Is anyone in single-user mode? If yes — have them switch. If no one is in QB — rename the .TLG.

Error 6190, -816

The .QBW and .TLG are out of sync from a session that ended abnormally. No one is actively in single-user mode — this is a stale desync. Fix: rename .TLG only.

6189 and 6190 are often confused. 6189 has the live-lock cause that 6190 does not.

Error 6175

Server found — but QBDBMgrN.exe is not running or crashes immediately. Fix the database service, not the .TLG. See our Error 6175 page.

Error 6176

QB cannot find the server's address — DNS or network identity failure. Fix the QBDSM scan and .ND file. See our Error 6176 page.

What the -816 suffix means: Across all 6000-series errors, -816 means the file is exclusively locked — QB found the file but another process holds a lock preventing access. In 6189, that lock is either a live single-user session or a .TLG desync that prevents QB from opening the file safely. Always check whether someone is genuinely in single-user mode before looking for stale files.

The server-first restart rule: Always restart the server before workstations. If workstations restart first, they reconnect to the server before it has cleared the old session state — perpetuating the error. Correct order: (1) close all QB on workstations, (2) restart the server, (3) wait for QuickBooksDB service to show Running in services.msc, (4) then restart workstations one at a time.

What Causes QuickBooks Error 6189, 816?

Active Single-User Mode Session

Most common cause — 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 QB entirely.

.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. QB detects the mismatch and refuses to open the file to prevent data damage. Renaming the .TLG forces QB to create a clean one — no data is lost through this process.

Stale .QBW.lock File

When QB 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, QB sees the orphaned lock, interprets it as an active session, and produces 6189, 816. Deleting the stale .lock file resolves this.

Old QBDSM Version After QB Upgrade

After upgrading QB (e.g., from QB 2022 to QB 2023), the old QuickBooksDB32 service may keep running alongside QuickBooksDB33. Two QBDSM versions competing for the same file produce 6189, 816 — the file appears locked because both services are attempting to manage it. Disable the old version's service in Windows Services.

Company File on Cloud Sync or External Drive

Files in OneDrive, Dropbox, Google Drive, or on USB/NAS drives produce 6189, 816 reliably. Cloud sync tools continuously scan and temporarily lock files — this directly conflicts with QB's locking mechanism. The file must be on a local Windows hard drive. This is a permanent fix, not a workaround.

Hosting Misconfiguration or Permission Issue

Workstations with "Host Multi-User Access" enabled, or the QBDataServiceUser account lacking Full Control over the company file folder, cause access conflicts that produce 6189. Only the server should host. The QBDataServiceUser account needs Full Control permissions on the folder containing the .QBW.

How to Fix QuickBooks Error 6189, 816

Start with Method 1 — check whether anyone is in single-user mode. This is the most common cause and the fastest fix.

METHOD 1 Check Whether Anyone Is in Single-User Mode Do this first — fastest resolution
1

Contact every potential QB user and ask them to open QB → File menu. If it shows "Switch to Multi-User Mode" — they are currently in single-user mode and holding the lock. Have them click it to switch to multi-user. If it shows "Switch to Single-User Mode" — they are already in multi-user mode and are not the cause.

2

If everyone is in multi-user mode or no one is currently in QB — the lock is either stale (Method 2) or caused by a .TLG desync (Method 3). Apply the server-first restart rule now: close all QB on workstations → restart server → wait for QuickBooksDB to show Running in services.msc → restart workstations one at a time. This alone clears many stale lock situations.

METHOD 2 End All QB Processes and Delete the Stale Lock File No one is in QB — orphaned lock file
1

On the server, press Ctrl + Shift + Esc to open Task Manager. Under the Details tab, end each of these processes if running: QBW32.exe, QBDBMgrN.exe, QBDBMgr.exe, QBUpdate.exe, QBCFMonitorService.exe. Select each → End Task.

2

Navigate to the company file folder. Look for a file named YourCompanyFile.QBW.lock (same name as the .QBW with .lock appended). Delete this file — unlike .ND and .TLG, the .lock file is always safe to delete. QB recreates it when it next opens the file. After deleting, try opening the company file from a workstation.

METHOD 3 Rename the .TLG File TLG desync — the -816 specific fix

Renaming (not deleting) the .TLG forces QB to create a fresh transaction log. No financial data is held in the .TLG — all data is in the .QBW. This is safe.

1

On the server, open Windows File Explorer. Navigate to the folder containing the company file (.QBW). Find YourCompanyFile.QBW.TLG → right-click → Rename → add .OLD to the end: YourCompanyFile.QBW.TLG.OLD.

2

Also rename the .ND file (same name, .ND extension) to .ND.OLD. Then open QuickBooks Database Server Manager (Start → type Database → open QBDSM) → Scan Folders → add the company file folder → Start Scan. This rebuilds the .ND file.

3

Open QuickBooks on the server and open the company file — QB recreates the .TLG automatically. Test multi-user access from workstations. If 6189, 816 now clears — the desync was the cause.

METHOD 4 Disable Old QBDSM Version After a QB Upgrade Error appeared after a QB version upgrade
1

Press Windows + R → type services.msc → Enter. Look for multiple QuickBooksDB entries — e.g. QuickBooksDB32 (QB 2022) and QuickBooksDB33 (QB 2023) both showing as Running. Right-click the older service (lower number) → Stop. Then right-click → Properties → Startup type: Disabled. Only the service matching your current QB version should be running. Restart the current service and retry multi-user access.

METHOD 5 Move File Off Cloud Storage or External Drive File on OneDrive, Dropbox, USB, or NAS
1

If the company file is stored in OneDrive, Dropbox, Google Drive, iCloud Drive, or on a USB, external, or NAS drive — move it to a local Windows hard drive. Create a folder such as C:\QuickBooksFiles\ on the server. Copy the .QBW file there. Run a QBDSM scan on the new folder. Open QB from the new location. Cloud sync tools continuously interfere with QB's file locking mechanism — error 6189, 816 will recur every sync cycle until the file is moved. This is a permanent fix, not a temporary workaround.

METHOD 6 Fix Hosting, Permissions + Run File Doctor All above tried — hosting or permission issue
1

Fix hosting: On each workstation — QB → File → Utilities. If "Stop Hosting Multi-User Access" shows → click it. On server — confirm hosting is ON. Fix permissions: Right-click company file folder → Properties → Security → Edit. Add QBDataServiceUser[XX] and your Windows account with Full Control. Check the .QBW file is not Read-Only. Run File Doctor: Tool Hub → Company File Issues → Run QuickBooks File Doctor → select company file → Check your file and network → admin password → run (10–15 min). File Doctor diagnoses both network and file-level issues in a single pass.

Quick Reference

Your situation Likely cause Start with
Someone's QB shows "Switch to Multi-User Mode" Live single-user lock Method 1 — have them switch to multi-user
No one is in QB — error after a crash or power failure Stale .lock file or .TLG desync Methods 2 + 3 — delete .lock, rename .TLG
File on OneDrive, Dropbox, or USB drive Cloud sync interference Method 5 — move to local drive
Error appeared after QB version upgrade Old QBDSM version competing Method 4 — disable old service
Opens on server, fails on all workstations Hosting or permissions Method 6 — hosting + File Doctor

Frequently Asked Questions

Is my company file data at risk when Error 6189, 816 appears?
No — as Intuit's own documentation states, Error 6189, 816 is a network access problem, not a data file problem. The .QBW file and all its financial records remain intact. The error blocks access to the file but does not modify or corrupt it. The .TLG file stores a transaction replay log (not the accounting data itself), so renaming it and allowing QB to create a fresh one does not lose any transactions. All financial data lives in the .QBW.
What is the .TLG file and is it safe to rename it?
The .TLG (Transaction Log) file records every change made to the company file as a sequential log — QB uses it for disaster recovery if it crashes mid-transaction. When an abnormal shutdown leaves the .TLG recording a transaction that the .QBW never fully received, they become desynced. QB detects this and refuses to open the file safely. Renaming the .TLG to .OLD removes the mismatched file. QB creates a fresh .TLG from the current .QBW state on next successful open. No financial data is stored in the .TLG — renaming it is safe. Naming rather than deleting preserves it for inspection if needed.
Can I store my QuickBooks company file in OneDrive or Dropbox?
No — Intuit explicitly does not support company files stored in cloud-sync folders (OneDrive, Dropbox, Google Drive, Box, iCloud Drive) for QB Desktop multi-user access. Cloud sync tools run as background processes that continuously scan, hash, and sometimes temporarily lock files they are syncing — this directly conflicts with QB's file locking mechanism and produces 6189, 816 reliably. For backing up your QB company file to the cloud, use QB's built-in backup to create a .QBB file, which can then be safely stored in cloud backup. The live .QBW must remain on a local Windows hard drive.

Related QuickBooks Multi-User Errors

Still Getting 6189, 816 After Rename and Restart?

Let QuickFix Bookkeeping Restore Your Multi-User Access.

Certified Intuit ProAdvisors — Multi-User Network Specialists

Persistent 6189, 816 after .TLG rename, lock file deletion, and QBDSM scan typically points to a network topology problem, a domain permissions policy, or a deeply damaged QB installation requiring specialist diagnosis. Our ProAdvisors resolve multi-user access errors in a single session.

Book a Free 30-Minute Consultation

No obligation. Same-day response. Multi-user access restored fast.