QuickBooks Error 6000, -305: Repairing Damaged .TLG and .ND Files

QuickBooks Error 6000, -305 occurs when QuickBooks attempts to open a company file but cannot establish database communication because its companion Network Data (.ND) or Transaction Log (.TLG) support files are damaged, locked, or out of sync. This error blocks both single-user and multi-user access to your accounting file. Renaming these two auxiliary files forces QuickBooks to automatically generate clean versions, resolving the file-handshake failure without altering your core financial records.

Fast-Fix: The 45-Second Solution

To resolve Error 6000, -305 immediately, close QuickBooks on all computers, navigate to your company file folder, and rename both the .ND and .TLG files. Add .old to the end of each filename (e.g., MyCompany.qbw.nd.old and MyCompany.qbw.tlg.old). Next, open QuickBooks and open your company file normally. QuickBooks will automatically recreate clean configuration and log files, clearing the startup lock.

Quick Status & Triage Snapshot

• Data Risk Tier: Low (The primary .QBW company file is typically undamaged; the corruption is isolated to external support files).
• Multi-User Impact: High (Blocks access for all workstations attempting to connect to the hosted company file).
• Common Trigger: Sudden server reboots, network interruptions during file saves, or third-party backup utilities locking files during active operations.
• Estimated Fix Time: 3 to 10 minutes.

Diagnostic Flowchart: Error 6000, -305 Decision Path

Plaintext

[Start: QuickBooks displays Error 6000, -305 when opening file]
       │
       ▼
Close QuickBooks on all workstations
       │
       ▼
Locate Company Folder > Rename .ND and .TLG to .ND.old and .TLG.old
       │
       ▼
Open QuickBooks and launch the Company File (.QBW)
       │
       ├─► Does the file open successfully?
       │     │
       │     ├─► YES: Clean files generated. Run a verified backup to reset the new .TLG baseline.
       │     │
       │     └─► NO: File still fails to open.
       │           │
       │           ├─► Is the company file stored on a dedicated server/network share?
       │           │     │
       │           │     ├─► YES ──► Rescan the folder using QuickBooks Database Server Manager.
       │           │     └─► NO  ──► Run QuickBooks File Doctor via QuickBooks Tool Hub.
       │           │
       │           └─► Does the error persist after Tool Hub scan?
       │                 └─► Test file locally on Desktop to isolate folder permission conflicts.

Is Your Data at Risk?

Because Error 6000, -305 targets auxiliary support files rather than the core transaction tables inside your .QBW database, your underlying accounting data is safe in the majority of cases:

• Safe Operations: Renaming .ND and .TLG files is a non-destructive procedure. The .ND file contains simple network pointer configuration text, and a new .TLG file is created on the next successful startup.
• Backup Consideration: If your company file experienced a severe crash during a batch entry or year-end close, the .TLG file might contain uncommitted transaction stream logs. Renaming it is safe, but keep the .tlg.old file rather than deleting it immediately until you verify your account balances. For deep transaction log recovery techniques.

Technical Anatomy: The Role of .ND and .TLG Files

When QuickBooks opens a company file, it does not access the .QBW database in isolation. It relies on a multi-part file handshake:

1. The Network Data File (.ND): A plain-text configuration file created by the QuickBooks Database Server Manager. It specifies the host machine’s IP address, computer name, network port, and hosting mode. If this file contains outdated network paths or corrupted characters, QuickBooks cannot locate the Sybase database engine.
2. The Transaction Log File (.TLG): A continuous log that mirrors every transaction entered into QuickBooks between full backups. If QuickBooks crashes during a write operation, the .TLG file can become desynchronized with the .QBW file header, causing Error -305 when the engine checks for file consistency.
3. The Lock Failure: When either file is corrupted or held open by a zombie process (or an unoptimized antivirus scanner), the database engine rejects the connection request to prevent structural damage.

Differential Diagnosis: Don’t Confuse This With…

• QuickBooks Error 6000, -77: Triggered by incorrect folder permissions or trying to open a file stored on an invalid drive type (such as a mapped drive path).
• QuickBooks Error 6000, -82: Indicates that another workstation has mistakenly turned on hosting mode, creating a host conflict with the main server.
• QuickBooks Error 6000, -301: Indicates that disk encryption software or third-party backup utilities are actively conflicting with the file system during read/write cycles.

Step-by-Step Repair Guide

Follow these steps in order to replace corrupted support files and restore connectivity.

Step 1: Manually Rename the .ND and .TLG Files

This is the primary fix for Error 6000, -305.

1. Ensure QuickBooks is completely closed on all workstations and the host server.
2. Open Windows File Explorer and browse to the folder where your company file is located (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
3. Find the files sharing the same name as your company file with the extensions .ND and .TLG:
   • [YourCompanyName].qbw.nd
   • [YourCompanyName].qbw.tlg
4. Right-click [YourCompanyName].qbw.nd, select Rename, and add .old to the end: [YourCompanyName].qbw.nd.old
5. Right-click [YourCompanyName].qbw.tlg, select Rename, and add .old to the end: [YourCompanyName].qbw.tlg.old
6. Open QuickBooks Desktop and select your company file. The software will create fresh .ND and .TLG files automatically.

Step 2: Rescan Folders with QuickBooks Database Server Manager

If the file is hosted on a network server and renaming the files does not resolve the issue, the database manager needs to re-index the folder.

1. On the host server, open the Windows Start menu and launch QuickBooks Database Server Manager.
2. Click the Scan Folders tab.
3. If your company folder is not listed, click Add Folder and select the directory containing your .QBW file.
4. Click Scan.
5. Once the scan completes, verify that the company file appears in the lower pane with active status.
6. Open QuickBooks on a workstation and attempt to open the company file over the network.

Step 3: Run QuickBooks File Doctor via QuickBooks Tool Hub

If manual renaming and rescanning fail, automated diagnostic tools will repair folder permissions and network ports.

1. Download and install the latest QuickBooks Tool Hub on the computer encountering the error.
2. Open the Tool Hub and select Company File Issues from the sidebar.
3. Click Run QuickBooks File Doctor.
4. Select your company file from the drop-down menu (or click Browse to find it).
5. Select Check your file and network, then enter your QuickBooks Administrator login when prompted.
6. Allow the tool 5 to 10 minutes to diagnose and repair network socket bindings and folder permissions.

Step 4: Test the Company File Locally

If Error 6000, -305 persists on a networked file, test whether the issue is isolated to network permissions or exists inside the .QBW file structure.

1. Copy the [YourCompanyName].qbw file from the network folder and paste it onto your local computer’s Desktop.
2. Open QuickBooks Desktop, hold down the Ctrl key until the No Company Open screen appears, and select Open or Restore an Existing Company.
3. Browse to your Desktop and select the copied .QBW file.
4. If the file opens on the desktop: The issue is caused by Windows folder sharing permissions or firewall rules on the server. For server permission repair.
5. If the file still fails to open locally: The primary .QBW database structure requires data verification and rebuild procedures.

Hard Stop: When to Escalate

If renaming the support files and running File Doctor fails to open the company file locally, you may be facing internal database corruption rather than simple support file damage. Stop troubleshooting and consider advanced recovery if:

• The local file test in Step 4 fails with an unrecoverable error code.
• The company file size has dropped to 0 KB or appears corrupted after an abrupt power outage.
• Running the Verify Data utility reports unfixable B-tree index errors in the transaction tables.

Closing the Books

QuickBooks Error 6000, -305 is almost always a temporary communication barrier caused by damaged auxiliary files rather than permanent damage to your financial ledger. By renaming the .ND and .TLG files and refreshing your database scan, you allow QuickBooks to rebuild its connection framework cleanly, returning your accounting workflow to normal without risk to your balances.