QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies

QuickBooks Error 6190, -816 occurs when the primary QuickBooks company file (.qbw) and its associated Transaction Log file (.tlg) become mismatched or fall out of sync. This error stops QuickBooks from opening the file because the database engine cannot align the record history in the transaction log with the state of the company file. To resolve Error 6190, -816, rename the .ND and .TLG files to allow QuickBooks to generate a clean transaction log, and verify that no workstations are holding the file open in Single-User Mode.

Fast-Fix: The 45-Second Solution

To resolve Error 6190, -816, open the directory containing your company file, rename both the .ND and .TLG files to .OLD, and open the company file in QuickBooks. Error 6190, -816 is caused when the transaction log pointer desynchronizes from the company database. Renaming these support files forces QuickBooks to create a clean, matched transaction log without affecting your core accounting records.

Quick Status & Triage Snapshot

• Data Risk Tier: Low to Medium. Core financial tables are safe, but incomplete or unsynced log chains must be cleanly severed.
• Multi-User Impact: High. No workstation can open the company file until the transaction log discrepancy is resolved.
• Common Trigger: Restoring a company file (.qbw) from a backup without overwriting the old .tlg file, or a network drop during multi-user write operations.
• Estimated Fix Time: 10 to 15 minutes.

Diagnostic Flowchart: Error 6190, -816 Decision Path

[Start: Error 6190, -816 appears when opening company file]
   │
   ▼
Was a backup (.QBB) recently restored into this folder?
   ├─► Yes ──► Old .TLG file was likely left behind. Rename .TLG to .TLG.old immediately.
   └─► No ───► Proceed to user access check.
          │
          ▼
Is another workstation logged in under Single-User Mode?
   ├─► Yes ──► Switch that workstation to Multi-User Mode or log out completely.
   └─► No ───► Rename both .ND and .TLG files on the host computer.
                 │
                 ▼
              Does the error persist after renaming .ND and .TLG?
                 ├─► No ──► [Resolved: Fresh transaction log generated]
                 └─► Yes ─► Run QuickBooks File Doctor from the Tool Hub.

Is Your Data at Risk?

The data inside your company file is generally safe. The .tlg file exists to record transactions entered since your last full backup, serving as a recovery buffer.

However, do not attempt to delete the main company file (.qbw) or manually edit the contents of the transaction log. If you recently restored a backup and did not rename the older .tlg file sitting in that folder, QuickBooks tries to reconcile an old log against a newer database state (or vice versa), which triggers the error.

Technical Anatomy: What This Error Means

QuickBooks uses a two-part database architecture:

1. The Company File (.qbw): Contains the core database tables, lists, and historical transactions.
2. The Transaction Log File (.tlg): Tracks incremental changes made to the database since the last time a full verification backup was created.

Both files share an internal pointer counter. Every time a transaction is saved, both the .qbw and .tlg advance their transaction counters in lockstep.

Error 6190, -816 occurs when QuickBooks reads the header of the .qbw file and finds a transaction pointer that does not match the pointer in the companion .tlg file. This happens frequently when an administrator restores a .qbw file into a directory where an existing .tlg from a different date already exists. Because the database engine cannot ensure data consistency across mismatched files, it stops the file from opening.

Differential Diagnosis: Don’t Confuse This With…

• QuickBooks Error 6189, 816: Caused by an active process or service holding an exclusive single-user lock on the file. While 6190 and 6189 often appear together in the same error message dialog, 6190 specifically diagnoses the pointer desynchronization.
• QuickBooks Error 6000, -80: Indicates data damage inside the actual data blocks of the .qbw file itself, rather than an external log file mismatch.
• QuickBooks Error 6155: Indicates that the file header of the .qbw file is damaged or unreadable, preventing initial database mounting.

Step-by-Step Repair Guide

Follow these steps on the host system where the company file resides.

Step 1: Rename the .ND and .TLG Files

Renaming the transaction log and network data files breaks the desynchronized link and forces QuickBooks to initialize a fresh, matched set.

1. Ensure QuickBooks is closed on all workstations and on the host server.
2. Open File Explorer and navigate to the directory where your company file is stored (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
3. Locate the files with the same name as your company file but with .ND and .TLG extensions:
   • [YourCompanyName].qbw.ND
   • [YourCompanyName].qbw.TLG
4. Right-click [YourCompanyName].qbw.ND and rename it to:
   [YourCompanyName].qbw.ND.old
5. Right-click [YourCompanyName].qbw.TLG and rename it to:
   [YourCompanyName].qbw.TLG.old
6. Open QuickBooks Desktop on the host computer and open the company file.
7. QuickBooks will automatically generate a new .tlg and .nd file synchronized to the current state of your .qbw file.

Step 2: Check for Single-User Mode Locks Across the Network

If another computer has opened the file in single-user mode, QuickBooks cannot synchronize the transaction stream for other users.

1. Open QuickBooks on each workstation on your network.
2. If QuickBooks opens the file on any workstation, check the top window banner.
3. If it says [Single-User Mode], go to File > Switch to Multi-User Mode.
4. If a workstation is frozen or unresponsive, open Windows Task Manager (Ctrl + Shift + Esc) on that machine and end the QBW32.exe process.

Step 3: Run QuickBooks File Doctor via the Tool Hub

If renaming the files does not resolve the issue, a structural mismatch may exist within the internal database tables.

1. Download and install the latest QuickBooks Tool Hub on the host server.
2. Launch the Tool Hub and select the Company File Issues tab.
3. Click Run QuickBooks File Doctor.
4. Browse to select your company file from the directory.
5. Select Check your file and network, provide your QuickBooks Admin password, and proceed.
6. The utility will re-index the database records and repair remaining discrepancies between the data engine and support files.

Step 4: Perform a Full Clean Backup and Verification

Once the file opens, run a verification to align your data:

1. Open your company file in QuickBooks.
2. Go to File > Back Up Company > Create Local Backup.
3. Complete a full local backup. Creating a verified backup resets the newly generated .tlg file counter and commits all cached transaction pointers cleanly.
4. Go to File > Utilities > Verify Data to ensure no secondary integrity errors remain.

Hard Stop: When to Call an Expert

Stop troubleshooting and contact professional data recovery services if:

• Renaming the .TLG file allows the file to open, but significant blocks of recent transactions (such as the last week or month) are missing from the register.
• The Verify Data utility repeatedly fails with internal database errors (such as LVL_ERROR or table index corruption in qbwin.log).
• The company file and transaction log were modified by an unauthorized third-party encryption tool or ransomware.

Related Errors

If you encounter related file-matching or recovery issues, explore these articles:

• QuickBooks Error 6189, 816: Fix “Company File is Already in Use”
• Manual Fix: Renaming .ND and .TLG Files to Resolve 6000 Errors
• The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor
• QuickBooks Error 6190 & 816: Resolving Transaction Log & Company File Mismatch
• .TLG Recovery: How to Recover Data from a Damaged Transaction Log File

Closing the Books

Error 6190, -816 is a protective signal that keeps your database ledger from writing to an unaligned transaction log. In the vast majority of cases, the core financial transactions in your .qbw file are completely intact. Renaming the desynchronized .tlg file and creating a fresh verified backup will clear the discrepancy and get your multi-user network back up and running.