Quickbooks File Repair — C=342

QuickBooks error C=342 signals structural damage to the data tree inside your company file — the internal index QuickBooks uses to locate transactions, lists, and balances. It is frequently followed by an illegal page fault (IPF) in appcore.dll, the module that reads that structure. When the tree is damaged, QuickBooks can no longer walk the file reliably, so it stops rather than risk writing bad data over good.

What the C=342 error means

Your financial records are stored in a relational structure of linked “trees.” Each tree points to the next record in a chain. A C=342 means one or more of those pointers no longer resolves — a branch points to a record that is missing, overwritten, or out of sequence. The raw transaction data usually still exists on disk; it is the map to that data that has broken, which is why a high proportion of C=342 files are recoverable.

Symptoms you will typically see

• QuickBooks crashes the moment the company file opens, or partway through loading.
• An appcore.dll IPF or “QuickBooks has stopped working” message accompanies the C=342 code.
• Verify Data fails, or Rebuild Data starts and then stalls, loops, or reports it cannot complete.
• Specific reports (a balance sheet, an aging report) trigger the error while the rest of the file opens.

Common causes

• Interrupted writes — a power loss, forced shutdown, or crash while QuickBooks was saving to the file.
• Network instability — in multi-user setups, a dropped connection to the server can leave the data tree half-written.
• Disk problems — bad sectors or a failing drive that truncated part of the file.
• File size and fragmentation — very large, heavily-fragmented company files are more prone to index damage.

What you can safely try first

Before anything else, stop working in the file and make a copy — continuing to use a damaged file can overwrite the very records that are still intact. Then, on the copy: run Verify Data to confirm the damage, try the built-in Rebuild Data utility, and restore your most recent pre-error backup or .TLG transaction log if one exists. Run the file locally rather than over the network while testing. If Rebuild loops, errors out, or the most recent clean backup is too old to be useful, stop — repeated rebuild attempts on a damaged tree can deepen the damage.

When professional recovery is the safer path

A C=342 that survives Verify/Rebuild is a job for data-tree reconstruction rather than the in-app utilities. Our engineers repair the damaged tree directly, re-link the orphaned branches, and return a working company file — all done in-house in North America, never shipped overseas. Recovery is backed by our no-data, no-charge guarantee: if we cannot recover your file, you pay nothing. See how QuickBooks data recovery works, or start a recovery.