QuickBooks Error -6190, -82: Clearing a Transaction Log Mismatch

Error -6190, -82 blocks QuickBooks Desktop from opening a company file when the transaction log disagrees with it. Here is how to clear it safely.

Error -6190, -82 stops QuickBooks Desktop at the door. You select the company file, the open fails, and the message points at a disagreement between your data and its transaction log. QuickBooks refuses to merge records that do not match, which is the right instinct. Our engineers clear this error in a fixed order, because the cause is usually a session or hosting conflict rather than real damage.

What does the -6190, -82 pairing actually mean?

Every company file works with a shadow. The transaction log, a .tlg file with the same name, records each entry before QuickBooks commits it to the main .qbw. When the two fall out of step, the program reports the mismatch and stops.

Three situations create the disagreement. Another computer still has the file open, so the database service cannot get exclusive access. Someone restored an older backup into a folder that still holds the newer log. Or a crash interrupted a write and left the log ahead of the file. Only the third case involves possible damage, which is why the cheap checks come first.

Get the file to yourself first

Two preconditions apply. Confirm you have a restorable backup, a .qbb or a known-good copy of the .qbw, from before today. Then put the file into a single-user state by closing QuickBooks on every machine that can reach it and rebooting the host.

A stuck session on a workstation produces this exact error, and a reboot often clears it without touching data. Try the file once after the reboot. If it opens, you are done; if not, keep going.

Rule out a hosting conflict

Hosting decides which machine runs the database service for the file. When a workstation has hosting switched on at the same time as the server, the two fight over the log and the open fails.

  1. Open a different company file, or the sample file, so the menus are live.
  2. Go to File > Utilities and read the options you see.
  3. If "Stop Hosting Multi-User Access" appears, choose it and confirm. Hosting is now off on this machine.
  4. If "Host Multi-User Access" appears instead, hosting is already off here. Leave it that way.
  5. Repeat on every workstation. Only the machine that stores the folder keeps hosting on.
  6. Close QuickBooks everywhere and try the company file again.

Rescan the folder with Database Server Manager

The server-side scan re-registers the file with the database service and rebuilds its view of the log. Run it on the machine that hosts the folder, not over the network from a workstation.

  1. Open QuickBooks Database Server Manager from the Windows Start menu.
  2. On the Scan Folders tab, choose Add Folder and browse to the folder holding the company file.
  3. Select the folder, continue, and choose Scan.
  4. Wait for the scan to finish. A large folder can take several minutes.
  5. Check the results list. The company file should appear with the correct QuickBooks version beside it.
  6. Open QuickBooks and try the file.

Two signs tell you the scan worked: the file shows a version rather than an error in the results, and the open now succeeds.

How do you handle a mismatched log safely?

If both checks fail, the log itself is the suspect. Deal with it in a way that keeps every byte recoverable:

  1. Copy the .qbw and the .tlg together to a separate folder. That pair is your fallback.
  2. Back in the working folder, rename the .tlg, for example to .tlg.old. Rename it, never delete it.
  3. Open the company file. QuickBooks builds a fresh log after a successful open.
  4. Run File > Utilities > Verify Data on the file that just opened.

The rename has a cost. Anything recorded in the log but never committed to the company file stays behind in the renamed copy. That window is normally small, because QuickBooks writes the main file as you exit. Keep the renamed log regardless: recovering transactions from a QuickBooks .tlg log is often possible when the trapped entries turn out to matter.

The deeper problem a log rename cannot fix

If the error survives the rename, or returns wearing a different -6000 code or a C= error, the company file itself is damaged. The log was the messenger, not the cause. At that point a restore from your most recent .qbb is the safe route, accepting whatever was entered since that backup. When a restore is not an option, see our QuickBooks error code repair service for rebuilding the file directly.

One habit prevents a repeat: never let an automated backup copy the .qbw while the file is open. A copy taken mid-session carries exactly this mismatch, and it resurfaces at the next restore. Take backups after everyone closes the file.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.