QuickBooks Error C=143 -- Data Damage in Your Chart of Accounts

QuickBooks error C=143 signals data damage in your chart of accounts or lists; our engineers repair the file so your records open normally again.

QuickBooks Desktop raises error C=143 when it tries to read your chart of accounts or a transaction list and finds records it cannot make sense of. The list refuses to open, and the dialog that appears explains almost nothing. This page explains what the code means, what triggers it, and how our engineers repair the file behind it.

What does the error say?

The dialog is short. In most cases it shows little more than the code itself, written as C=143, and a button to close it. The message arrives when you click Lists, open the Chart of Accounts, or run a report that reads those records. Sometimes QuickBooks freezes briefly first, then refuses the operation. Because the dialog carries no description, it is easy to assume the QuickBooks installation has failed. It has not; the fault sits inside the company file, so reinstalling the program changes nothing.

C=143 is a data damage code

The C= family covers internal errors QuickBooks raises when it meets a condition it cannot recover from while reading or writing data. C=143 points at damage in the structures holding your accounts and transaction records. When those records disagree with the file's own indexes, QuickBooks stops and reports the code rather than display numbers it cannot trust. The damage can sit in the chart of accounts, in a transaction list, or in the links that tie transactions to the accounts they post to.

That distinction matters. No update, reinstall, or new license will clear the code, because the problem lives in the data, not the software.

Common triggers

Damage rarely appears without a cause. In our repair work the same few culprits turn up again and again.

  • A write that never finished: a power cut, a forced shutdown, or QuickBooks closing while it was still saving.
  • A restore of an older backup into a different QuickBooks year or edition, or an upgrade that moved a file across several versions at once.
  • A company file kept on a network drive or NAS with an unstable connection to the host computer.
  • An earlier rebuild run on a file whose damage the rebuild could not actually repair.

How do you fix it?

Work through the scenarios below in order. The first covers most of the cases our engineers see.

Scenario 1: the error appears in the file you use every day

  1. Switch to single-user mode so no other copy of QuickBooks touches the file while you work.
  2. Make a fresh local backup under File, Back Up Company, Create Local Backup. Keep that copy untouched; it is your safety net.
  3. Run Verify Data under File, Utilities, Verify Data. The check reads the whole file and reports what it finds.
  4. Open the QBWin.log file that Verify names when it finishes. It lists the records that failed the check, and it is the first thing an engineer will ask for if the repair needs to go further.
  5. If Verify reports damage, QuickBooks will offer to rebuild. Treat that offer carefully. A rebuild can finalize damage that a specialist could otherwise unwind, and on some files it makes matters worse. If you run one anyway, run it on a copy, never on your only file, then run Verify again to see what changed.
  6. If Verify finds nothing yet the list still refuses to open, the damage sits where the built-in check cannot reach. Stop using the file and have it assessed; every further session risks writing new records onto damaged space.

Scenario 2: the error started after an upgrade or a restore

Go back to the backup made just before the change and run Verify on that copy in single-user mode. If the older file is clean and its lists open normally, the conversion introduced the damage. Do not keep working in the new file. A conversion repair needs the pre-upgrade backup intact, together with the QBWin.log from the damaged copy. When you ask for the file to be evaluated, include the Product Information screen (press F2); it shows the file size and the customer, vendor, and transaction counts.

Scenario 3: the file lives on a network drive

Close QuickBooks on every machine, copy the company file to the local desktop, and run Verify against that local copy. A clean result means the damage lives in the network copy or in the write path between machines; restore your latest known-good backup onto the host and test again. If the local copy throws the same error, treat it as scenario 1.

Scenario 4: damage prevents a backup

When the backup itself fails, or Verify crashes partway through, stop creating copies by trial and error. Compress the company file into a zip archive and send that for evaluation instead; an engineer can work on the raw file when no backup or portable copy can be made. Do not run a rebuild in this state. Leave that side to the engineer who has the file open.

Keeping C=143 from coming back

  • Back up every working day and keep a rolling set of backups rather than overwriting a single file.
  • Run Verify after every upgrade, conversion, or large import, while any problem is still small.
  • Never force QuickBooks closed or power the machine off while it is saving a transaction.
  • Host the file on one stable machine with a healthy disk, and avoid two people editing from different hosts at once.

A code that returns session after session means the damage has outgrown the tools built into the program. The sooner the file stops being used, the more of your records a repair can bring back.

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.