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

Renaming .ND and .TLG files is the universal first-line manual repair for the QuickBooks 6000 error series (including Errors 6000 -77, 6000 -80, 6000 -83, 6123, 6189, and 6190). These companion files store network parameters and interim transaction logs. When they become damaged, bloated, or locked by background processes, QuickBooks blocks access to your company file. Renaming them to .old forces QuickBooks and the Database Server Manager to regenerate clean, matching files. This manual procedure resolves the error without damaging your primary accounting data.

Fast-Fix: The 45-Second Solution

To manually fix 6000-series errors, close QuickBooks on all computers and open the company file directory. Locate the two files sharing your exact company file name with the extensions .ND and .TLG (e.g., Company.qbw.nd and Company.qbw.tlg). Right-click each and rename them to Company.qbw.nd.old and Company.qbw.tlg.old. Rescan the folder using QuickBooks Database Server Manager and reopen your company file.

---

Quick Status & Triage Snapshot

• Primary Diagnostic Purpose: Resolving multi-user connection drops, database verification failures, and transaction log desynchronization across the entire 6000-series error family.
• Data Risk Tier: None. Your actual accounting records, invoices, and customer balances are stored exclusively inside the .QBW file.
• Affected Errors: 6000 -77, 6000 -80, 6000 -83, 6000 -305, 6123, 6144, 6177, 6189, and 6190.
• Estimated Execution Time: 3 to 5 minutes.

---

What Are .ND and .TLG Files? (And Is It Safe to Rename Them?)

Many QuickBooks administrators hesitate to touch files in the company directory out of concern for data loss. Understanding what these files do clarifies why renaming them is completely safe.

The Role of the .ND (Network Data) File

The .ND file is a plain configuration file created by the QuickBooks Database Server Manager. It contains:

• The host server’s IP address and computer name.
• The dynamic TCP port assigned to the database engine.
• The path to the company file.
• Whether the file is configured for Multi-User or Single-User hosting.

QuickBooks reads this file across the network to find the database engine. If your server rebooted, received a new DHCP IP address, or experienced network drops, the .ND file becomes outdated. Renaming it forces the server to create a fresh file with current network settings.

The Role of the .TLG (Transaction Log) File

The .TLG file is an interim transaction buffer used by the database engine:

• It records transactions entered into the system between backups.
• When you create a verified local backup (.QBB), QuickBooks commits all log transactions into the .QBW file and resets the .TLG file to near zero bytes.
• If the .TLG file swells to gigabytes in size or becomes out of sync with the .QBW file, the database engine blocks access to prevent writing to a damaged log stream.

Renaming the .TLG file resets the transaction log without removing any recorded transactions from your company file.

---

Diagnostic Flowchart: Support File Repair Workflow

Start: 6000-series error appears on workstation or server
 │
 ├──> Close QuickBooks Desktop on all network computers
 │     └── Open Task Manager to ensure qbw32.exe is not running in background.
 │
 ├──> Open company file directory in Windows File Explorer
 │     ├── Enable "File name extensions" under View menu.
 │     ├── Rename CompanyName.qbw.nd to CompanyName.qbw.nd.old.
 │     └── Rename CompanyName.qbw.tlg to CompanyName.qbw.tlg.old.
 │
 ├──> Multi-User Network Setup?
 │     ├── YES ──> Open Database Server Manager on server and rescan folder.
 │     └── NO  ──> Launch QuickBooks and open the .QBW file directly.
 │
 └──> File opens successfully?
       ├── YES ──> Perform full verified backup to truncate new log file.
       └── NO  ──> Issue is deeper than support files; run QuickBooks File Doctor.

---

Step-by-Step Guide: How to Manually Rename .ND and .TLG Files

Perform this procedure on the computer or server where the company file physically resides.

Step 1: Close QuickBooks and Terminate Background Services

Before Windows allows you to rename support files, all file locks must be released.

1. Ensure every user on your local network exits QuickBooks Desktop.
2. Press Ctrl + Shift + Esc to open Task Manager.
3. Go to the Details tab, locate any instances of qbw32.exe or qbupdate.exe, right-click them, and select End task.

Step 2: Show File Name Extensions in Windows

By default, Windows hides file extensions, which can cause you to accidentally rename files to Company.qbw.nd.nd.

1. Press Windows Key + E to open File Explorer.
2. In Windows 11: Click View in the top ribbon, select Show, and verify that File name extensions has a checkmark next to it.
3. In Windows 10: Click the View tab in the ribbon and check the box for File name extensions.

Step 3: Locate and Rename the Support Files to .old

1. Navigate to the folder hosting your company file (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
2. Locate the two files with your company name ending in .nd and .tlg:
   • YourCompanyFile.qbw.nd
   • YourCompanyFile.qbw.tlg
3. Right-click YourCompanyFile.qbw.nd, click Rename, and append .old to the end:
   YourCompanyFile.qbw.nd.old
4. Right-click YourCompanyFile.qbw.tlg, click Rename, and append .old to the end:
   YourCompanyFile.qbw.tlg.old
5. Leave YourCompanyFile.qbw untouched.

Step 4: Rescan the Directory with Database Server Manager

If you use QuickBooks in Multi-User Mode across an office network, rescan the directory to regenerate the .ND file immediately:

1. Click the Windows Start menu on your host server.
2. Search for QuickBooks Database Server Manager and open it.
3. Click the Scan Folders tab.
4. Click Add Folder, select your company file folder, and click Scan.
5. Once the scan reports “OK”, close the tool.

Step 5: Launch QuickBooks and Rebuild the Database Cache

1. Launch QuickBooks Desktop on your computer.
2. Open the .QBW company file.
3. QuickBooks will automatically generate a clean, synchronized .TLG file.
4. Create a verified backup (File > Back Up Company > Create Local Backup) to truncate the newly created transaction log and verify full table integrity.

For ongoing management of transaction log file sizes, review .TLG File Fix: How to Truncate Transaction Logs to Boost Performance.

---

Differential Diagnosis: Which 6000-Series Errors Does This Fix?

Renaming .ND and .TLG files directly resolves the following error codes:

• **QuickBooks Error 6189, 816: How to Fix “Company File is Already in Use”:** Clears stale file-lock tokens left behind by crashed client sessions.
• **QuickBooks Error 6190 & 816: Resolving Transaction Log & Company File Mismatch:** Replaces an out-of-sync transaction log with a clean file matching the database checkpoint.
• **QuickBooks Error 6000, -83: Expert Guide to Host Configuration & Setup Errors:** Resolves IP address and network path routing failures between workstations and the host server.

---

Hard Stop: When Support File Renaming Isn’t Enough

If you rename the .ND and .TLG files, rescan the directory, and still encounter a 6000-series error when opening the file, the issue is not caused by support files.

You are dealing with either Windows folder permission restrictions or internal database corruption within the .QBW file itself. Move directly to The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor to repair internal database tables, network firewall rules, and folder permissions.