QuickBooks Error -6190, 0: Company File and Transaction Log Mismatch

QuickBooks Desktop shows error -6190, 0 when the company file and its transaction log disagree; this guide explains the cause and how to clear it.

Error -6190, 0 stops QuickBooks Desktop from opening a company file. In most cases our engineers see, the data itself is healthy and the transaction log beside the file is the real problem. This page covers what the code means, what sets it off, and the steps that get the file open again.

The message on screen

The dialog most often reported to us reads: "We're sorry. QuickBooks encountered a problem. Error codes: (-6190, 0)." The exact wording varies by build and year, and some installs mention a network problem instead. The code in parentheses is the constant. Treat the network wording with caution; QuickBooks blames the connection first, but the cause is usually local.

The meaning of error -6190, 0

Every company file keeps a companion transaction log, a file with the TLG extension that lives in the same folder. The log records each entry made since the last completed backup. Before opening the file, QuickBooks checks that the two belong together. The 6190 code means that check failed. The log on disk does not match the company file beside it. The trailing zero is a sub-code and adds no detail. A mismatch alone can block the open, which is why the data inside often survives untouched.

Common triggers

We meet these causes in roughly this order:

  • The file is already open in single-user mode on another computer when a second user tries to open it across the network.
  • A crash, power cut, or forced shutdown leaves the log half written.
  • A backup is restored into a folder that still holds an older transaction log.
  • Cloud sync software copies or locks the company file while it is open.
  • Backup or antivirus tools grab the log mid write and hold it.

Fixing error -6190, 0

Work through the scenarios below in order and stop as soon as the file opens. Take a fresh backup before you begin.

The file is open on another machine

  1. Close the company file on every computer, then close QuickBooks on each one.
  2. Restart the machine that hosts the file.
  3. Open the file on that machine, then choose Switch to Multi-user Mode from the File menu.
  4. Open the file again from each workstation.
  5. If the error returns, review hosting on every machine. Multi-user hosting belongs on the computer holding the file and nowhere else.

The transaction log is out of sync

  1. Create a local backup first, from the Back Up Company option on the File menu. The log carries entries made since the last backup, so renaming it without one can lose those entries.
  2. Close QuickBooks everywhere.
  3. In the folder that holds the company file, find the matching file with the TLG extension.
  4. Rename it by adding .OLD to the end. Keep the renamed file; do not delete it.
  5. Reopen the company file. QuickBooks builds a clean log as it opens.

The error followed a restore

  1. Restore the backup again, into a new and empty folder this time.
  2. Open the company file from that folder, so no older log can interfere.
  3. If it opens cleanly, tidy the original location afterwards.

Sync or backup software is involved

  1. Exclude the company folder from any cloud sync tool, or move the file to a shared folder that nothing syncs.
  2. Add the folder to the exclusion list in your backup and antivirus software, or schedule both to run after hours.
  3. If the error persists, apply the log rename steps above.

After the file opens

Run a verification pass before trusting the file with new work. Choose Verify Data under the Utilities option on the File menu. If it reports damage, follow it with Rebuild Data from the same place, then verify once more.

Keeping the error away

  • Run hosting on one machine only, and leave it that way.
  • Close the file at day's end instead of leaving sessions open overnight.
  • Keep the company folder out of synced locations entirely.
  • Schedule scans and backups for hours when nobody has the file open.
  • Back up on a regular schedule. Each completed backup starts a fresh, small log, which keeps any future recovery simple.
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.