QuickBooks Error C=102: Damage in a Transaction List

QuickBooks Error C=102 points to damage in a transaction list. Our engineers explain what the code means and how to get the file working again.

Error C=102 is an old QuickBooks Desktop code that still surfaces in company files with years of history in them. It means one of the transaction lists inside the file has structural damage. In most cases a verify and rebuild clears it. When that fails, the break sits deeper, and the file needs repair at the list level.

What does the error message say?

The dialog is sparse. Most installations show a single line:

Error: C=102

The wording around that line varies by release. Some builds add a general note that QuickBooks ran into a problem with the company file. Others suggest rebuilding your data. The timing varies too. The code can appear when you open the file, when you save a transaction, or partway through Verify Data. The C= number is the part worth reading. It tells you the failure lives inside the data file, not in Windows, your license, or your network.

What does the code mean?

QuickBooks keeps transactions in internal linked lists. Each record points to the next in sequence, and related lists reference each other. A C= code is the program telling you one of those internal reads failed.

C=102 points at a transaction list. Somewhere in it, a record is out of sequence, a link points nowhere, or a list entry no longer matches the transactions attached to it. The program reaches the broken spot, stops, and reports the code. Any feature that scans the same list can set it off. That is why the error can seem to follow you around the program.

Common triggers

Five situations cover almost every C=102 file we see:

  • A file with many years of entries. Long lists hold more links, and more places to break.
  • An interrupted save. A power cut, a forced quit, or a workstation shut down mid-write leaves a list half-written.
  • Unstable multi-user access. A dropped connection during a transaction can break the link between two records.
  • A version change. Upgrading a file, or restoring a backup into a different edition, rewrites internal structures and can expose older damage.
  • Quiet damage from an earlier event. Some breaks sit undisturbed until a report or a search touches the affected list.

How do you fix it?

Work through the scenarios in order. The first one resolves most files.

Damage confirmed by Verify Data (the common case)

  1. Back up first. From the File menu, choose Create Backup, and save it on the local drive. Rebuild changes data in place, so keep a fallback.
  2. Switch to single-user mode from the File menu. Nothing else should write to the file during the repair.
  3. Run Verify Data: File, Utilities, Verify Data. Note what it reports.
  4. Run Rebuild Data: File, Utilities, Rebuild Data. It will ask for a backup before it starts; let it take one. On large files the pass can sit still for a long time. Leave it alone until it reports completion.
  5. Run Verify Data again. A clean result means the list damage is gone.
  6. If Verify still fails, run Rebuild once more. A second pass clears damage the first one could not.
  7. If the error survives that, stop. Restore the most recent backup made before the error appeared, then verify the restored file.

The error appeared after an upgrade or a restore

  1. Stop working in the new file. Every save risks writing over the weak spot.
  2. Run Verify Data in single-user mode and read the result.
  3. If Verify fails, run Rebuild once, then verify again.
  4. If damage persists, go back to the backup taken before the version change. Verify that copy clean, then repeat the upgrade.

The file is shared over a network

  1. Check hosting. On each machine, open File, Utilities. Only the computer that holds the file should show Stop Hosting Multi-User Access.
  2. Run Verify and Rebuild at the machine holding the file, in single-user mode. Do not run them from a workstation over the wire.
  3. Inspect the network between passes. A failing cable, switch, or wireless hop can corrupt a save in transit.
  4. Re-map the shared drive if its path changed, so workstations are not writing through a stale connection.

Rebuild fails, or the error keeps returning

  1. Stop rebuilding. A utility that cannot rewrite the damaged structure will not succeed on a fourth or fifth pass, and every pass writes changes.
  2. Set aside the backup made before the first rebuild.
  3. Write down what you were doing when the code first appeared. It narrows the search to one list.
  4. At this stage the file needs its lists repaired directly, on a working copy, by someone who works at that level. Our engineers do that work in-house, and a repaired file is verified clean before it comes back to you.

How do you keep it from coming back?

  • Turn on automatic backups and keep several generations, not just the newest.
  • Run Verify Data once a month. Damage caught early is easier to clear.
  • Close QuickBooks properly. Never force it shut or power off during a save, and let long reports finish before you walk away.
  • Install each release update when it arrives. Later releases carry fixes for known write problems.
  • Press F2 now and then and read the Product Information window. A growing file size and target count tell you the lists are getting long. A planned condense keeps the file lighter than an emergency repair would.
Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.