How to Fix QuickBooks Error 6073 (and 99001): Multi-User Recovery Guide

QuickBooks Desktop relies on real-time database locks to ensure that multiple team members can enter bills, process invoices, and manage payroll simultaneously without corrupting the general ledger. However, when those database locks fail to release, or when file permissions fall out of alignment, the software halts with QuickBooks Error (-6073, -99001).

This error is a common roadblock in multi-user office environments. It typically appears when a workstation attempts to open a company file stored on a host server, only to find that the file is locked in single-user mode or set to a read-only state.

This guide explains what Error 6073 means, why it occurs, what precautions to take before troubleshooting, and step-by-step solutions to restore multi-user access without risking data loss.

What Is QuickBooks Error 6073?

QuickBooks Error 6073 is an operational database lock error. It indicates that the QuickBooks Database Server Manager cannot grant write access to the company file (.QBW) because another user, background process, or file attribute has placed the file in exclusive or read-only mode.

When this error occurs, QuickBooks displays one of two messages:

"QuickBooks is unable to open this company file. It may have been opened by another user. You should ask that user to switch to multi-user mode so you can both use it at the same time. The error code is (-6073, -99001)."

Or:

"QuickBooks is trying to open the company file in an environment that is read-only or restricted."

flowchart TD

    User["Workstation Tries to Open Company File"] --> Check{"Database Engine Lock Check"}

    Check -->|Open in Single-User Mode| Err["Error (-6073, -99001)"]

    Check -->|Active Lock File (.ND / .TLG)| Err

    Check -->|Folder Marked 'Read-Only'| Err

    Check -->|Multi-User Active & Unlocked| Pass["Company File Opens Normally"]

Common Causes of QuickBooks Error 6073 and 99001

Error 6073 is rarely caused by transactional data damage. Instead, it is almost always triggered by system-level locks or user permission settings:

• File Opened in Single-User Mode: Another user on the network opened the company file in Single-User Mode (for tasks like rebuilding data, running payroll, or importing list files), blocking concurrent connections.
• Orphaned Database Locks: A workstation lost power, disconnected from Wi-Fi, or closed improperly, leaving lingering session locks in the Network Data (.ND) or Transaction Log (.TLG) files on the server.
• Read-Only Folder Permissions: The folder hosting the company file, or the .QBW file itself, is marked "Read-only," which prevents the database engine from creating temporary write handles.
• Active Cloud-Sync Software: Services like OneDrive, Dropbox, Google Drive, or Box are actively scanning or syncing the company file folder in the background, locking the file.
• Antivirus or Security Software Scans: An endpoint security program is running an active scan on the .QBW file, temporarily locking read/write access.
• Corrupted Network Data Configuration: The .ND file contains outdated IP pointers or corrupted database tokens, preventing the host machine from completing network handshakes.

Symptoms of Error 6073

• The company file opens normally on the host server, but client workstations cannot access it across the network.
• Users receive a prompt stating that another user currently has the file open, even when all other workstations appear to be closed.
• QuickBooks freezes or closes abruptly when switching from Single-User to Multi-User Mode.
• The company file opens in read-only mode, preventing users from saving new invoices, bills, or journal entries.

Before You Start: Preparation and Data Safety

Before modifying network sharing settings, ending background tasks, or restarting server services:

1. Verify All Workstations Are Closed: Check with all QuickBooks users in the office to confirm whether anyone is actively performing administrative tasks (such as year-end closes, payroll runs, or data rebuilds).
2. Create a Manual Local Backup: If you can open the company file from any computer in single-user mode, make an immediate local backup (.QBB) via File > Back Up Company > Create Local Backup.
3. Verify File Location: Confirm that the company file resides on a supported Windows machine running the QuickBooks Database Server Manager, rather than on a network-attached storage (NAS) unit that lacks native Windows file-locking support.

How to Fix QuickBooks Error 6073

Follow these troubleshooting procedures in order, starting with the simplest user-mode checks and moving to server-level configuration fixes.

Step 1: Check If Another User Has the File Open in Single-User Mode

The most frequent trigger for Error 6073 is that another user left the file open in Single-User Mode.

1. Go to the other computers on your network where QuickBooks is installed.
2. If the company file is open on any computer, click the File menu in the top-left corner.
3. Check the menu options:

• If the option says Switch to Multi-User Mode, click it.
• If the user is running an administrative task, allow them to finish, then have them switch the file back to multi-user mode.

1. If a computer was shut down improperly while QuickBooks was still open, turn that computer back on, open QuickBooks, and close the file properly via File > Close Company/Logoff.
2. Return to the affected workstation and try opening the company file again.

Step 2: Terminate Lingering Background QuickBooks Processes

If a computer disconnected abruptly, its background tasks may still hold an active lock on the server's database engine.

1. On the workstation showing Error 6073 (and on any machine that recently accessed the file), press Ctrl + Shift + Esc to open Windows Task Manager.
2. Click the Processes or Details tab.
3. Look for any of the following processes:

• QBW32.EXE
• qbupdate.exe
• QBDBMgrN.exe

1. If any of these processes are running while QuickBooks appears closed, highlight each one and click End Task.
2. Repeat this check on the host server if no users are actively working in the software.

Step 3: Remove Read-Only Attributes from the Folder and File

If the company file or its hosting folder is flagged as read-only, the database manager cannot create the temporary lock files needed for multi-user access.

1. On the host computer or server, open Windows File Explorer.
2. Navigate to the folder containing your company file (e.g., C:\Users\Public\Documents\Intuit\QuickBooks\Company Files).
3. Right-click the folder containing your company file and select Properties.
4. In the General tab, locate the Attributes section at the bottom.
5. If the Read-only checkbox is marked or partially filled, click it to clear the checkmark.
6. Click Apply. When prompted, choose Apply changes to this folder, subfolders and files, then click OK.
7. Next, right-click the company file itself (.QBW), select Properties, confirm that Read-only is unchecked, and click OK.

Step 4: Recreate the Network Data (.ND) and Transaction Log (.TLG) Files

The .ND and .TLG files manage network communication and data sequencing. If they retain outdated lock states from an improper shutdown, renaming them forces the database engine to build fresh, unlocked configuration files.

Note: Renaming the .ND and .TLG files does not delete your accounting history. 

The .ND file will regenerate automatically during your next network scan, 

and your primary financial data remains safe inside the .QBW file.

1. Ensure all users across the network have completely closed QuickBooks.
2. On the host server, open the folder where your company file is stored.
3. Locate the files with the same name as your company file but ending in .ND and .TLG:

• YourCompanyFile.qbw.nd
• YourCompanyFile.qbw.tlg

1. Right-click the .ND file, select Rename, and append .OLD to the end: YourCompanyFile.qbw.nd.OLD.
2. Right-click the .TLG file, select Rename, and append .OLD to the end: YourCompanyFile.qbw.tlg.OLD.
3. Open the QuickBooks Database Server Manager from the Windows Start menu on the server.
4. Click the Scan Folders tab, browse to your company file folder, and click Start Scan.
5. Once the scan reports Success, open QuickBooks on the workstation and access the file in multi-user mode.

Step 5: Run QuickBooks Tool Hub Diagnostics

If manual steps do not resolve the lock, use the automated diagnostic tools in the QuickBooks Tool Hub:

1. Close QuickBooks Desktop on the affected workstation.
2. Launch the QuickBooks Tool Hub (make sure you are running the latest version, such as 1.6.0.8).
3. Select the Program Problems tab in the left-hand menu.
4. Click Quick Fix my Program. This ends lingering background tasks, clears temporary memory leaks, and resets registry keys.
5. If Error 6073 persists, switch to the Company File Issues tab.
6. Click Run QuickBooks File Doctor.
7. Browse to select your company file, choose Check your file and network, enter your administrative password, and run the repair scan.

When to Seek Professional Help

While most 6073 errors are resolved by switching user modes or renaming .ND files, certain complex technical scenarios require specialist assistance:

• Persistent Lockouts with All Systems Off: The database engine reports the file as open exclusively even after rebooting all workstations and the host server.
• Corrupted Internal Database Flags: The internal database header is damaged, causing the software to permanently misread user counts or multi-user flags.
• Active Directory and Domain Permission Locks: Networks managed by Group Policy Objects (GPOs) where folder permissions are repeatedly reverted to read-only.
• Co-Occurring -6000 Series Errors: Error 6073 appearing alongside fatal errors such as -6000, -82 or -6123, 0, which indicate deeper transactional table corruption.

Contact the Data Service Team

When automated diagnostic tools cannot clear the file lock or when facing critical multi-user downtime, contact the dedicated Data Service Team at +1-(888)-718-7888 for professional, secure database reconstruction, multi-user network optimization, and comprehensive QuickBooks data recovery.

How to Prevent QuickBooks Error 6073

1. Establish Single-User Protocols: Require team members to notify the office before switching to Single-User Mode, and switch back to Multi-User Mode immediately after completing administrative work.
2. Exclude Files from Cloud Syncing: Never store active .QBW working files inside Dropbox, OneDrive, Google Drive, or Box. These services frequently lock files during sync cycles, triggering Error 6073.
3. Use Wired Ethernet Connections: Ensure all accounting workstations are connected via stable gigabit Ethernet cables. Wi-Fi drops frequently cause orphaned lock files on the server.
4. Follow Proper Shutdown Procedures: Never turn off client computers or the host server while QuickBooks is open. Always exit through File > Exit to give the database engine time to release its memory handles cleanly.

Frequently Asked Questions (FAQs)

Does Error 6073 mean my company data is corrupted?

No. In most cases, Error 6073 is an operational state error rather than structural data damage. It simply means the software detected an active single-user session, a read-only restriction, or an orphaned file lock.

What is the difference between Error 6073 and Error 99001?

They appear together as a paired diagnostic message (-6073, -99001). The 6073 code indicates that QuickBooks cannot access the file due to an active lock or restricted permissions, while -99001 is the internal database sub-code indicating a single-user or hosting conflict.

Can I fix Error 6073 by copying the file to my desktop?

Yes, as a diagnostic test. Copying the .QBW file to your local C:\ drive can help confirm whether the issue is caused by server network locks or folder permissions. However, do not continue entering live transactions in the local copy while others work on the network, as this creates split, out-of-sync ledgers.

Why does Error 6073 return after renaming the .ND file?

If the error returns repeatedly, an automated background process (such as an antivirus scan, an unapproved cloud backup service, or a third-party add-on) is likely locking the file, or Windows folder permissions on the host machine are being reset by network Group Policy.

Conclusion & Action Plan

QuickBooks Error (-6073, -99001) can disrupt daily accounting workflows, but it is almost always caused by an active single-user session, read-only folder attributes, or orphaned .ND network lock files. By checking user modes across workstations, ending lingering background tasks, clearing read-only attributes, and rescanning your shared folders with the QuickBooks Database Server Manager, you can resolve the lockout and restore multi-user operations safely.

If automated diagnostic tools fail to clear the file lock, or if you encounter persistent database corruption and multi-user network failures, contact the certified Data Service Team at +1-(888)-718-7888 for immediate, secure database reconstruction, server environment optimization, and complete technical support.