QuickBooks Error -6120 -- Company File Fails to Open After a Bad Rebuild
QuickBooks error -6120 blocks you from opening your company file after damage or an interrupted verify and rebuild. Here is what it means and how to fix it.
QuickBooks error -6120 appears when the program cannot open a company file because the file's internal structure is damaged. It usually shows up right after a verify or rebuild that did not finish cleanly. The file is often recoverable, and in most cases you can get back into it with the steps below.
What the error message says
The message you see at open time reads:
"Error -6120, 0: An error occurred when QuickBooks tried to access the company file."
Some installations show a shorter variant that lists only the code and the file name. Either way, QuickBooks stops at the opening screen and never loads your data.
What the code means
The 6000 family of codes covers failures that happen while QuickBooks is trying to open a company file rather than while you are working in it. The -6120 entry in that family points to structural damage inside the file itself, or to a rebuild that was started and never completed. The database engine reads the file, finds records it cannot reconcile, and refuses to continue rather than risk writing more data on top of the problem.
What triggers it
Our engineers see three triggers again and again:
- An interrupted rebuild. The machine lost power, was shut down, or froze partway through a rebuild, leaving the file half repaired.
- Latent file damage. A verify reported problems, the rebuild was skipped or failed, and the damage spread until the file would no longer open.
- A crash or forced close while QuickBooks had the file open, which can leave internal pointers inconsistent.
Network problems and stored-on-network files make all three more likely, because a dropped connection mid-write corrupts the same structures.
How to fix it
Work through these in order. Stop as soon as the file opens, and make a fresh backup before you do anything else.
1. Restore from your most recent backup. This is the fastest reliable fix and the one that works most often. Copy a recent .QBB backup to the local hard drive, open QuickBooks, and restore it to a new file name. If the restored file opens, run a verify on it before you resume work. You lose only the transactions entered since that backup.
2. Open a different company file first. Sometimes the error sits in the QuickBooks session rather than the file. Hold Ctrl while double-clicking the QuickBooks icon to open with no company file loaded. Then use the File menu to open your file. If it opens, run verify and rebuild immediately.
3. Run verify and rebuild from the no-company-file state. With the file open from step 2, go to the File menu, choose Utilities, then Verify Data. If verify reports damage, choose Rebuild Data and let it run to completion. Do not close QuickBooks or power off the machine during the rebuild, even if it seems stalled for several minutes.
4. Copy the file locally. If the file lives on a network share or a synced folder, copy the .QBW file and its .TLG companion to a local folder and try opening it there. Sync services and flaky network shares are a common source of this error.
5. Rename the transaction log. Copy the .QBW file to a new folder, then rename the .TLG file that sits beside it, changing its extension to .OLD. QuickBooks builds a fresh log when the file opens. Only do this on a copy, never on the only version of the file.
6. Send the file for repair. If none of the above opens the file, the damage is inside the data itself. A repair service can rebuild the internal structures and return your data in a working file. Have ready the file name, its approximate size, whether it is stored locally or on a network, and the date of your most recent backup.
How to prevent it from coming back
Back up on a schedule you can afford to lose data against; daily is a sensible default for an active file. Run Verify Data weekly and rebuild promptly when verify reports problems. Never close QuickBooks by force, and never let a machine sleep or lose power during a rebuild. Store the company file on a local drive or a stable wired network share, not in a cloud sync folder. Keep an eye on file size as well, because oversized files verify and rebuild more slowly and fail more often.