When QuickBooks displays the message “Your data has been rebuilt, but some errors persist,” the built-in Rebuild Data utility has resolved basic database index and pointer errors, but encountered structural damage it cannot fix automatically. This partial repair status occurs when damaged records require manual intervention, such as orphaned inventory items, broken link tables, or out-of-balance transactions. Your company file is not lost, but you must identify the specific damaged records in your diagnostic logs and correct them manually to prevent corruption from spreading.
Fast-Fix: Clearing Persistent Errors After a QuickBooks Rebuild
Run a second consecutive rebuild, then review QBWin.log for remaining errors. Close QuickBooks, reopen it, and run File > Utilities > Rebuild Data once more; complex integrity issues often resolve on the second pass. If the error repeats, press F2, then F3, open the QBWIN.LOG, search for
LVL_ERROR, and note the damaged transaction or list IDs. Edit or re-save those specific records in QuickBooks, then run Verify Data to confirm a clean pass.
Quick Status & Triage Snapshot
- Data Risk Tier: Medium to High. While minor index errors were fixed, unresolved structural discrepancies will continue to corrupt historical reports or cause sudden application crashes.
- Multi-User Impact: High. Workstations must remain out of the company file in single-user mode until the database verifies with zero errors.
- Common Trigger: Power outages during save operations, large company files with un-truncated transaction logs, or repeated forced terminations via Task Manager.
- Estimated Fix Time: 15 to 45 minutes, depending on the volume of unfixable records.
Technical Anatomy: Why the Automated Rebuild Leaves Errors Behind
The QuickBooks Rebuild Data utility is a sequential batch-repair script. It steps through your relational database tables, rebuilding internal indexes, sorting damaged arrays, and re-linking transaction targets to their sources.
The Automated Rebuild Sequence:
Phase 1: Table Scan ──────> Identifies broken pointers and orphan records.
Phase 2: Automated Fix ───> Re-indexes keys and recalculates standard account balances.
Phase 3: Deep Logic Check ─> Evaluates strict accounting constraints (Debits = Credits).
│
UNRESOLVABLE CONFLICT ENCOUNTERED:
• Example: An invoice references an inventory item that was hard-deleted.
• Example: A transaction split has no balancing credit target.
│
▼
Rebuild cannot "invent" missing accounting data without user approval.
Result: "Your data has been rebuilt, but some errors persist."
The script can repair physical table structures, but it cannot make accounting decisions. If an invoice has an unlinked payment, or if an item list has corrupted metadata that would alter your general ledger balance if deleted, the utility intentionally leaves the record alone. It flags the issue in the system log and notifies you that manual repair is required.
To understand what the initial integrity check discovered before the rebuild ran, review Integrity Report: Interpreting Errors Found by the “Verify Data” Tool.
Diagnostic Flowchart: Resolving Persistent Rebuild Errors
Start: "Some Errors Persist" Warning
│
├── Run Rebuild Data a second time immediately.
│ │
│ ├── Did the second rebuild finish with "No errors found"?
│ │ └── YES: The file is healthy. Resume normal operations.
│ │
│ └── NO: Errors still persist.
│ │
│ ▼
└── Open QBWin.log (Press F2 > F3 > Open File)
│
├── Locate the most recent "LVL_ERROR" entries.
│ │
│ ├── Are the errors tied to List Items (Customers, Vendors, Items)?
│ │ └── Merge or edit the damaged list entries.
│ │
│ └── Are the errors tied to Transactions (Invoices, Bills, Checks)?
│ └── Locate transaction by date/num, re-save or recreate it.
│
└── Run Verify Data to confirm clean pass.
Step-by-Step Guide to Clearing Persistent Errors
Work through these steps in order to isolate and eliminate remaining data errors.
Step 1: Execute a Second Consecutive Rebuild
Complex data damage often involves interdependent tables. Repairing high-level index keys in the first pass exposes deeper subordinate errors that the utility can only resolve during a second pass:
- In QuickBooks, go to File > Utilities > Verify Data.
- When the verification fails, select Rebuild Now (or go directly to File > Utilities > Rebuild Data).
- Follow the prompts to create an updated local backup.
- Allow the process to complete without touching your keyboard or mouse.
- If the message “QuickBooks has rebuilt your data and no errors were found” appears, your database is repaired.
- If the “some errors persist” message appears again, proceed immediately to Step 2.
If the utility enters an infinite loop or runs for hours without completing, follow Rebuild Loop: How to Stop QuickBooks from Getting Stuck in a Rebuild Cycle.
Step 2: Extract the Specific Corrupt Records from QBWin.log
QuickBooks writes every failed repair operation to an internal diagnostic log. You must extract these error lines to determine which records require manual correction:
- Open QuickBooks to your company file.
- On your keyboard, press the F2 key (or Ctrl + 1) to open the Product Information window.
- While that window is open, press F3 (or Ctrl + 2) to open the Tech Help interface.
- Select the Open File tab.
- Locate and click on QBWIN.LOG, then click Open File.
- The log will open in Windows Notepad. Press
Ctrl + Endto scroll to the very bottom of the document. - Press
Ctrl + Fto open the search box, typeLVL_ERROR, and set the search direction to Up. - Click Find Next.
Sample QBWin.log Error Line:
LVL_ERROR|BuildEngine|CheckDoc: Verify Target: Bad target 45892 in Invoice 10452 Date: 10/12/2025
Note the exact transaction type, date, reference number, or list element name identified in the log line. For a detailed guide on navigating this diagnostic log, consult Log Files: How to Locate Verify.log and Rebuild.log in Windows.
Step 3: Manually Edit or Re-enter the Flagged Records
Once you know the exact records causing the failure, you can fix them using one of these targeted methods:
- For Damaged Transactions:
- Open the transaction identified in the log (e.g., Invoice 10452).
- Make a minor edit (such as adding a period to the memo field) and click Save & Close. This forces the database engine to recalculate the transaction’s debit/credit targets and rewrite its pointers.
- If re-saving does not clear the error, take a screenshot of the transaction details, delete the transaction entirely, and manually recreate it.
- For Damaged List Items (Customers, Vendors, Accounts, Items):
- Open the relevant list center (e.g., Item List).
- Locate the damaged entry noted in the log.
- Right-click the item and select Edit.
- Add an asterisk () to the item name, click OK, then edit it again and remove the asterisk.
- If the record remains unreadable, create a clean duplicate item and use QuickBooks’ native merging feature to merge the corrupt entry into the new one.
For deeper technical breakdowns on repairing specific transaction links, review Transaction Table: Fixing Data Integrity Errors in QuickBooks Transactions.
Step 4: Run QuickBooks File Doctor
If multiple database tables report systemic corruption, manual editing can become impractical. In this scenario, run the standalone database repair tool:
- Close QuickBooks Desktop.
- Launch the QuickBooks Tool Hub.
- Select Company File Issues from the menu.
- Click Run QuickBooks File Doctor.
- Select your company file from the drop-down menu, choose Check your file, and enter your QuickBooks Admin credentials.
- The File Doctor will execute low-level repair routines on the underlying Sybase relational database structure.
For full diagnostic usage, reference The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor.
Diagnostic Branching: Common Persistent Error Categories
If your log points to structural errors that cannot be edited through the user interface, check these two common failure categories:
1. Damaged Payroll Tax Tables
If LVL_ERROR references payroll items, payroll summary lines, or historical tax tables, the manual rebuild engine cannot modify them to prevent compliance issues. Download the latest payroll tax table update under Employees > Get Payroll Updates, then run File > Utilities > Verify Data.
2. Out-of-Balance Link Discrepancies
When the log cites “Link mismatch” between payments and invoices, open the customer payment, uncheck the associated invoice to detach the link, save the payment as an unapplied credit, and re-check the invoice to reapply the credit cleanly.
Hard Stop: Critical Warning Signs and Data Recovery Escalation
Stop attempting in-product rebuilds and escalate to an authorized data recovery specialist if you notice:
- Rapidly Escalating Error Counts: The first rebuild log lists 10 errors, but subsequent passes report dozens of new, unrelated table failures.
- Verify Freezes Indefinitely: The Verify Data utility stops responding on the exact same percentage mark every time it runs. If this occurs, follow Verify Data: How to Run Integrity Checks Without Freezing Your PC.
- Missing Historic Balance Sheet Values: Running a balance sheet report displays blank spaces or zeroes for entire fiscal quarters where transactions previously existed.
- Complete Rebuild Abortion: The rebuild terminates abruptly without generating a completion dialogue. See Rebuild Failure: What to Do When “Rebuild Data” Cannot Fix Your File.
Closing the Books
Receiving a notice that “some errors persist” does not mean your accounting database is destroyed. It simply means the automated repair script fixed what it safely could and handed the remaining issues over to you for review. By inspecting QBWin.log for the exact record identifiers, re-saving or recreating those transactions, and verifying the file a final time, you can return your company file to a fully validated state.