Fix QuickBooks Desktop Error -6189, -816 (Company File Access)

Last reviewed 2026-07-03 4 min read

Resolve QuickBooks Desktop error -6189, -816 when the transaction log is out of sync. Follow our self-help guide to fix this -6000 family error without upg

When QuickBooks Desktop displays error code -6189, -816, it means the software cannot open or access your company file. This code belongs to the broader -6000 series of errors—a family of issues that all relate to company file corruption, network glitches, or database sync failures. If you are running an older, unsupported version of QuickBooks Desktop and intend to keep it that way, you can resolve this entirely offline.

What Error -6189, -816 Means

Specifically, this error indicates a mismatch between your company file (.qbw) and its corresponding transaction log file (.tlg). QuickBooks uses the transaction log to track unsaved changes before writing them to the main database. If the log file falls out of sync with the company file—often due to an improper shutdown, a sudden power loss, or a network hiccup—QuickBooks locks you out to prevent data corruption.

Common Causes

Before jumping into repairs, it helps to understand what likely triggered the sync failure:

Improper shutdowns: Closing the computer or experiencing a crash while QuickBooks is still open.
Network timeouts: A brief disconnection between a workstation and the server in multi-user mode.
Stale network data files: The .ND (Network Descriptor) files QuickBooks uses to locate the database across your network are outdated or corrupted.
Database server manager conflicts: Multiple instances of the QuickBooks Database Server Manager are running, or the service has stalled.

How to Fix It (Step-by-Step)

Work through these steps in order. They are effective for QuickBooks Desktop Pro, Premier, and Enterprise, regardless of whether the version is officially supported by Intuit.

1. Test with a Local Copy

First, determine if the problem is your network or the file itself.

Copy the company file (.qbw) from your server to your local Desktop.
Open it directly from that location while holding down the Alt key (this suppresses background tasks).
If it opens perfectly, the issue is your network configuration or hosting settings, not the file. If it throws the same error, proceed to the next step.

2. Rename the Transaction Log and Network Files

When .TLG and .ND files become corrupted, QuickBooks gets confused. Renaming them forces the software to rebuild fresh ones.

Navigate to the folder containing your company file.
Locate the .TLG file (it will have the exact same name as your company file but end in .tlg).
Right-click and rename it (for example, add .OLD to the end, making it companyname.qbw.tlg.OLD).
Do the same for the .ND file (companyname.nd.OLD).
Try opening the company file again. (Note: If you do not have a recent backup, renaming the .TLG means you cannot use it to recover data in a worst-case scenario. Always keep a safe copy of the original file before renaming).

3. Rescan with Database Server Manager

If the file opens locally but fails over your network, you need to rebuild the network connection.

Open the QuickBooks Database Server Manager on the computer acting as your server.
Go to the Folders tab and click Browse to select the folder where your company file is stored.
Click Scan. This process reads the folder and generates brand new, clean .ND files.

4. Run Verify and Rebuild

If the file still struggles to open, the database itself may have minor structural damage.

Open QuickBooks and go to File > Utilities > Verify Data.
If QuickBooks detects a problem, select Rebuild Data.
The Rebuild utility will automatically attempt to repair the structural integrity of the database. Run Verify a second time once the Rebuild finishes to ensure the repair was successful.

Preventing the Error from Recurring

To keep your long-term Desktop installation stable, ensure the server computer is set to never go to sleep or hibernate while users are logged in, as sleep modes frequently sever the database connection and corrupt the .TLG file. Additionally, make it a habit to close QuickBooks properly at the end of every workday rather than leaving it running overnight.

When the Company File Itself is Damaged

If you have renamed the .TLG, rescanned the database, and the Verify/Rebuild utility fails to fix the error, your company file is likely suffering from deep structural corruption. At this stage, manual intervention is required to salvage the data. When you face severe database corruption, our team provides direct QuickBooks company file repair services to extract your data and rebuild a healthy, working .qbw file so you can get back to managing your books.