QuickBooks Error 6000-34: Repairing a Damaged Company File

Error 6000-34 stops QuickBooks Desktop from opening a damaged company file; this guide explains the cause and how to get the file opening again.

Error 6000-34 appears at the moment QuickBooks Desktop tries to read a company file into memory. The program finds the file, starts the load, then stops and reports the two codes. Our engineers see this failure often, and in most cases the file itself is damaged. The sections below cover the message, the meaning, the triggers, and the repairs that hold up in practice.

The exact message

When the failure occurs, QuickBooks shows a dialog that reads:

An error occurred when QuickBooks tried to access the company file.

The codes -6000, -34 appear with it, sometimes written as one string, 6000-34. Wording varies a little between releases, but the two numbers identify the fault. After the dialog, the file may open partially, or not at all.

The meaning of the code

The 6000 family covers failures that happen while QuickBooks opens or works inside a company file. The suffix narrows the fault. In the -34 variant, the program reached the file, began reading it, and hit structural damage or a corrupted companion file that halted the load. QuickBooks then treats the file as unreadable and exits with the code pair. The numbers matter less than the fact behind them: the read failed, and something on disk is the reason.

Common triggers

Our repair history points to five triggers, ordered here from most to least common.

Damage inside the company file. A power cut, a crash, or a forced shutdown while the file was open can leave the internal database inconsistent. QuickBooks then refuses the next open attempt.

Corrupted companion files. Each company file pairs with a network data file (.ND) and a transaction log (.TLG). Damage to either can make a healthy file look unreadable.

Network and hosting faults. Opening the file across a network, with the wrong computer set as host or a dropped connection, returns the same codes.

Windows restrictions. A read-only attribute, or an account without full rights to the folder, blocks the read.

Program damage. In a small share of cases the QuickBooks installation itself is broken, and the file is innocent.

Repair steps for each cause

Start with the first scenario, because it matches most reports.

A damaged company file

  1. Restore your latest backup. Choose File, then Open or Restore Company, then Restore a backup copy, and follow the prompts. A restored backup file is a clean rebuild of the data.
  2. If no backup exists, install the QuickBooks Tool Hub that Intuit publishes, open it, and run its File Doctor scan against the file. The scan inspects the database structure and applies repairs where it can.
  3. If the scan reports damage it cannot repair, try Auto Data Recovery. Close QuickBooks, open the folder holding the company file, and look for a matching .ADR file. Copy it to a new folder, remove the .ADR ending so the name ends in .QBW, and open the copy.
  4. A file beyond those measures needs manual data recovery, not another tool pass.

Corrupted companion files

  1. Close QuickBooks on every computer that uses the file.
  2. Open the folder holding the company file.
  3. Find the .ND and .TLG files that share its name.
  4. Copy the .TLG to a safe place first if data recovery may be needed later; renaming it discards the log it holds.
  5. Rename both files by adding .OLD to the end, then reopen the company file. QuickBooks rebuilds them fresh.

A network or hosting fault

  1. Copy the company file to the desktop of one computer and open it there.
  2. If the local copy opens, the file is healthy and the fault sits in the path, not the data.
  3. On the computer that stores the file, turn hosting on; on every workstation, turn it off. The File, Utilities menu holds the switch.
  4. Browse to the shared folder over the network instead of a mapped drive letter, then open the file again.

Windows restrictions

  1. Right-click the company file, choose Properties, and clear the read-only box if it is checked.
  2. Grant your Windows account full control of the folder that holds the file.
  3. Sign in as a Windows administrator and open the file once more.

Program damage

  1. In the Tool Hub, run the Quick Fix My Program option, then try the file again.
  2. If the error persists, copy the company file to safe storage, uninstall QuickBooks, reinstall it, and open the copy.

Preventing the error from returning

Prevention here is mostly a matter of data hygiene.

  • Schedule automatic backups inside QuickBooks, and keep at least one copy off the computer that hosts the file.
  • Run Verify Data from the File, Utilities menu after each month-end close. It surfaces emerging damage before a file refuses to open.
  • Close the company file and exit QuickBooks before shutting down any computer, and never force the program closed with the file open.
  • Keep the file out of folders that cloud sync tools watch. A sync that writes mid-process is a common path to corruption.
  • Install each maintenance release, since the vendor ships file-handling corrections in them.
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.