QuickBooks Error -6189, -816 -- Company File and Transaction Log Mismatch

QuickBooks error -6189, -816 blocks access when the company file and its transaction log are out of sync; our engineers resolve the mismatch and restore access.

When QuickBooks Desktop cannot reconcile a company file (.qbw) with its companion transaction log file (.tlg), it blocks access to prevent data corruption. Error -6189, -816 is one of several codes in the 6000 series that signals this mismatch. Our engineers have resolved this error across single-user and multi-user environments, and in nearly every case the company data is fully recoverable once the underlying mismatch is corrected.

What the Error Message Says

The full message displayed by QuickBooks Desktop reads:

"QuickBooks was unable to open the company file. Error code: -6189, -816."

In some environments the error is paired with a secondary code (-6190), and the message may include the path to the company file that QuickBooks attempted to open.

What the Code Means

Error -6189, -816 indicates that QuickBooks detected a discrepancy between the company file and the transaction log file. The transaction log records every change made to the company file since the last full backup. When the two files fall out of alignment — different timestamps, mismatched internal pointers, or a log that references data the company file does not contain — QuickBooks refuses to open the file to avoid writing inconsistent data.

What Triggers It

The most common triggers our engineers see are:

• Copying or moving the company file without the transaction log. When a user copies only the .qbw file to a new location and leaves the .tlg file behind, QuickBooks detects the mismatch on the next open attempt.
• An improper shutdown. A power outage, a forced system restart, or a crash that interrupts QuickBooks while it is writing to the company file can leave the log and the data file out of sync.
• Network storage timing issues. In multi-user setups where the company file lives on a network share, latency or a brief disconnection during a write operation can desynchronize the two files.
• Antivirus or backup software interference. Security software that locks or quarantines the .tlg file while QuickBooks is running can prevent the log from updating, creating the mismatch.
• Restoring from an incomplete or damaged backup. A backup that did not capture both files consistently will reproduce the mismatch on restore.

How to Fix It

Our engineers recommend working through these scenarios in order, starting with the most common cause.

Scenario 1: The file was copied without its transaction log

1. Locate the original folder where the company file was stored before the copy.
2. Check whether the .tlg file (same name as the company file, with a .tlg extension) is present there.
3. Copy the .tlg file to the same folder as the current company file.
4. Open QuickBooks and attempt to open the company file again.

If the original .tlg file is no longer available, proceed to Scenario 3.

Scenario 2: A crash or improper shutdown caused the mismatch

1. Close QuickBooks on all workstations.
2. Navigate to the folder containing the company file.
3. Locate the .tlg file and rename it (for example, add .old to the end of the filename). Do not delete it — keep it as a fallback.
4. Open QuickBooks and attempt to open the company file. Without the log, QuickBooks will attempt to open the company file directly.
5. If the file opens successfully, immediately create a full backup (File ▸ Back Up Company ▸ Create Local Backup). This generates a fresh, consistent transaction log.

Scenario 3: The mismatch persists or the file still will not open

1. Close QuickBooks on all machines.
2. Locate the company file folder and identify both the .qbw and .tlg files.
3. Rename the .tlg file by adding .old to the extension.
4. Use the QuickBooks Auto Data Recovery feature if it is available for your version: copy the .qbw.adr file from the Auto Data Recovery folder, rename it to .qbw, and attempt to open it.
5. If Auto Data Recovery is not available or does not resolve the issue, restore from the most recent verified backup (File ▸ Open or Restore Company ▸ Restore a backup copy).
6. If no usable backup exists, the company file itself may need professional repair. Our engineers can rebuild the internal structure of the file and re-establish a valid transaction log.

Scenario 4: Antivirus or backup software is interfering

1. Temporarily disable real-time scanning or backup locking on the folder that contains the company file.
2. Rename the .tlg file as described in Scenario 2.
3. Open the company file and create a fresh backup.
4. Re-enable the antivirus software and add the QuickBooks data folder to its exclusion list so it does not lock the .tlg file during normal operation.

How to Prevent It Recurring

• Always move or copy the company file and the transaction log file together. The simplest approach is to create a portable company file (.qbm) or a full backup (.qbb) before relocating data, then restore at the destination.
• Schedule regular verified backups. A verified backup resets the transaction log cleanly, which reduces the chance of a mismatch accumulating over time.
• Ensure every workstation shuts down QuickBooks properly at the end of the day. Avoid powering off machines while QuickBooks is open.
• Configure antivirus and backup software to exclude the QuickBooks company file folder from real-time scanning and file locking.
• On network installations, verify that the host machine has stable connectivity and that no workstation loses its network connection during a transaction save.