Quickbooks File Repair — Quickbooks Error Codes (-6189, -82)

QuickBooks errors -6189 and -82 appear together when QuickBooks cannot open your company file because the database has stopped matching its transaction log. The pairing usually points at a mismatch between the working file and the supporting files QuickBooks reads alongside it, and the original diagnosis on this code is clear: this is a recoverable error.

What error -6189, -82 means

Your company file (.QBW) does not live alone. QuickBooks keeps a transaction log (.TLG) and, in multi-user mode, a network descriptor (.ND) that tells it where and how to reach the data. The -6189, -82 combination is raised when those pieces fall out of step — the log no longer aligns with the database, or the file was opened in a way the database engine cannot reconcile. Because the underlying financial records are typically still present, recovery odds are good.

Symptoms you'll typically see

  • QuickBooks refuses to open the company file and returns the -6189, -82 pair.
  • The file opens on the machine that hosts it but fails from other workstations.
  • Switching to multi-user mode triggers the error, while single-user briefly works.
  • The error follows a copy, restore, or move of the file to a new folder or drive.

Common causes

  • A damaged or mismatched .TLG transaction log paired with the .QBW.
  • A stale or corrupt .ND network descriptor after a server change.
  • The file being opened from a backup or copy while the original was still in use.
  • Hosting set on more than one computer, or the Database Server Manager not running on the host.

What you can safely try first

Make a copy of the company file before touching anything, then work only on the copy. Confirm the file is on the machine that hosts it and open it locally rather than over the network. Renaming the matching .TLG and .ND files (so QuickBooks rebuilds fresh ones) resolves many mismatch cases. Verify that hosting is enabled on the host only, and that the QuickBooks Database Server Manager is running there. If the file still will not open after these steps, stop — further forced opens can worsen the mismatch.

When professional recovery is the safer path

When the .QBW itself carries internal damage rather than a simple log mismatch, the in-app steps will not clear it, and repeated attempts risk overwriting good records. Our engineers reconcile the database against its logs and rebuild a clean, openable file, all handled in-house in North America and never sent overseas. The work is backed by our no-data, no-charge guarantee. See how QuickBooks data recovery works, or start a recovery.