QuickBooks Error 6190
Let’s Dive in to see…
How to fix QuickBooks Error=6190
QuickBooks Company File Error · 6190 Series · Multi-User Conflict
How to Fix QuickBooks Error 6190
QuickBooks displays an error referencing -6190 — typically alongside a secondary code such as -816 — when opening a company file in a multi-user environment.
The 6190 family of errors indicates a conflict between the company file (.QBW) and its transaction log (.TLG) in a multi-user environment. At QuickFix Bookkeeping, 6190 errors are caused by the .TLG and .QBW falling out of sync — usually after a session ended abnormally. The fix is renaming the .TLG (safe, no data loss) and letting QB rebuild it fresh. The secondary code tells you the specific trigger: -816 means there's also an exclusive lock.
6190 Sub-Codes — What Each Means
6190, -816
.TLG mismatch PLUS exclusive lock. Most common variant. Rename .TLG first, then check for stale .lock file. See dedicated 6190-816 page for the full fix.
6190, -301
.TLG mismatch AND company file has damage. Rename .TLG then run Verify/Rebuild. File Doctor may be needed.
6190 (no sub-code)
Pure .TLG-to-.QBW mismatch without a lock. Rename .TLG → QB creates a fresh one → open normally.
What Causes QuickBooks Error 6190?
.TLG and .QBW Out of Sync
Root cause of all 6190 errors — the transaction log file (.TLG) was written by a different QB session state than the current .QBW. This happens when QB crashes, when a user's connection drops mid-session, or when the file is restored from backup without updating the .TLG. QB detects the mismatch on open and reports 6190. Fix: rename .TLG → QB creates a fresh one.
Network Drop During Active Multi-User Session
A network outage during an active QB session caused one user's connection to drop without a clean session close. The .TLG recorded the incomplete session state and now conflicts with the .QBW's state after clean closes from other users. Renaming the .TLG resolves this.
Backup Restored Without Matching .TLG
A .QBB backup was restored into a folder where a .TLG from a more recent session exists. The restored .QBW's state is older than the existing .TLG — they don't match. Renaming the existing .TLG before opening the restored file prevents 6190.
QB Crashed During Write Operation
QB crashed while writing a transaction — the .TLG received partial data about the transaction that the .QBW didn't fully commit. QB detects the .TLG contains entries the .QBW doesn't acknowledge and reports 6190. Renaming the .TLG loses only the uncommitted partial transaction — committed data is safe.
Power Loss During Active Session
Power failure while QB was writing: the .TLG captured a write that the .QBW didn't receive. On restart, 6190 appears. Renaming the .TLG allows QB to open and show the state before the power loss — the in-progress transaction at the time of power loss is lost but all committed transactions are intact.
File Copied to New Location Without .TLG
The .QBW was copied to a new location but the .TLG from the original location wasn't copied too. QB finds an old .TLG at the destination (from a previous file stored there) and reports a mismatch. Delete or rename the old .TLG from the destination before opening.
How to Fix QuickBooks Error 6190
Related QuickBooks Errors
Error 6190 Persisting After .TLG Rename and Rebuild?
Let QuickFix Bookkeeping Recover Your Company File.
Persistent 6190 after renaming the .TLG and running Rebuild means the company file has structural damage beyond what Rebuild can fix — we assess the extent of damage and determine whether restore or specialist repair is the appropriate path.
Book a Free 30-Minute ConsultationNo obligation. Same-day response.