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

September 21, 2026 6 min read

QuickBooks Error 6000, -305 occurs when QuickBooks Desktop attempts to open your company file but cannot read or synchronize with its accompanying Network Data (.nd) or Transaction Log (.tlg) files. When these auxiliary files become corrupted, locked by background processes, or out of sync with the primary .qbw database, QuickBooks halts file access to prevent data divergence.

Fast-Fix: The 45-Second Solution

To resolve Error 6000, -305 immediately, close QuickBooks on all computers, navigate to the folder hosting your company file, and rename both the .ND and .TLG files by appending .old to their extensions (e.g., MyCompany.qbw.nd.old). Next, open the QuickBooks Database Server Manager on the host machine and run a folder scan. QuickBooks will automatically recreate clean configuration and log files when you reopen the file.

Quick Status & Triage Snapshot

Data Risk Tier: Low. The primary company database (.qbw) is rarely damaged when this code appears.
Multi-User Impact: High. Workstations will be locked out of the company file until the hosting metadata files are regenerated.
Common Trigger: Abrupt server reboots, network drops during an active write cycle, or third-party backup utilities locking files during operations.
Estimated Fix Time: 5 to 10 minutes.

Diagnostic Flowchart: 6000, -305 Decision Path

[Start: Error 6000, -305 Displays]
          │
          ▼
Are all users completely out of QuickBooks?
  ├── No  ──> Close QuickBooks on all workstations via Task Manager (kill QBW32.exe).
  └── Yes ──> Continue.
          │
          ▼
Is the company file stored locally or on a dedicated server?
  ├── Dedicated Server ──> Rename .ND/.TLG on the Server, then run Database Server Manager Scan.
  └── Local Drive (C:) ──> Rename .ND/.TLG locally, open QuickBooks directly.
          │
          ▼
Does the file open successfully?
  ├── Yes ──> Issue resolved (Run a manual backup immediately to reset the new .TLG file).
  └── No  ──> Check for third-party file locks or folder permission restrictions.

Is Your Data at Risk?

The appearance of Error 6000, -305 usually looks more dangerous than it is. The .tlg (Transaction Log) file keeps track of changes made to the database since your last full backup, while the .nd (Network Data) file is a plain-text configuration file that tells the QuickBooks Database Server Manager what network ports to use.

If the error appeared during normal login or opening: Your financial records are almost certainly intact. The software simply cannot parse the handshake instructions.
If the error appeared immediately following an ungraceful shutdown during a transaction save or rebuild: There is a slight chance the transaction log desynchronized midway through writing. If you need to dive into log anomalies later, check Log Analysis: How to Find and Fix “LVL_ERROR” in the QBWin.log.

Technical Anatomy: What This Error Means

When QuickBooks Desktop opens a company file (CompanyFile.qbw), it initiates a handshake with the QuickBooks Database Server Manager engine (dbmgr.exe / qbcfmonitorservice.exe). For this handshake to work:

The .nd file provides the IP address, port number, and hosting status of the server.
The .tlg file establishes the transactional delta between the last verified state of the database and current pending transactions.

Error -305 triggers when the transaction log header or network pointer contains conflicting bytes or unreadable characters. Because QuickBooks cannot verify if transactions were missed or partially written, it blocks database connection routines rather than risking database divergence.

Differential Diagnosis: Don’t Confuse This With…

QuickBooks Error 6000, -83: Indicates that QuickBooks cannot access the host computer due to network configurations or permissions, rather than a corrupt support file. If your network configuration is the culprit, see QuickBooks Error 6000, -83: Fixing Host Computer Configuration Errors.
QuickBooks Error 6190, -816: Occurs when the .qbw file and the .tlg file mismatch because one was restored without the other. See QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies.
QuickBooks Error 6000, -77: Points specifically to an invalid or unsupported folder path (such as trying to open a file stored on a cloud sync folder or external media). See Fix QuickBooks Error 6000, -77: Incorrect Company File Path.

Step-by-Step Repair Guide

Follow these sequential steps on the machine that physically stores the company file.

Step 1: Terminate All Hanging QuickBooks Processes

Before working with support files, ensure no orphaned network connections exist:

Press Ctrl + Shift + Esc on the host server to open Task Manager.
Go to the Details tab.
Locate and end the following processes if running:
- QBW32.exe
- QBDBMgr.exe
- QBDBMgrN.exe
- QBCFMonitorService.exe

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

Open Windows File Explorer and navigate to the directory holding your company file (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
Search for the files sharing your company file’s exact name with the extensions .nd and .tlg:
- [YourCompanyFileName].qbw.nd
- [YourCompanyFileName].qbw.tlg
Right-click [YourCompanyFileName].qbw.nd, select Rename, and add .old to the very end:
- [YourCompanyFileName].qbw.nd.old
Right-click [YourCompanyFileName].qbw.tlg, select Rename, and add .old:
- [YourCompanyFileName].qbw.tlg.old(Note: If file extensions are hidden, enable them under Windows File Explorer by clicking View > checking File name extensions).

For a deeper dive into how QuickBooks handles these files during recovery, refer to Support Files: The Role of .ND and .TLG Files in QuickBooks Recovery.

Step 3: Rescan Using QuickBooks Database Server Manager

If your file is hosted over a network, you must force QuickBooks to rebuild the .nd file with correct network parameters:

Press the Windows Key, type QuickBooks Database Server Manager, and open the utility.
Select the Scan Folders tab.
Click Browse and select the folder where the company file resides.
Click Start Scan.
Once the scan completes and displays the file in the lower window, open QuickBooks on the hosting machine, then launch it from the workstation.

If the utility fails to start or complete the scan, consult QuickBooks Error 6175: Fix: QuickBooks Unable to Start Database Server.

Hard Stop: When to Call an Expert

Stop troubleshooting and seek advanced data recovery if you observe any of the following:

Renaming the .tlg file results in QuickBooks prompting: “The transaction log file is damaged or missing and must be repaired before opening.”
The .qbw file size has shrunk to 0 KB or drastically reduced in size unexpectedly.
You experience repeated blue screens (BSOD) or disk I/O errors while attempting to rename the files, which points to physical drive degradation.

Closing the Books

Encountering a 6000-series error can disrupt your workflow, but Error 6000, -305 is fundamentally a support-file desynchronization issue rather than core data corruption. Once you isolate the damaged auxiliary files and allow the Database Server Manager to regenerate fresh pointers, your accounting data will load smoothly. Perform a standard scheduled backup shortly after regaining access to initialize your new transaction log file cleanly.

QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies

October 2, 2026

QuickBooks Error 6176: Troubleshooting Firewall Blocks on Company File Paths

October 1, 2026

QuickBooks Error 6189, 816: Fix “Company File is Already in Use”