QuickBooks Error 6190, 816

Let’s Dive in to see…

How to Fix QuickBooks Error=6190, 816

Schedule a call to fix QuickBooks Errors

QuickBooks Company File Error · 6000 Series

How to Fix QuickBooks Error 6190, 816

QuickBooks displays: "An error occurred when QuickBooks tried to access the company file (-6190, -816)" or "QuickBooks is unable to open this company file. It may have been opened by another user."

Error 6190, 816 is a Transaction Log file mismatch combined with a single-user mode conflict. At QuickFix Bookkeeping, this is distinct from Error 6189-816 (network hosting configuration): 6190 specifically means the .TLG transaction log is out of sync with the .QBW company file — usually after a crash, forced close, or when a user is stuck in single-user mode blocking multi-user access.

The QuickFix Bookkeeping Distinction — 6190 vs 6189 vs 6000-816

All three use the -816 sub-code and block company file access — but the root cause and fastest fix differ significantly.

6190, 816 — this page

.TLG out of sync with .QBW, OR ghost single-user lock. First fix: server user toggles hosting off/on (30 sec). If persists: rename .ND + .TLG, run QBDSM scan.

6189, 816

Network hosting/configuration problem. QBDSM can't reach the file. Fix: restart server first, rename .TLG + fix QBDSM. Network layer, not a TLG mismatch.

6000, 816

Third-party backup software (Acronis, Symantec) has the .QBW locked. Close backup software + configure exclusions. Not a TLG or hosting issue.

The fastest 6190-specific fix — mode toggle (30 seconds): On the server/host computer, open QB → File → Utilities → click Stop Hosting Multi-User Access → confirm → immediately click Host Multi-User Access again. This resets the hosting state and clears any ghost single-user lock. Other workstations can then reconnect. If the error still appears after the toggle, proceed to rename .ND + .TLG.

What Causes QuickBooks Error 6190, 816?

.TLG and .QBW Out of Sync

Primary cause — the Transaction Log file was written at a different point in time than the .QBW. After a crash, forced shutdown, or QB update on one machine without server sync, the two files are mismatched. QB detects the inconsistency and blocks access. Rename both .ND and .TLG and run a QBDSM scan to rebuild synchronized files.

Ghost Single-User Mode Lock

A user closed QB without switching back to multi-user mode, or QB crashed during single-user mode. QB's hosting layer still believes single-user is active, blocking all other users. The mode-toggle on the host clears this state. The error message says "another user has the file open" even though no one is logged in.

File Updated on Workstation Without Server Sync

A user opened the company file directly on a workstation, made changes, and closed — without the server's .TLG reflecting those changes. The next multi-user access attempt finds the server .TLG doesn't match the .QBW state and reports 6190. Always access files via the server path, never by copying locally and editing.

Old QBDSM Left Behind After Version Upgrade

After a QB version upgrade, the old Database Server Manager can remain installed and conflict with the new one. Two QBDSM versions compete for the company file and produce 6190 intermittently. Fix: identify and uninstall the old QBDSM, then rescan with only the new version. Common after upgrading from e.g. QB 2022 to QB 2024.

Version Mismatch Across Machines

Running different QB maintenance release numbers across the server and workstations causes inconsistency in .TLG interpretation. The server and workstations must all run the same QB release. If they differ, the workstation's QB may write TLG entries in a format the server's QBDSM doesn't recognize, producing recurring 6190.

Corrupted .ND or .TLG File

The .ND (Network Data) or .TLG file is damaged — not just out of sync, but invalid in structure. A partial write from a power failure or disk error left the file unreadable. QB can't reconcile the corrupted configuration and reports 6190 consistently. Renaming both removes the damaged files; QBDSM rebuilds clean replacements.

How to Fix QuickBooks Error 6190, 816

Try the 30-second mode toggle first — it resolves the ghost single-user lock immediately. If it doesn't clear, rename .ND and .TLG.

METHOD 1 Toggle Multi-User Mode on the Host Computer 30 seconds — clears ghost single-user lock

On the server/host computer — open QB → File → Utilities. If Stop Hosting Multi-User Access is shown, click it → Yes. Then immediately: File → Utilities → Host Multi-User Access → Yes. This resets the hosting state and clears any ghost single-user lock left by a crashed or uncleaned exit.

On the affected workstation — retry opening the company file. If it opens, the error was a ghost single-user lock and is resolved. If 6190-816 persists → proceed to Method 2.

METHOD 2 Rename .ND and .TLG Files + QBDSM Scan TLG mismatch — resolves most persistent 6190 cases

Close QB on all computers. On the server, navigate to the company file folder. Find YourFile.QBW.ND → right-click → Rename → add .OLD. Find YourFile.QBW.TLG → Rename → add .OLD. Do this from the server itself, not over a network share path.

Open QuickBooks Database Server Manager on the server → Scan Folders → add the company file folder → Start Scan. QBDSM creates fresh, synchronized .ND and .TLG files matched to the current .QBW state. Open QB on the server first, then workstations.

METHOD 3 Update QB on All Machines + Run Quick Fix My Program Version mismatch across server and workstations

On every computer: QB → Help → Update QuickBooks Desktop → Update Now → Reset Update → Get Updates → restart. All machines must run the same QB maintenance release. Check: press F2 in QB → note the Release number — it must match across all machines. After matching releases, run Tool Hub → Program Problems → Quick Fix My Program on each machine.

METHOD 4 Check for Old QBDSM After Version Upgrade Post-upgrade conflict between two QBDSM versions

Control Panel → Programs and Features → look for multiple listings of QuickBooks Database Server Manager. If you see an old version alongside the current one, uninstall the old version → restart → run QBDSM scan with only the current version. Also restart the server first and open QB on the server before any workstations connect.

METHOD 5 Run QuickBooks File Doctor + Verify/Rebuild Underlying file damage after all above tried

Tool Hub → Company File Issues → Run QuickBooks File Doctor → select company file → Check your file and network → Continue → admin password → run. After File Doctor: QB → File → Utilities → Verify Data → if issues found → Rebuild Data → backup when prompted → run to completion. Rebuild addresses internal data inconsistencies that may have caused the TLG mismatch originally.

Quick Reference

Situation	Cause	Start with
Says "another user has single-user mode" but no one is	Ghost single-user lock	Method 1 — toggle hosting
6190 after crash or forced QB close	TLG mismatch from crash	Method 2 — rename .ND + .TLG
6190 after QB version upgrade	Old QBDSM conflict	Method 4 — remove old QBDSM
6190 recurring every few days	Version mismatch across machines	Method 3 — update all machines same release

Frequently Asked Questions

What is the difference between Error 6190 and Error 6189?

Both use the -816 sub-code and both block company file access in multi-user mode, but they originate at different layers. Error 6189 is a network and hosting configuration problem — QBDSM can't find or reach the company file because hosting is misconfigured or the network path has changed. Error 6190 is specifically a .TLG file mismatch or a single-user mode conflict — the network path is fine but the transaction log doesn't match the company file's current state. In practice: 6189 is fixed at the network/hosting layer; 6190 is fixed at the file level (rename .TLG) or by clearing a ghost single-user lock with the mode toggle.

The error says "another user has the file in single-user mode" but no one is logged in — why?

This is a ghost lock — QB's internal state still believes single-user mode is active even though the user closed QB (via a crash or forced close rather than a clean exit). QB's hosting layer writes a flag when single-user mode starts and clears it on a clean exit. If the exit wasn't clean, the flag persists until explicitly reset. The mode-toggle on Method 1 resets this flag by stopping and restarting the hosting service, which clears all state flags. Restarting QB on the host computer also works in most cases.

Should I rename the .TLG from the server or from a workstation?

Always rename from the server — the machine that physically hosts the company file. The .TLG lives in the same folder as the .QBW on the server's local drive. Renaming via a network share path can fail silently or create permission issues. After renaming both .ND and .TLG locally on the server, run the QBDSM scan also from the server to ensure the new files are created with the server's credentials and network configuration. Never rename just the .TLG without also renaming the .ND — both must be refreshed together for QBDSM to rebuild accurate network configuration.

Related QuickBooks Errors

Error 6189-816 Error 6000-816 Error 6000-107 6000 Series Hub All QuickBooks Errors

Error 6190, 816 Persisting After TLG Rename and Mode Toggle?

Let QuickFix Bookkeeping Restore Your Multi-User Access.

Certified Intuit ProAdvisors — Company File Specialists

Recurring 6190-816 after all standard fixes typically points to an old QBDSM version conflict, a Windows domain permissions issue, or deep .QBW file damage requiring specialist tools.

Book a Free 30-Minute Consultation

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