QuickBooks Error 6190: Fix the Transaction Log Mismatch

If QuickBooks refuses to open your company file and the error points at a mismatch or another user, you're looking at this:

Error -6190, -816: QuickBooks is unable to open this company file because it is already open by another user, or the transaction log file does not match the company file.

This one has two distinct causes — an out-of-sync .TLG file, or a genuine multi-user conflict — and the fix depends on which one you're dealing with. Work through these in order; the first fix resolves the large majority of 6190 errors.

Before you start, make a copy of your .QBW company file somewhere safe. It takes 30 seconds and gives you a fallback.

What Causes Error 6190

QuickBooks pairs every company file (.QBW) with a transaction log (.TLG). The .TLG tracks changes in real time so QuickBooks can sync across sessions. When the two files get out of sync — usually from a crash, an abrupt shutdown, or a failed multi-user switch — QuickBooks refuses to open the company file and throws 6190.

The other common trigger: someone else genuinely has the file open, or QuickBooks thinks they do (stale session lock).

The specific causes:

• The .TLG file timestamp or internal state doesn't match the .QBW — typically caused by a crash or hard shutdown
• Another user's QuickBooks session is still live on a different machine
• The wrong machine is set to host the file (multi-user hosting misconfigured)
• The company file is being opened over a network path that's slow or unreliable, causing a partial open that gets treated as "in use"
• An older version of QuickBooks opened the file and created an incompatible log entry

Fix 1: Rename the .TLG File (Resolves Most 6190 Errors)

When the .TLG and .QBW are out of sync, the fastest fix is to rename the .TLG file. QuickBooks will build a fresh one the next time it opens the company file. You won't lose data — the .TLG is a log, not your ledger.

1. Close QuickBooks on all machines
2. Open the folder that contains your company file
3. Find the file with the same name as your company file but with a .tlg extension:

   YourCompany.qbw.tlg
   

4. Right-click it and rename it by adding .OLD to the end:

   YourCompany.qbw.tlg.OLD
   

5. Open QuickBooks and try opening the company file

QuickBooks recreates the .TLG automatically. If the file opens, you're done. If you're still seeing 6190, continue to Fix 2.

Fix 2: Make Sure Nobody Else Has the File Open

Error 6190 uses the phrase "already open by another user" for a reason. Before assuming it's a corrupt .TLG, verify that no one else is actively in the file.

On a single machine:

• Look at the Windows taskbar or Task Manager and confirm QuickBooks isn't running in the background (look for QBW32.exe in the Processes list)

On multi-user:

• Walk to each workstation and confirm QuickBooks is fully closed — not minimized, not in the background
• On the server, open Task Manager and check for QBW32.exe or QBDBMgrN.exe holding the file

If you find a process still running that shouldn't be, end the task, then try opening the company file again. Also try:

1. In QuickBooks, go to File → Utilities → Stop Hosting Multi-User Access on each workstation (not the server)
2. Restart the QuickBooks service on the server

Fix 3: Run QuickBooks File Doctor

If renaming the .TLG didn't work and no one else has the file open, File Doctor is the next stop. It's built to diagnose and repair both company file and network issues that trigger 6190.

1. Download and install the QuickBooks Tool Hub from Intuit's support page
2. Open Tool Hub and click Company File Issues
3. Click Run QuickBooks File Doctor
4. Select your company file from the dropdown (or click Browse to find it)
5. Choose Check your file (or Check your file and network for multi-user setups)
6. Enter your QuickBooks admin password and let it run

File Doctor will repair the company file configuration and regenerate helper files. When it finishes, try opening the file.

Fix 4: Verify Hosting Settings on Every Machine

If you're on multi-user, incorrect hosting is a frequent trigger for 6190. The rule is simple: one machine hosts, everything else doesn't.

Check this on every machine:

1. Open QuickBooks and go to File → Utilities
2. Look at the hosting option:
   • Server (the machine that holds the .QBW file): You should see Stop Hosting Multi-User Access — this means hosting is ON. Leave it.
   • Each workstation: You should see Host Multi-User Access — this means hosting is OFF. If a workstation shows Stop Hosting, click it to turn hosting off.

Restart QuickBooks on each machine after making changes. Then try opening the company file from the workstation that was throwing 6190.

Fix 5: Check the Network Path

If your company file is accessed over a network and the path is unreliable — slow VPN, a mapped drive that sometimes disconnects, a NAS device — QuickBooks can throw 6190 because it sees a partial or interrupted open as "already in use."

Steps to rule this out:

1. Try copying the .QBW file to a local drive on the machine that's having trouble:

   C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\
   

2. Open QuickBooks and open the local copy

If it opens cleanly from the local drive, the network path is the problem. QuickBooks recommends hosting the company file on a Windows machine on the same local network, not on a NAS or over a VPN.

Still Stuck?

A few more things worth checking if none of the above cleared 6190:

• Update QuickBooks: Go to Help → Update QuickBooks Desktop and install any available updates. Some builds have bugs that cause spurious 6190 errors that are already patched.
• Check the .ND file too: Alongside the .TLG, rename the .ND file the same way (add .OLD) to force a rebuild of the network data file. They often need to be reset together.
• Different QuickBooks versions: If different machines in a multi-user setup are running different QuickBooks versions, the .TLG format can mismatch. All machines should run the same year and edition.
• Run Verify Data: Go to File → Utilities → Verify Data to check for internal file damage. If Verify finds issues, follow up with Rebuild Data.

If 6190 persists after all of this, the company file may have structural damage. Intuit's Data Recovery service or a QuickBooks ProAdvisor specializing in file repair is the realistic next step.

One Alternative Worth Knowing About

If you're a solo founder and 6190 keeps pulling you away from actual work — especially if the underlying problem is the fragile .TLG/.QBW pairing on a network drive — it's worth knowing that this architecture is a QuickBooks design choice, not a universal accounting requirement.

Prosper is what I built for that situation: a web app at $29/month with no company file, no .TLG to corrupt, and no session lock errors. It auto-categorizes most transactions and only asks you to review the ones that need a decision. If you're on Stripe or Mercury, it pulls those in and reconciles them. No installs, no server, no multi-user hosting to misconfigure.

That said — if QuickBooks is working for you and you just needed the file open again, the steps above should get you there.

Not professional tax or accounting advice. Consult a CPA for your situation.