QuickBooks Error 6000, -305: How to Repair Damaged Support and Log Files

QuickBooks Error 6000, -305 occurs when QuickBooks Desktop attempts to open your company file but fails because the accompanying support files—specifically the Transaction Log (.TLG) or Network Data (.ND) files—are damaged, out of sync, or locked. These secondary support files coordinate database transactions and multi-user access between your workstation and the database manager. You can fix Error 6000, -305 quickly by renaming the corrupted .ND and .TLG support files, allowing QuickBooks and the Database Server Manager to regenerate fresh, error-free versions.

Fast-Fix: The 45-Second Solution

To resolve QuickBooks Error 6000, -305, close QuickBooks on all computers and open the folder containing your company file. Locate the two files sharing your company file’s exact name but ending with the extensions .ND and .TLG (e.g., MyCompany.qbw.nd and MyCompany.qbw.tlg). Right-click each file and rename them to .ND.old and .TLG.old. Reopen QuickBooks and log in to your file; the application will automatically recreate clean, healthy support files.

---

Quick Status & Triage Snapshot

• Error Code: 6000, -305 (Belongs to the 6000 series company file access family).
• Data Risk Tier: Low. The primary .QBW database file is typically healthy; the failure resides within the secondary communication and recovery logs.
• Multi-User Impact: High. Error 6000, -305 locks the company file, preventing all workstations from opening it until the support files are refreshed.
• Estimated Repair Time: 5 to 10 minutes.

---

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

To understand why Error 6000, -305 occurs, it helps to understand how QuickBooks uses secondary support files:

1. The Network Data (.ND) File: The .ND file is a plain configuration file created by the QuickBooks Database Server Manager. It contains the server’s IP address, hosting port number, network protocol flags, and the database engine version. If the IP address of the server changes or the file is marked read-only, QuickBooks cannot establish a network connection to the database engine and halts with a 6000-series error.
2. The Transaction Log (.TLG) File: The .TLG file records every transaction entered into the company file since the last full manual backup. It serves as an interim recovery log to restore data if the main .QBW file unexpectedly crashes. If the .TLG file size expands out of proportion, suffers bad sectors, or becomes desynchronized from the .QBW transaction table header, QuickBooks rejects the file to prevent database inconsistency.

When either file becomes corrupted, the software throws Error 6000, -305, signaling that it cannot reconcile database communication parameters with the companion support logs.

---

Is Your Data at Risk?

Because Error 6000, -305 targets secondary support files rather than the core ledger tables, your underlying accounting data is safe. Renaming the .ND file carries zero risk; QuickBooks simply creates a new one during its next network query.

Renaming the .TLG file resets the interim transaction log back to zero, but leaves all historical entries inside your .QBW file completely intact. The only data that would ever depend on a .TLG file is unsaved transactional state data during a severe database restore operation.

---

Diagnostic Flowchart: Error 6000, -305 Decision Path

Start: Error 6000, -305 appears when selecting company file
 │
 ├──> Are other users actively logged into the company file?
 │     ├── YES ──> Have all users exit QuickBooks. File locks cause support file access errors.
 │     └── NO  ──> Proceed to file modification.
 │
 ├──> Open company file directory in Windows File Explorer
 │     ├── Are file extensions (.ND and .TLG) visible?
 │     │     ├── NO  ──> Enable "File name extensions" in Windows Explorer View settings.
 │     │     └── YES ──> Rename files to .ND.old and .TLG.old.
 │
 ├──> Attempt to open the company file on the host server
 │     ├── File opens successfully?
 │     │     ├── YES ──> Open QuickBooks Database Server Manager and rescan directory.
 │     │     └── NO  ──> Run QuickBooks File Doctor to repair primary database damage.
 │
 └──> Test access from client workstations.

---

Step-by-Step Repair Guide

Follow these steps directly on the computer or server where the company file is physically stored.

Step 1: Terminate Lingering Database Services

Before you can rename locked support files, you must release all active file handles.

1. Ensure all users across your network close QuickBooks Desktop.
2. On the server or host computer, press Ctrl + Shift + Esc to open Task Manager.
3. Go to the Details tab.
4. Locate any running instances of:
   • qbw32.exe
   • qbupdate.exe
   • qbdbmgrn.exe
5. Highlight each process and click End process.

Step 2: Make File Extensions Visible in Windows

If Windows is set to hide known extensions, you might rename files incorrectly (e.g., creating file.nd.nd).

1. Open File Explorer (Windows Key + E).
2. Click the View tab in the top navigation ribbon.
3. In Windows 11, click Show, then check File name extensions. In Windows 10, simply check the box labeled File name extensions in the View ribbon.

Step 3: Rename the .ND and .TLG Files

Renaming these files clears the corrupted support data and prompts the database engine to build fresh files.

1. Browse to the folder holding your company file (for example, C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
2. Find the file with your company’s name ending in .ND (e.g., CompanyFileName.qbw.nd).
3. Right-click the file, select Rename, and append .old to the extension (e.g., CompanyFileName.qbw.nd.old).
4. Find the matching transaction log file ending in .TLG (e.g., CompanyFileName.qbw.tlg).
5. Right-click the file, select Rename, and change it to CompanyFileName.qbw.tlg.old.
6. Leave the primary database file (CompanyFileName.qbw) completely unchanged.

For an exhaustive breakdown of the renaming procedure across various operating systems, see our dedicated guide on Manual Fix: Renaming .ND and .TLG Files to Resolve 6000-Series Errors.

Step 4: Rescan the Directory with Database Server Manager

If your company file is hosted on a network server for multi-user access, you must force the Database Server Manager to create a new .ND file containing current hosting configurations.

1. Click the Windows Start menu on your host server.
2. Type QuickBooks Database Server Manager and launch the application.
3. Click the Scan Folders tab.
4. If your company file directory is already listed, highlight it and click Scan. If not, click Add Folder, select your company directory, and click Scan.
5. Once the scan completes and confirms status as “OK”, close the tool.
6. Open your company folder in File Explorer; you will see a newly generated .ND file alongside your .QBW file.

Step 5: Open the File and Truncate the Transaction Log

1. Launch QuickBooks Desktop on the host computer or workstation.
2. Open your company file and log in with your administrative credentials.
3. Once the dashboard loads, QuickBooks automatically generates a fresh .TLG file.
4. To permanently stabilize the new support files, run a full verification backup:
   • Go to File > Back Up Company > Create Local Backup.
   • Select Options, ensure Complete verification is checked, and complete the backup save.
   • Performing a verified backup resets the transaction log clean state.

---

Differential Diagnosis: Error 6000, -305 vs. Related Codes

• Error 6000, -305 vs. QuickBooks Error 6190 & 816: Resolving Transaction Log & Company File Mismatch: Error 6190, -816 occurs when the transaction log file was updated by a newer version of the company file or another machine, creating an active mismatch. Error 6000, -305 indicates physical support file damage or internal read parsing failures.
• Error 6000, -305 vs. QuickBooks Error 6000, -80: How to Fix Data Damage in Your Company File: Error 6000, -80 signifies structural table damage inside the core .QBW database itself. If Error 6000, -305 reappears immediately after replacing .ND and .TLG files, the underlying database contains structural table damage.
• Managing Oversized Transaction Logs: If your .TLG file routinely swells to tens of gigabytes, causing 6000-series errors to return periodically, follow our maintenance guide on .TLG File Fix: How to Truncate Transaction Logs to Boost Performance.

---

Hard Stop: When to Escalate to QuickBooks File Doctor

If you have renamed both the .ND and .TLG files, rescanned the host folder with Database Server Manager, verified folder permissions, and the system still generates Error 6000, -305 upon opening, the primary .QBW company file itself has suffered physical corruption in its header blocks.

Do not attempt manual edits to database tables using third-party tools. Run the integrated repair suite by following The 6000 Series Master Fix: Troubleshooting with QuickBooks File Doctor. If the File Doctor reports that it cannot repair the company file, restore your most recent verified backup (.QBB) or escalate the database to professional data recovery services.