QuickBooks Error 6108: Condense Data Stops Partway

QuickBooks Error 6108 stops the Condense Data utility partway through; we explain what the code means and how to get the condense working again.

Error 6108 is the code QuickBooks Desktop shows when the Condense Data utility quits before it finishes. The company file usually survives the failure, but it will not get any smaller until the fault behind the code is cleared. This page covers the message, the cause, and the order of steps our engineers work through.

What does the error message say?

Most often you see a Windows dialog that reads: "QuickBooks has encountered a problem and needs to close. We're sorry for the inconvenience." The number 6108 appears in the error details or in the dialog title. Some releases instead show a notice from the condense itself, stating that your data could not be condensed. The wording varies by version. The number and the failed condense are the constants.

What does error 6108 mean?

The 6000 series covers company file trouble, and 6108 is a condense-specific failure inside it. Condensing is not simple deletion. The utility removes old transactions and writes summary journal entries in their place, so it rewrites large portions of the file. When it meets a record it cannot read or rewrite cleanly, it stops rather than produce a damaged result. The code therefore points at structural damage that, in most cases we see, existed before the condense began.

What triggers error 6108?

Damage already inside the file is the leading trigger. Broken transaction links, damaged list entries, and audit trail faults all qualify. Verify Data often flags them beforehand, but not always.

Where and how the condense runs matters too. The utility wants to work alone: single-user mode, local drive, nobody else in the file. Running it in multi-user mode, or against a file on a network share, invites failure.

An interrupted run is the third trigger. A power cut, a forced close, or a machine that sleeps mid-condense can leave the file and its transaction log out of step.

The last common trigger is an out-of-date release. Later builds carry condense fixes that older ones lack.

How do you fix error 6108?

Work the scenarios in order. The first one clears most cases we see.

The file itself is damaged

1. Make a manual backup first: choose File, then Back Up Company, and store it somewhere safe.
2. Run Verify Data (File > Utilities > Verify Data) and read the result.
3. If verify reports problems, run Rebuild Data from the same menu and accept its backup prompt. Rebuild can need several passes, so repeat until verify comes back clean.
4. Retry the condense. If it fails again, condense a narrower window: transactions before an earlier cutoff date, not everything at once.
5. If verify still fails, restore your most recent backup and verify that copy instead. Condense it once it passes.
6. When no backup verifies clean, the damage sits in data that rebuild cannot rewrite. A dedicated file repair is then the practical route. Our engineers repair files in this state and condense them once the structure is sound.

The condense ran over a network or in multi-user mode

1. Have every user close QuickBooks.
2. Press F2 and check the Location field in the Product Information window. A network path there confirms the file is not local.
3. Copy the company file, with its .TLG file, to a local drive on your fastest PC.
4. Open the copy, switch to single-user mode, and run the condense there.
5. Copy the file back afterwards and re-enable hosting on the machine that serves the file.

A previous condense was interrupted

1. Reopen the company file and let QuickBooks finish its startup checks. If it offers to complete or undo partial condense work, allow it.
2. Create a fresh full backup with verification. This also brings the transaction log back into step with the file.
3. Run Verify Data, then retry the condense.

QuickBooks is behind on updates

1. Update to the latest release from the Help menu, then close and reopen QuickBooks.
2. Verify the file, then run the condense again.

How can you stop error 6108 from coming back?

Run Verify Data on a fixed schedule; monthly suits most files. Rebuild whenever it reports problems, because damage caught early rarely blocks a condense.

Always accept the backup prompt before a condense starts. It is your rollback if the run fails.

Do the condense in single-user mode, on a local copy, outside working hours. Disable sleep on the machine, keep laptops plugged in, and never force QuickBooks closed mid-run.

Keep QuickBooks Desktop on the current release. Press F2 now and then to watch file size and table counts, and condense before the file grows so large that a run takes hours.