How to Resolve QuickBooks Error 6073 99001: A Complete Guide

QuickBooks Error 6073 99001 is a common multi‑user error that prevents users from opening a company file when someone else has locked it. If you’ve encountered this error, you’ve likely been greeted with a message such as: The disruptive nature of this error can interrupt work and cause significant delays. In this article, you’ll find everything you need to resolve it—from understanding the root causes to following detailed troubleshooting steps and taking measures for prevention. Let’s dive in.

1. What Is QuickBooks Error 6073 99001?

Error 6073 99001 typically pops up in a multi‑user network when QuickBooks Desktop attempts to open a company file (.QBW) but finds it is already in use or locked. It may display variants like:

• Error code 6073 99001

• Error opening company file – Another user is using it

• Couldn’t open company file; only one QuickBooks user is allowed

In essence, it prevents any additional users from accessing the company file—to protect data integrity when the file is actively in use or has not been properly closed.

2. Common Causes of Error 6073 99001

Identifying the root can help prevent recurrence. Here are common triggers:

1. A user still accessing the file
   Someone may have the file open—perhaps locked in the background or via an Auto Recovery prompt.

2. Corrupted network configuration
   Damaged .ND (Network Data) or .TLG (Transaction Log) files could be blocking the file.

3. Issue with the server or host machine
   The server or hosting workstation’s QuickBooks Database Server Manager may not be running.

4. Insufficient folder or file permissions
   Inadequate read/write rights to the shared folder where your company file resides.

5. The file was opened on a local drive
   Attempted access from a server-hosted file but QuickBooks sees it locally.

6. Incorrect firewall or DNS settings
   Network traffic may be blocked or rerouted due to security settings.

3. How to Resolve QuickBooks Error 6073 99001

Let’s break down each step in detail.

A. Switch to Single‑User Mode

First action on a network: check if someone is actively using the file.

1. From the hosting computer, open QuickBooks Desktop.

2. Go to File → Switch to Single‑User Mode.

3. If prompted, ask the user to close the file.

4. When successful, switch back to Multi‑User Mode and have others attempt to open it.

If this works, the problem was simply a locked session.

B. Restart Server & Workstations

Network glitches or hung processes often cause locks that persist unseen.

• Reboot the server/host computer running QuickBooks Database Server Manager.

• Restart each workstation that accesses QuickBooks.

• Reattempt opening the company file.

Often, this simple step removes hidden session locks.

C. Verify Folder Permissions

QuickBooks requires specific permissions to access shared folders:

1. Go to the folder holding the .QBW file.

2. Right-click → Properties → Security tab.

3. Ensure Read, Write, Modify, and Full Control are granted for:

   • All QuickBooks users

   • The NETWORK SERVICE and ALL APPLICATION PACKAGES groups

4. Apply settings recursively to all subfolders.

5. Users should then attempt to open the file again.

Without proper permissions, QuickBooks can’t create or access network lock files.

D. Rename .ND and .TLG Files

These small support files help QuickBooks track database connections. Corruption here can cause errors.

1. Locate the folder with your .QBW company file.

2. Look for:

   • <YourCompanyName>.nd

   • <YourCompanyName>.tlg

3. Right-click and rename them:

   • .nd → .nd.old

   • .tlg → .tlg.old

4. Open QuickBooks on the hosting system; it will rebuild these files.

5. Try again in multi‑user mode.

If corrupted .ND was the issue, QuickBooks replaces it and restores access.

E. Copy File Locally

If network issues persist, temporarily move your company file:

1. Copy the .QBW to a local drive on any machine.

2. Open QuickBooks and access the file locally.

3. If it opens, the error is network-related.

4. Close QuickBooks and return the file to the shared folder.

5. Open in multi‑user mode to test.

This isolates whether the file or network is at fault.

F. Run QuickBooks File Doctor

QuickBooks includes a diagnostic tool to repair data and network issues:

1. Open QuickBooks Tool Hub (download from Intuit if needed).

2. Navigate to Company File Issues → Run QuickBooks File Doctor.

3. When prompted, do:

   • Select company file

   • Click Check your file

   • Enter QuickBooks admin credentials

   • Start the scan

Let it detect and repair network/file issues. Once complete, retry opening the company file.

4. Prevention Tips & Best Practices {#prevention}

Following these proactive steps can help avoid Error 6073 99001 in the future:

• Close all sessions fully: Ensure users properly exit QuickBooks (not just minimize or lock).

• Update regularly: Keep QuickBooks, Windows, and server software on latest versions.

• Scheduled backups: Backup your company files daily and archive logs once a week.

• Maintain network health:

  • Use reliable wired connections rather than Wi‑Fi for servers.

  • Disable aggressive antivirus or firewall rules blocking QuickBooks ports.

• Permission audits: Check folder permissions monthly and add new users appropriately.

• Use File Doctor proactively: Run it periodically to catch corruption early.

• Limit admin sessions: Host QuickBooks Database Server Manager only on a designated server.

• Train users: Educate staff to exit correctly and recognize Auto Recovery dialogs.

5. When to Contact Support {#support}

If the error persists after all steps, escalate to:

• Your network or IT support
  For diagnostics on DNS, connectivity, or server-side logs that you may not have access to.

• QuickBooks Support
  Contacted via:

  • QuickBooks Help menu → Contact Support

  • Intuit’s website – chat or call

  • Provide detailed info:

    • Exact error message

    • Steps already tried

    • QuickBooks version & year (e.g., v2023, release R7)

    • Hosting setup (Windows Server version, peer-to-peer, mapped drives)

Advanced scenarios where QuickBooks specialists may help include:

• File-level corruption beyond File Doctor’s fix

• Complicated multi-site network environments

• Migrating company file to a hosted or cloud server

• Rebuild and restore processes if the file itself is damaged (keeping backup first)

6. Conclusion

QuickBooks Error 6073 99001 is often network-related—caused by locked sessions, corrupted support files, or permission gaps. In most cases, it can be resolved with:

1. Switching to single-user mode

2. Restarting involved systems

3. Adjusting folder permissions

4. Renaming .ND and .TLG

5. Copying the file locally

6. Running the File Doctor tool

By applying these solutions methodically, most users eliminate the error and restore multi‑user access. Regular maintenance—such as updating software, checking permissions, training staff, and running File Doctor—can help prevent it.

If these steps fail or the situation is complex, QuickBooks Support and IT professionals are your next best resource. With the right combination of troubleshooting and preventive action, your team can keep QuickBooks running smoothly and collaboratively.

Frequently Asked Questions

Q1: Can I fix QuickBooks Error 6073 99001 without IT help?
Yes, many users can resolve this error by following basic troubleshooting steps such as switching to single‑user mode, renaming .ND and .TLG files, and checking folder permissions. However, if these steps don’t work, assistance from an IT professional or QuickBooks Support may be necessary for network or file corruption issues.

Q2: What causes the .ND and .TLG files to get corrupted?
.ND and .TLG files can become corrupted due to abrupt shutdowns, improper file closing, network interruptions, or malware infections. These files help QuickBooks manage multi‑user access, so damage to them can prevent the company file from opening properly.

Q3: Is it safe to rename or delete .ND and .TLG files?
Yes, it is safe to rename or delete these files. QuickBooks automatically rebuilds new .ND and .TLG files when you reopen your company file. This process often fixes errors related to these files without affecting your actual financial data stored in the .QBW file.