QuickBooks Error 6000-73: Company File Locked or Damaged

Last reviewed 2026-09-20 4 min read

Error 6000-73 stops QuickBooks Desktop from opening a company file that is damaged or locked; this guide explains the causes and the fix.

Error 6000-73 appears the moment QuickBooks Desktop reaches for a company file and cannot open it. Either something else holds the file locked, or the database inside is damaged. Our engineers clear this code often, and in most cases you can clear it yourself with the steps below.

What does the error message say?

The dialog usually reads:

An error occurred when QuickBooks tried to access the company file. Please try again. If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6000, -73).

Wording varies a little between releases, and the pair may display as 6000 73 or -6000, -73. The dialog can also surface during a backup, a condense, or a switch between single-user and multi-user mode. The advice in the last line of the quote is boilerplate shared across the whole 6000 range. The code, not the wording, tells you what failed.

What does error 6000-73 mean?

The 6000 series covers company file access faults. The second number narrows the cause. Here, QuickBooks reached the file but could not get the exclusive access it needs at open. Either another process held the file, or the data inside was damaged. A stale lock is far more common than real damage, so treat the code as a jammed door rather than a lost ledger.

What triggers error 6000-73?

Several situations produce the same code:

A previous QuickBooks session hung and never released the file.
A workstation lost power or dropped its network link while the file was open.
Hosting is switched on at more than one machine, so two database managers fight over the file.
The file sits in a cloud-synced folder, and the sync tool locked it mid-write.
The Windows account lacks full rights to the folder, or the .qbw is marked read-only.
The transaction log or network data file beside the company file is stale or mismatched.

How do you fix error 6000-73?

Work through the scenarios in order; the first one resolves most cases we see.

Clear the stale lock. Have every user close QuickBooks. Open Task Manager (Ctrl+Shift+Esc) and end any QuickBooks process still running, such as QBW32.exe. Restart the machine that hosts the file, then reopen the company file in single-user mode.
Test with a local copy. Copy the .qbw file to the workstation desktop; do not move the original. If the copy opens, the data is sound and the fault is in the path, the permissions, or the sync. If the copy fails as well, the file itself is damaged, so skip to scenario five.
Rename the companion files. Close QuickBooks everywhere and copy the whole folder first as a precaution. Rename the transaction log (.tlg) and the network data (.nd) file so each name ends in .OLD, then reopen the company file. QuickBooks rebuilds fresh versions of both. The log only matters for disaster recovery, which is why the folder copy comes first.
Correct hosting and folder rights. On each workstation, open the File menu and choose Utilities. If the option reads Stop Hosting Multi-User Access, hosting is on in the wrong place, so stop it. On the server, run the Database Server Manager and scan the folder holding the file. Grant your Windows account full control of that folder, and clear the read-only flag on the .qbw. Move the file out of any cloud-synced folder for good.
Repair or restore. If a local copy opened, run Verify Data from the Utilities menu, and let Rebuild Data finish if verify reports problems. If nothing opens the file, restore your most recent .qbb backup. With no backup, look beside the file for a QuickBooksAutoDataRecovery folder; the copies inside, paired with the transaction log, are the raw material for recovery. That recovery is work our engineers handle directly.

How can you keep it from coming back?

Schedule automatic backups, and keep one copy off the machine that hosts the file.
Run Verify Data monthly, and rebuild whenever it flags a problem.
Keep hosting enabled on exactly one machine, and rescan in the Database Server Manager after any update.
Store the company file on a wired local drive of the server, never in a synced folder.
Close QuickBooks before shutting down Windows, and put the host machine on a battery backup so a power cut cannot interrupt a write.

An interrupted write lies behind much of the damage our engineers see, so that last habit earns its keep.