Why Does QuickBooks Keep Showing Error 6073 99001 When I Open My File?

If you've just tried to open your company file and got stuck staring at "Error -6073, -99001," you're not alone, and it doesn't mean your books are broken. This is one of the more common QuickBooks error codes 6073 99001 issues, and it almost always comes down to how QuickBooks is trying to access the file — not a problem with your actual financial data.

That distinction matters. A lot of people panic and assume they've lost data or corrupted their books. In reality, this error is QuickBooks telling you it can't get the kind of access it needs (exclusive or multi-user) to open the file right now. Something else — a leftover process, a network hiccup, a permissions issue, or another computer on the network — is standing in the way.

QuickBooks error codes 6073 99001 appear when QuickBooks Desktop cannot get exclusive or shared access to your company file because another process — often QuickBooks itself, a background service, or another user on the network — already has the file open or locked. It's a file-access conflict, not data corruption. In most cases, closing all open instances of QuickBooks, checking who else is logged into the company file, and restarting the QuickBooks database service resolves it. If that doesn't work, the QuickBooks File Doctor or a manual hosting/network fix usually clears it.

What Is QuickBooks Error 6073 99001, Really?

QuickBooks error code 6073 99001 is a file access error, not a data error. It shows up when:

  1. QuickBooks can't open the company file because it's already open elsewhere

  2. The file is hosted on a network and there's a conflict with how it's being shared

  3. A background QuickBooks process (like the QuickBooksDBXX service) is stuck or hasn't released the file

  4. Multiple users are trying to access the file in a way the current hosting setup doesn't support

You'll typically see this error in a multi-user network environment, though it can also happen on a single computer if QuickBooks didn't shut down properly the last time you used it.

What Causes QuickBooks Desktop Error Code 6073?

The root causes generally fall into a few buckets:

  1. File already in use — Someone (including you, in a previous session) has the company file open, and QuickBooks hasn't released the lock.

  2. QuickBooks Database Server Manager issues — The service that manages multi-user access has stopped, crashed, or isn't configured correctly.

  3. Incorrect hosting settings — More than one computer is set to "host multi-user access," which confuses QuickBooks about who's actually in charge of the file.

  4. Windows or network permission problems — The folder containing your company file doesn't have the right permissions set for QuickBooks to read/write to it.

  5. Firewall or antivirus interference — Security software blocking the ports QuickBooks uses to communicate across the network.

  6. Leftover .ND or .TLG files — Damaged or outdated network descriptor files that confuse QuickBooks about the file's location or status.

None of these mean your company file itself is corrupted — that's the reassuring part. It's almost always about access, not data integrity.

Step-by-Step Solution to Fix Error 6073 99001

Work through these in order. Most people resolve the issue within the first three or four steps.

Step 1: Close QuickBooks Completely on Every Computer

Before anything else, make sure QuickBooks isn't running anywhere — including on the server or host computer.

  1. Close QuickBooks on your own machine.

  2. Ask anyone else on the network to close it too.

  3. Open Task Manager (Ctrl + Shift + Esc on Windows) and check the "Processes" tab for QBW32.exe or QBW.exe. If it's still listed after closing the program, end the task manually.

Step 2: Restart the QuickBooks Database Server Manager

The database service is what allows multiple users to share a company file. If it's frozen or stopped, you'll get access errors.

  1. On the computer hosting the file, open the Services app (search "Services" in the Windows Start menu).

  2. Find QuickBooksDBXX (the XX matches your QuickBooks year, like QuickBooksDB24).

  3. Right-click and select Restart. If it's not running, select Start.

  4. Try reopening your company file.

Step 3: Check Who Has Multi-User Hosting Turned On

Only one computer on your network should have multi-user hosting enabled — usually the server or the computer where the company file physically lives.

  1. On each workstation, go to File > Utilities.

  2. If you see "Stop Hosting Multi-User Access," that computer currently has hosting on. If it's not meant to be the host, click it to turn hosting off.

  3. On the correct host computer, you should see "Host Multi-User Access." Make sure it's active there.

Step 4: Use QuickBooks File Doctor

QuickBooks includes a diagnostic tool called QuickBooks Tool Hub, which contains the File Doctor utility.

  1. Download and install QuickBooks Tool Hub from Intuit's official site if you don't already have it.

  2. Open Tool Hub and select Company File Issues.

  3. Run QuickBooks File Doctor and choose your company file.

  4. Select "Check your file and network" and let it scan.

This tool checks network setup, file permissions, and connectivity in one pass, which covers several of the root causes at once.

Step 5: Check .ND and .TLG Files

Every company file has an accompanying .ND (Network Descriptor) file that tells QuickBooks how to find it on the network. If this file is outdated or damaged, it can trigger access errors.

  1. Go to the folder where your company file is stored.

  2. Look for a file with the same name as your company file but ending in .ND.

  3. Rename it (add "OLD" to the end) rather than deleting it — this forces QuickBooks to rebuild it.

  4. Reopen QuickBooks and try accessing the file again; it will recreate the .ND file automatically.

Step 6: Review Firewall and Antivirus Settings

QuickBooks uses specific ports to communicate across a network (commonly 8019, and a range between 56726–56728, though this varies by version). If your firewall or antivirus is blocking these:

  1. Use the QuickBooks Tool Hub's "Network Issues" section, which includes a firewall port checker.

  2. Temporarily disable third-party antivirus to test whether it's the source (re-enable it afterward and add QuickBooks as an exception instead of leaving it off).

Step 7: Confirm Folder Permissions

The Windows folder containing your company file needs full read/write permissions for the Windows user account running QuickBooks.

  1. Right-click the folder > Properties > Security.

  2. Make sure the relevant user accounts have "Full Control."

  3. Apply changes and restart QuickBooks.

If you've gone through all seven steps and the error persists, that's usually a sign of a more specific network configuration issue that benefits from a closer look at your particular setup — at that point, Intuit's official support resources (through the in-product Help menu or quickbooks.intuit.com/support) can walk through your environment directly. If you'd rather talk it through with someone, you can also reach a support line at 1-866-513-4656.

Common Mistakes People Make With This Error

Understanding these mistakes can save you a lot of wasted time:

  1. Turning on hosting on multiple computers. This is one of the most frequent causes of 6073 99001. Only the host machine should have multi-user access enabled.

  2. Deleting the .ND file instead of renaming it. Renaming lets QuickBooks safely rebuild it; deleting can sometimes cause confusion if QuickBooks expects a specific file structure.

  3. Ignoring background processes. Closing the QuickBooks window doesn't always end the process. Always check Task Manager.

  4. Restarting the computer instead of the QuickBooks service first. A full restart works, but it's often unnecessary — restarting just the database service is faster and usually enough.

  5. Assuming the company file is corrupted. This leads people to skip straight to restoring a backup, which isn't needed for a pure access error and can cause you to lose recent work unnecessarily.

  6. Running an outdated version of QuickBooks Desktop. Older releases have known bugs with multi-user access that later updates fixed.

Expert Tips for Avoiding This Error in the Future

  1. Keep QuickBooks Desktop updated. Go to Help > Update QuickBooks Desktop regularly. Many multi-user and network fixes are rolled into updates before they become official "known issues."

  2. Store your company file on the host computer's local drive, not a mapped network drive or cloud-sync folder like Dropbox or OneDrive. Cloud-sync folders can lock files in ways that conflict with QuickBooks' own file-locking system.

  3. Limit hosting to one dedicated machine, ideally one that stays on and connected whenever others need access.

  4. Schedule regular backups so that if you ever do run into real file corruption (a separate issue from this error), you have a recent, clean copy to fall back on.

  5. Document your network setup — which computer hosts the file, which ports are open, which folder the file lives in — so troubleshooting is faster next time.

These habits also help prevent related network errors, including the ones covered in these walkthroughs: QuickBooks Company File Not Found, How to Fix QuickBooks Error H202, and How to Fix QuickBooks Error PS038 — all of which stem from similar multi-user and network-configuration issues.

Frequently Asked Questions

What is QuickBooks errors 6073 and 99001?

It's a combined error code that appears when QuickBooks Desktop can't access the company file because it's already open, locked, or blocked by a network or hosting conflict. It doesn't indicate data corruption.

What causes QuickBooks Desktop error code 6073?

The most common causes are the company file being open on another computer, incorrect multi-user hosting settings, a stalled QuickBooks database service, firewall interference, or outdated .ND network files.

What is the error code -6073 -99001?

This is the same error, just displayed with negative signs as QuickBooks sometimes formats its error codes. It refers to the identical file-access conflict described above.

Can I fix error 6073 99001 without calling anyone?

Yes, in most cases. Restarting the QuickBooks Database Server Manager, correcting hosting settings, and renaming the .ND file resolve it for the majority of users without needing outside help.

Does this error mean I lost my QuickBooks data?

No. This is an access error, not a corruption error. Your data is very likely intact; QuickBooks simply can't open a connection to it at that moment.

Why does this error only happen on some computers and not others?

It usually happens on whichever computer is trying to access the file when hosting settings are misconfigured, or when that specific machine has a firewall rule blocking QuickBooks' network ports.

Should I restore a backup to fix this error?

No, not for this specific error. Restoring a backup is meant for actual data corruption. Since 6073 99001 is an access issue, restoring a backup won't fix it and could cause you to lose recent transactions unnecessarily.

Post you may find helpful: How to repair company file with QuickBooks File Doctor

Conclusion

QuickBooks error codes 6073 99001 look alarming, but they're one of the more fixable issues you'll run into with QuickBooks Desktop. In almost every case, it comes down to a file-access conflict — another process holding the file open, a misconfigured hosting setup, or a network/firewall rule getting in the way — rather than any damage to your actual financial records.

Work through the steps in order: close all instances of QuickBooks, restart the database service, confirm only one computer is hosting, run the File Doctor tool, and check your .ND file and folder permissions. For the vast majority of users, one of these steps clears the error and gets the company file open again.

If you've worked through everything here and it's still not resolving, that usually points to a more specific network or Windows configuration detail worth a closer look — Intuit's official support resources are the right next stop for that. Either way, this is a solvable problem, and it doesn't require redoing your books or panicking about lost data.

Write a comment ...

Write a comment ...