QuickBooks Error 6000 -83: What It Means and How to Fix It (2026)
Quick Answer
Error 6000, -83 means QuickBooks found the company file but cannot verify its integrity. This usually indicates a damaged .TLG transaction log file or a conflict with the .ND configuration file.
What Error 6000, -83 Actually Means
Error -6000, -83 is a file verification error. QuickBooks can locate and access the company file but something is wrong with its companion files (the transaction log or network descriptor). The company file itself may be fine, but QuickBooks refuses to open it because it cannot verify the supporting files.
Common causes:
- The .TLG (Transaction Log) file is damaged or out of sync with the .QBW file
- The .ND (Network Descriptor) file contains stale or incorrect hosting information
- A previous backup restore did not include the matching .TLG file
- An unexpected shutdown corrupted the transaction log mid-write
How to Fix Error 6000, -83
Rename the .TLG and .ND files
Navigate to your company file folder. Rename CompanyFile.QBW.TLG to CompanyFile.QBW.TLG.OLD and CompanyFile.QBW.ND to CompanyFile.QBW.ND.OLD. QuickBooks recreates both files when you open the company file.
Open the file from the correct location
Open QuickBooks first, then use File > Open or Restore Company > Open a company file. Browse to the file manually rather than using the recent files list, which may point to an old or wrong location.
Copy the file to the desktop and try opening it
Copy just the .QBW file (not .TLG or .ND) to your desktop. Try opening it from there. If it works, the issue is with the original location, not the file.
Run Verify and Rebuild
Once the file is open, go to File > Utilities > Verify Data. If it finds problems, run File > Utilities > Rebuild Data. This repairs internal data structures.
Why Error 6000, -83 Keeps Coming Back
Error -83 tends to recur after power outages, forced shutdowns, or system crashes during QuickBooks operations. The transaction log gets corrupted because the write was interrupted. Use a UPS (uninterruptible power supply) on the server and enable Windows auto-recovery features.
Scan Your QuickBooks for Error 6000, -83 Conditions
Hubricon's Data Janitor scans your QuickBooks file and flags the exact conditions that cause Error 6000, -83 — uncategorized transactions, duplicate entries, reconciliation gaps, and more. Free scan, no signup required.
Takes ~90 seconds. Read-only access. We never modify your QuickBooks data.
Frequently Asked Questions
Will deleting the .TLG file cause data loss?
No. The .TLG file is a transaction log used for recovery. Deleting or renaming it means QuickBooks starts a new log. Any committed transactions in your .QBW file are safe.
What is the .ND file?
The Network Descriptor (.ND) file tells QuickBooks which computer is hosting the company file. If it contains wrong information, QuickBooks cannot verify the file. Renaming it forces a fresh one to be created.
Can Error -83 happen with QuickBooks Online?
No. QBO does not use local company files, transaction logs, or network descriptors.
Should I run Verify or Rebuild first?
Always run Verify first. It checks for problems without changing anything. Only run Rebuild if Verify reports errors. Rebuild modifies the file, so back up before running it.
How does Hubricon handle QuickBooks data integrity?
Hubricon reads your data through the QuickBooks API, which only returns verified, committed data. There is no risk of transaction log corruption or file integrity issues with API-based access.
Stop fixing QuickBooks errors manually
Hubricon monitors your QuickBooks data 24/7 and prevents the conditions that cause errors like 6000, -83. Connect in 2 clicks, see results in 90 seconds.