Fixing QuickBooks Error -6189 and -6190 -816 After Moving a Company File
QuickBooks errors -6189 and -6190 -816 typically appear when a company file and its transaction log fall out of sync after being copied or moved.
QuickBooks Desktop users frequently encounter Error -6189 or -6190 -816 when attempting to open their company file, particularly after relocating or copying the file from one location to another. The software refuses to open the data, blocking all access to financial records. These errors indicate a breakdown in how QuickBooks tracks recent changes, and resolving them requires realigning the components that keep the company data intact.
Understanding the Root Cause
Both Error -6189 and Error -6190 -816 fundamentally point to a data mismatch. QuickBooks Desktop relies on a primary company file, recognizable by its .qbw extension, to store all financial records. Alongside this file sits a transaction log, marked as .tlg, which acts as a continuous record of every change made during a working session. Under normal operations, these two files must remain perfectly synchronized.
The mismatch commonly occurs when a user copies or moves the company file while QuickBooks is still actively running. If the application is left open during the transfer, the resulting copied files often fail to mirror one another accurately. The primary company file might reflect one state of the data, while the transaction log reflects another. The errors can also surface when a file set up for single-user access is suddenly treated as a multi-user file, or when different workstations on a network inadvertently point to separate, conflicting copies of the same data.
Securing the Data Before Troubleshooting
Before attempting any repairs, users must ensure that all active QuickBooks sessions are completely closed across all computers. No other user should have the file open, and no background instances of the software should be running. Once the environment is clear, the immediate priority is data preservation. Creating a manual backup of the current, error-producing file provides a safety net before any diagnostic tools attempt to rewrite or repair the data structure.
Running the QuickBooks Tool Hub
The primary method for resolving this synchronization failure is the QuickBooks Tool Hub. Users should navigate to the Company File Issues tab within the hub and run File Doctor. This integrated utility is designed to scan the directory, identify discrepancies between the company file and its associated log, and automatically repair standard file damage or network glitches that might be preventing the software from reading the data correctly.
Manually Realigning the Transaction Log
When the automated tools fail to clear the error, manually forcing QuickBooks to rebuild its tracking files is the next step. Users can locate the folder containing the problematic company file and identify the corresponding .tlg file. Renaming this file—often by simply adding the word “old” or a similar designation to the end of the file name—forces QuickBooks to generate a brand new, empty transaction log the next time the company file opens.
The same action is frequently applied to the network data file, which carries the .nd extension. These files act as directional markers for QuickBooks. Removing the old ones allows the software to recreate them from scratch, effectively wiping out the mismatched data paths that trigger the -6189 and -6190 -816 alerts.
Isolating the File to Rule Out Network Confusion
Because these errors often stem from multiple computers attempting to read different versions of the same file, isolating the data can rule out network variables. Moving the primary company file directly to the desktop of a local machine, rather than accessing it over a server or shared drive, allows the user to test the file in a controlled environment. If the file opens successfully on the local desktop, the original issue likely stems from network routing, conflicting file copies, or multi-user hosting settings rather than actual data corruption.
Preventing Future Mismatches
Avoiding a recurrence of these errors requires strict file-management habits. Users should never copy, move, or rename a .qbw file while QuickBooks is running. The proper procedure is to close the company file from within the software, exit the application entirely, and only then move the data to a new location. This ensures that the primary file and the transaction log are completely static and perfectly matched at the moment of transfer.
When the File Remains Unreadable
If the error persists after realigning the transaction log, clearing the network data files, and running the automated diagnostic tools, the primary company file itself is likely damaged. In these severe cases, the standard built-in repair utilities are insufficient. Users facing a damaged .qbw file may need a professional QuickBooks Desktop file repair service to rebuild the structural integrity of the data. Specialists can piece together the intact portions of the company file and its transaction log, returning a fully functional, reconciled file that opens normally.