QuickBooks Error 6190 & 816: Resolving Transaction Log & Company File Mismatch

November 9, 2026 6 min read

QuickBooks Error 6190 & 816 occurs when QuickBooks Desktop detects a mismatch between your company file (.QBW) and its transaction log file (.TLG). The error message usually warns that “QuickBooks is unable to open this company file.” This problem arises when a company file is restored or updated on a different computer without its corresponding .TLG file, leaving the transaction log out of sequence with the main database. You can resolve Error 6190 & 816 by renaming both the .ND and .TLG support files, forcing QuickBooks to rebuild a matching transaction log.

Fast-Fix: The 45-Second Solution

To fix QuickBooks Error 6190 & 816, rename the out-of-sync .ND and .TLG files to force a new transaction log generation. Ensure all users close QuickBooks. Open the shared folder containing your company file, find the files ending in .ND and .TLG that match your company name, and rename them to .ND.old and .TLG.old. Reopen QuickBooks and open your company file; the database engine will automatically generate a synchronized transaction log.

Quick Status & Triage Snapshot

  • Error Code Combination: 6190 & 816 (Database engine transaction log state desynchronization).
  • Data Risk Tier: Low to Medium. Historical transactions inside the .QBW file are safe, but recent uncommitted log transactions may need validation.
  • Multi-User Impact: Complete lockout. No user can access the company file until the database engine reconciles the transaction log sequence.
  • Common Triggers: Restoring a .QBW file from a flash drive or backup without restoring the accompanying .TLG file, opening a company file on another machine and returning it, or an abrupt power failure during an active write sequence.
  • Estimated Fix Time: 10 to 15 minutes.

Technical Anatomy: The Transaction Log Handshake and Checkpoint Desync

QuickBooks Desktop uses write-ahead transaction logging managed by the Sybase SQL engine:

  1. How the Transaction Log Functions: Every time an invoice, payment, or journal entry is entered, the engine writes the raw database transaction to the .TLG file first. It then commits that transaction to the main .QBW database table and creates a verification checkpoint token.
  2. The Desync Mechanism: The .QBW and .TLG files maintain internal sequence counters that must match. If you copy Company.qbw to a laptop, make entries, and copy it back into the office server while overwriting only the .QBW file, the original .TLG file on the server will contain outdated checkpoint numbers.
  3. The Engine Block: When QuickBooks launches, the database manager compares the internal transaction count of the .QBW file against the log counter in the .TLG file. If they do not match, the database engine refuses to mount the database to prevent silent table corruption, returning Error 6190 & 816.

Is Your Data at Risk?

Your accounting data is safe. The core database tables reside inside the .QBW file. Renaming the desynchronized .TLG file detaches the unreadable log stream and prompts QuickBooks to generate a clean log starting from your current .QBW transaction state.

However, if this error occurred immediately after an unexpected power outage, do not immediately enter new transactions once the file opens. Run a data verification routine to confirm that the last transaction written before the outage was saved cleanly.

Diagnostic Flowchart: Error 6190 & 816 Decision Path

Start: Error 6190 & 816 appears on screen
 │
 ├──> Did someone copy or restore the .QBW file without its .TLG companion?
 │     ├── YES ──> Rename .TLG to .TLG.old and let QuickBooks generate a new one.
 │     └── NO  ──> Proceed to full network check.
 │
 ├──> Close QuickBooks on all workstations
 │     └── Rename both .ND and .TLG files in the company directory.
 │
 ├──> Rescan folder with QuickBooks Database Server Manager on server
 │     ├── Opens cleanly? ──> Run File > Back Up Company to truncate log state.
 │     └── Error persists? ──> Proceed to QuickBooks File Doctor.
 │
 └──> Run File Doctor via QuickBooks Tool Hub to repair damaged database headers.

Step-by-Step Repair Guide

Follow these steps in sequence on the computer or server where the company file is physically stored.

Step 1: Ensure All Users Exit QuickBooks on the Network

Before you can rename locked support files, all network handles to the database must be closed.

  1. Instruct every user in your organization to log out and close QuickBooks Desktop.
  2. On the server hosting the company file, open Task Manager (Ctrl + Shift + Esc).
  3. Click the Details tab, locate any instances of qbw32.exe, and click End task.

Step 2: Rename the Out-of-Sync .ND and .TLG Files

Renaming the companion files removes the desynchronized transaction log and forces QuickBooks to build fresh communication files.

  1. Open File Explorer and browse to your company file directory (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
  2. Make sure file extensions are visible: in File Explorer, click View, select Show, and check File name extensions.
  3. Locate the files sharing your company file’s name:
    • YourCompanyName.qbw.nd
    • YourCompanyName.qbw.tlg
  4. Right-click YourCompanyName.qbw.nd, select Rename, and change it to:
    YourCompanyName.qbw.nd.old
  5. Right-click YourCompanyName.qbw.tlg, select Rename, and change it to:
    YourCompanyName.qbw.tlg.old
  6. Do not modify or rename the main .QBW file.

For a comprehensive manual guide on these files, review Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors.

Step 3: Rescan the Directory with Database Server Manager

If your company file is shared over a network, you must instruct the Database Server Manager to regenerate an updated .ND file.

  1. On the host server, click the Start menu, type QuickBooks Database Server Manager, and launch it.
  2. Select the Scan Folders tab.
  3. Click Add Folder, select your company file folder, and click Scan.
  4. When the scan finishes with an “OK” status, close the utility.

Step 4: Open the Company File and Truncate the Transaction Log

  1. Launch QuickBooks Desktop on the host computer or a workstation.
  2. Select Open or restore an existing file, choose your company file, and log in with your administrative account.
  3. QuickBooks will automatically create a brand-new .TLG file matching the current state of your .QBW file.
  4. To permanently verify and stabilize the database:
    • Go to File > Back Up Company > Create Local Backup.
    • Click Options, ensure Complete verification is selected, and save the backup file.
    • Running a verified backup resets the newly generated transaction log and truncates temporary tables.

To learn how to manage transaction log file growth over time, see .TLG File Fix: How to Truncate Transaction Logs to Boost Performance.

Hard Stop: Severe Transaction Table Desynchronization

If renaming the support files fails to resolve Error 6190 & 816 and QuickBooks reports that it cannot open the file, the company file was likely copied while a transaction was actively writing to disk.

Download and run the integrated repair engine via The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor. If File Doctor reports structural damage it cannot repair, restore your most recent complete verified backup (.QBB) to prevent permanent accounting table corruption.

QuickBooks Error 6129, 0: Fixing Database Connection Verification Failures

November 7, 2026

QuickBooks Error 6130: Resolving Database Server Connection Problems

November 7, 2026

QuickBooks Error 6123, 0: Troubleshooting Lost Connections to Company Files

November 7, 2026