QuickBooks Error -6190, 82 -- Fixing the Company File and TLG Mismatch

QuickBooks error -6190, 82 blocks opening your company file when the transaction log no longer matches it. Here is what causes it and how to recover.

QuickBooks error -6190, 82 appears when you try to open a company file and QuickBooks refuses because the transaction log (.tlg) file does not agree with the company file itself. The file will not open until the mismatch is resolved. Our engineers treat this as one of the more recoverable 6000 series errors, because in most cases the underlying data is intact and only the pairing between the two files is broken.

What the error message says

The message typically reads:

"QuickBooks is unable to open this company file. An error occurred when QuickBooks tried to access the company file. Please try again. If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6190, 82)."

Some installations show a shorter version: "Error -6190, 82: QuickBooks cannot open the company file." Either way, the file fails to open in single-user mode, multi-user mode, and often even on the server host itself.

What the code means

Every company file has a companion transaction log with the same name and a .tlg extension. QuickBooks writes pending changes to the log first, then folds them into the company file. The log exists so that if QuickBooks crashes mid-write, the data can be reconstructed on the next open.

Error -6190, 82 means QuickBooks compared the two files and found they describe different states. The log contains transactions the company file does not, or the two disagree about where the last clean save ended. Rather than risk merging inconsistent data, QuickBooks stops and refuses to open the file.

What triggers it

The mismatch almost always comes from one of these situations:

1. A failed or interrupted sync, backup, or file copy left the .tlg and the .qbw out of step.
2. The company file was copied or restored without its matching .tlg file, or with a .tlg from a different point in time.
3. QuickBooks closed abruptly, through a crash, power loss, or a forced shutdown, while the log held uncommitted changes.
4. Two users opened the same file from different copies in different folders, so each folder built its own divergent log.
5. Hosting configuration problems caused a workstation and the server to open different physical copies of the file.

How to fix it

Work through these scenarios in order, most common first. Make a manual copy of the entire company folder before you start.

Scenario 1: A stale or mismatched .tlg file

1. Close QuickBooks on every computer, including the server.
2. Open the folder holding the company file and confirm you can see file extensions.
3. Find the file with the same name as your company file but ending in .tlg.
4. Rename it, for example by adding .old to the end. Do not delete it yet; it is your rollback path.
5. Reopen the company file. QuickBooks will build a fresh log on first save.

This resolves the majority of -6190, 82 cases. If the file opens and your balances look right, you are done.

Scenario 2: A recent good backup exists

1. Restore your most recent .qbb backup to a new folder, not over the live file.
2. Open the restored file and verify key reports, such as the balance sheet and a recent profit and loss, against your records.
3. Re-enter any transactions dated after the backup.

Scenario 3: The file still will not open

If renaming the log and restoring a backup both fail, the company file itself is likely damaged. At this point the file needs a rebuild at the data level.

1. Try File, then Utilities, then Rebuild Data if you can get the file open at all.
2. If the file will not open, our engineers can repair it directly. Send the company file or a backup, the admin password, the approximate size, the years of data it holds, and the date of the last transaction you know is good. We will assess the corruption pattern and confirm what can be recovered before any work begins.

How to prevent it recurring

Never copy a company file without its .tlg companion; move the pair together or, better, create a backup (.qbb) and move that. Avoid abrupt shutdowns, and close QuickBooks properly at the end of every session. Keep one authoritative copy of the file on the server and map every workstation to that same path, so divergent logs cannot form. Finally, run scheduled backups so a good restore point is always available if a sync or copy fails again.