QuickBooks Error 6155: Running Diagnostics for Damaged File Headers

QuickBooks Error 6155 occurs when QuickBooks cannot open your company file because the file header is corrupted, damaged, or unreadable. The header functions as the structural table of contents for your database; when its pointers or metadata become corrupt, QuickBooks stops the opening process to prevent catastrophic data loss. In most cases, you can resolve this error by verifying folder read/write permissions, restoring a recent backup, or running the diagnostic file repair utility in the QuickBooks Tool Hub.

Fast-Fix: The 45-Second Solution

To resolve Error 6155 immediately, close QuickBooks, download and run the QuickBooks Tool Hub, and select “QuickBooks File Doctor” under Company File Issues. Error 6155 is primarily caused by corrupted database header pointers or restricted Windows folder permissions on the .qbw file. Running File Doctor automatically repairs header blocks and resets read/write security permissions across the hosting folder.

Quick Status & Triage Snapshot

  • Data Risk Tier: Medium to High (header corruption can prevent database mounting, but raw transaction tables usually remain intact).
  • Multi-User Impact: Yes. If the header on the host file is damaged, all workstations are locked out.
  • Common Trigger: Abrupt system shutdowns during save operations, server storage disconnects, or third-party backup software locking the file during an update.
  • Estimated Fix Time: 15 to 30 minutes.

Diagnostic Flowchart: Error 6155 Decision Path

[Start: Error 6155 appears on file open]
   │
   ▼
Is the company file stored on a local drive (C:) or a network share?
   ├─► Local Drive (C:)
   │      │
   │      ▼
   │   Run QuickBooks File Doctor via Tool Hub.
   │   Did File Doctor clear the error?
   │      ├─► Yes ──► [Resolved: Open file & verify data]
   │      └─► No ───► Test file in clean directory / restore backup.
   │
   └─► Network Share / Server
          │
          ▼
       Check folder permissions for "Everyone" and "QBDataServiceUser".
       Are full permissions assigned?
          ├─► No ──► Grant Full Control, rename .ND/.TLG, retry.
          └─► Yes ─► Run File Doctor on the host server directly.

Is Your Data at Risk?

The risk level depends on when the error surfaced:

  • Low Risk: If Error 6155 appeared immediately upon opening QuickBooks in the morning after a standard reboot, the issue is frequently a file lock or a folder security permission problem rather than actual internal database destruction.
  • High Risk: If the error appeared immediately following an operating system freeze, a power outage during invoice entry, or an interrupted rebuild process, the header pointer damage is likely structural. Do not attempt repeated forced opens, as this can fragment unwritten cache data.

Technical Anatomy: What This Error Means

QuickBooks company files (.qbw) run on an embedded Sybase/Advantage Database Server engine. The first blocks of the .qbw database contain the file header. This header holds essential metadata: the database schema version, transaction counter offsets, data table pointers, and verification checksums.

When you launch a company file, QuickBooks reads the header before mounting the data tables. If the checksum calculated at launch does not match the value stored in the header, or if the header indicates an unclosed transactional write from an interrupted session, QuickBooks aborts the handshake and throws Error 6155. It refuses to mount the database to avoid writing new transactions onto broken table indexes.

Differential Diagnosis: Don’t Confuse This With…

  • QuickBooks Error 6000, -80: Indicates data damage deep inside transaction records or multi-user access conflicts across the local network, rather than isolated header corruption.
  • QuickBooks Error 6123, 0: A network communication breakdown where the client loses connection to the database server during the handshake, leaving the file header completely undamaged.
  • QuickBooks Error 6177, 0: Occurs when QuickBooks uses an incorrect path or localized drive letter to reach the server rather than an actual damaged file block.

Step-by-Step Repair Guide

Follow these steps progressively, starting with the least invasive tool.

Step 1: Run QuickBooks File Doctor from the Tool Hub

  1. Close all open instances of QuickBooks Desktop.
  2. Download the latest version of the QuickBooks Tool Hub and install it on the machine hosting the file.
  3. Open the Tool Hub and select the Company File Issues tab on the left menu.
  4. Click Run QuickBooks File Doctor.
  5. Select your company file from the drop-down menu (or click Browse to locate it).
  6. Select Check your file and network, enter your QuickBooks Admin password, and select Continue.
  7. Allow the tool to scan and repair the file headers. This process can take between 5 and 20 minutes depending on file size.

If File Doctor reports that it resolved the issue, open QuickBooks and launch your file. If the tool reports an unrecoverable structural error, proceed to Step 2.

Step 2: Clear Support Files (.ND and .TLG)

Damaged network configuration and transaction log support files can feed corrupt header pointers back into QuickBooks. Re-indexing these files forces QuickBooks to rebuild clean metadata headers.

  1. Open File Explorer and navigate to the directory containing your .qbw company file.
  2. Locate the two companion files sharing your exact company name:
    • [YourCompanyName].qbw.ND (Network Data)
    • [YourCompanyName].qbw.TLG (Transaction Log)
  3. Right-click each file and rename them:
    • Change [YourCompanyName].qbw.ND to [YourCompanyName].qbw.ND.old
    • Change [YourCompanyName].qbw.TLG to [YourCompanyName].qbw.TLG.old
  4. Do not touch or rename the main .qbw file.
  5. Launch QuickBooks Desktop and open the company file. QuickBooks will generate new, undamaged .ND and .TLG support files automatically.

Step 3: Verify and Repair Folder Read/Write Permissions

If Windows revokes write access to the header file, QuickBooks reports the header as damaged.

  1. Right-click the folder containing your company file and select Properties.
  2. Click the Security tab, then select Edit.
  3. Verify that the following user accounts are listed and have Full Control checked under “Allow”:
    • SYSTEM
    • Everyone
    • Administrators
    • QBDataServiceUserXX (where XX corresponds to your QuickBooks version, such as 34 for 2024 or 36 for 2026)
  4. If an account is missing, click Add, enter the name, and check Full Control.
  5. Click Apply, then OK, and reopen the company file.

Step 4: Test in a Clean Local Directory

To isolate whether the issue is inside the file itself or tied to the local directory structure:

  1. Create a new folder directly on your root drive: C:\QBTest.
  2. Copy (do not cut) your .qbw file from its original location and paste it into C:\QBTest.
  3. Open QuickBooks, select Open or Restore an Existing Company, and browse to C:\QBTest.
  4. If the file opens successfully, your original folder path or security environment is damaged. If the file still throws Error 6155 in C:\QBTest, the header corruption is embedded directly inside the .qbw file.

Hard Stop: When to Call an Expert

Cease automated troubleshooting and consult a certified data recovery specialist if you encounter any of the following symptoms:

  • The company file displays a file size of 0 KB.
  • QuickBooks File Doctor crashes mid-scan with a fatal unhandled exception or reports “Corrupt Database Header Block 0.”
  • Restoring a recent .QBB backup produces the exact same Error 6155, indicating that corruption was backed up previously.

If you encounter secondary issues during diagnosis, see these related guides:

Closing the Books

A file header error sounds severe, but in the overwhelming majority of cases, the actual accounting records inside your database remain untouched. Work methodically through permission resets and the QuickBooks File Doctor before jumping to drastic measures. As long as you preserve your original file and avoid forced hard shutdowns during diagnostic scans, your financial records can typically be brought back online without data loss.