Manual Fix: Renaming .ND and .TLG Files to Resolve 6000 Errors

Renaming the .ND (Network Data) and .TLG (Transaction Log) files is the standard manual fix for resolving QuickBooks 6000-series errors, such as 6000 -77, 6000 -80, 6000 -83, and 6190 -816. These auxiliary files store temporary network path configurations and transaction logs. When either file becomes corrupted, desynchronized, or locked, QuickBooks refuses to open the company file (.qbw) to prevent database corruption. Renaming them forces QuickBooks to automatically generate clean, undamaged support files the next time you open your company file.

Fast-Fix: The 45-Second Solution

To resolve 6000-series errors immediately, navigate to the folder storing your .qbw company file, right-click the matching .ND and .TLG files, and rename them with .old appended to each extension. Error 6000 issues are frequently caused by corrupt network configuration data or transaction pointer desynchronization. Renaming these files releases stale locks and forces QuickBooks to regenerate fresh support files when you launch the company file.

Quick Status & Triage Snapshot

• Data Risk Tier: Low. The .ND file contains only network configuration data. The .TLG file holds incremental transaction logs since the last full backup; renaming it does not delete transactions from the main .qbw file.
• Multi-User Impact: High. Workstations are locked out of the company file until the support files are regenerated.
• Common Trigger: Sudden workstation disconnections, server power outages, network drops during save operations, or restoring a .qbw file into a folder that contains an older .TLG file.
• Estimated Fix Time: 3 to 5 minutes.

Diagnostic Flowchart: Renaming .ND & .TLG Decision Path

[Start: 6000-series error appears on open]
   │
   ▼
Close QuickBooks on all workstations and host computer.
   │
   ▼
Open the folder containing the company file (.qbw).
Locate [FileName].qbw.ND and [FileName].qbw.TLG.
   │
   ▼
Are Windows file extensions (.nd and .tlg) visible?
   ├─► No ──► Open Windows Explorer View settings > Check "File name extensions."
   └─► Yes ─► Proceed to rename.
                 │
                 ▼
              Rename files to [FileName].qbw.ND.old and [FileName].qbw.TLG.old.
              Reopen QuickBooks on the host machine.
                 │
                 ▼
              Did the company file open cleanly?
                 ├─► Yes ──► [Resolved: Fresh .ND and .TLG files generated]
                 └─► No ───► Proceed to QuickBooks File Doctor or host checks.

Is Your Data at Risk?

Renaming .ND and .TLG files is a safe, non-destructive diagnostic procedure.

• The .ND file: Contains no financial data. It is a configuration file that tells QuickBooks Database Server Manager what network port and protocol to use.
• The .TLG file: Stores changes made to the database since your last manual backup. Renaming it will not wipe ledger entries; the primary .qbw database retains all committed transactions.

Precautionary Rule: If your database has experienced severe corruption and you plan to work with professional data recovery engineers to recover uncommitted transactions from an interrupted session, make a copy of the .TLG file rather than deleting it. Renaming the file to .old accomplishes this by preserving the original log file while letting QuickBooks create a clean one.

Technical Anatomy: What These Files Do

QuickBooks relies on two companion files to broker database access:

1. The Network Data (.ND) File: A plain-text configuration file containing the server’s IP address, computer name, network port, and local path to the company file. If a network IP changes or a workstation disconnects improperly, the .ND file can retain stale socket information, causing 6000-series errors when a client workstation tries to connect.
2. The Transaction Log (.TLG) File: A companion relational log that acts as a staging buffer between the Sybase database engine and the .qbw database. It keeps track of transactional commits. When the transaction counter inside the .qbw file fails to match the pointer in the .TLG file (often due to an interrupted write operation or an unlinked restore), QuickBooks halts execution with an error like Error 6190, -816 or Error 6000, -80.

When you rename these files, QuickBooks cannot find them and automatically constructs fresh ones matching the exact current state of the .qbw database.

Differential Diagnosis: Don’t Confuse This With…

• QuickBooks Error H202: Occurs when a workstation cannot ping the host server across the local area network due to firewall or DNS blocks, even if the .ND file is properly formed.
• QuickBooks Error 6175, 0: Occurs when the database service (QuickBooksDBXX) is stopped on the server; renaming .ND files will not fix Error 6175 until the service itself is started.
• QuickBooks Error 6155: Indicates that the .qbw file header is physically damaged or has read-only permission locks, which requires running QuickBooks File Doctor rather than solely resetting support files.

Step-by-Step Repair Guide

Follow these steps directly on the computer or server hosting the company file.

Step 1: Ensure All Instances of QuickBooks Are Closed

1. Instruct all users to exit QuickBooks Desktop.
2. On the host computer, press Ctrl + Shift + Esc to open Task Manager.
3. In the Processes tab, look for any remaining instances of QBW32.exe, QBDBMgrN.exe, or QBCFMonitorService.exe.
4. If found, highlight each and click End Task to release lingering file locks.

Step 2: Show Hidden File Extensions in Windows

If file extensions are hidden, you will not be able to locate or change the .ND and .TLG extensions properly.

1. Open File Explorer on the host machine.
2. Click the View tab in the top navigation ribbon.
3. In the Show/hide section, check the box for File name extensions.

Step 3: Rename the .ND and .TLG Files

1. Navigate to the directory containing your company file (default: C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
2. Locate the files with the exact same name as your company file:
   • [YourCompanyName].qbw.ND
   • [YourCompanyName].qbw.TLG
3. Right-click [YourCompanyName].qbw.ND and select Rename.
4. Add .old to the end of the file name:
   [YourCompanyName].qbw.ND.old
5. Right-click [YourCompanyName].qbw.TLG and select Rename.
6. Add .old to the end of the file name:
   [YourCompanyName].qbw.TLG.old
7. Leave the main .qbw file untouched.

Step 4: Reopen the Company File

1. Open QuickBooks Desktop on the host computer.
2. Open the company file (.qbw).
3. QuickBooks will automatically generate new .ND and .TLG files in the directory.
4. Once the file opens on the host, open QuickBooks on client workstations to verify network access.

Step 5: Create a Verified Backup to Reset the Transaction Log

Once access is restored, run a complete backup to re-index the transaction stream:

1. In QuickBooks, go to File > Back Up Company > Create Local Backup.
2. Select Local Backup and click Next.
3. Complete the backup process. This commits all cached transactions and resets the newly generated .TLG file counter cleanly.

Hard Stop: When to Call an Expert

Cease manual file modifications and consult a data recovery professional if:

• Renaming the .ND and .TLG files allows the company file to open, but recent financial transactions or customer records are missing.
• Windows displays an operating system error (“The file or directory is corrupted and unreadable”) when you attempt to rename the files, indicating disk hardware corruption.
• The company file continues to display Error 6000, -80 after generating fresh .ND and .TLG files.

Related Errors

If renaming these files does not resolve your 6000-series error, consult these guides:

• The 6000 Series Errors: Complete Diagnosis & Repair Framework
• The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor
• QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies
• QuickBooks Error 6189, 816: Fix “Company File is Already in Use”
• .TLG Recovery: How to Recover Data from a Damaged Transaction Log File

Closing the Books

Renaming .ND and .TLG files is a fundamental troubleshooting step for QuickBooks 6000-series errors. Because it clears out corrupt pointer references and broken network data without touching your financial tables, it solves the majority of file access issues quickly. After renaming the files and confirming your data opens cleanly, running a quick verified backup will keep your new transaction logs aligned.