Fix QuickBooks Desktop Error -6240: Multi-User & File Damage

Last reviewed 2026-07-03 4 min read

Resolve QuickBooks Desktop error -6240 and related -6000-series company file errors. Step-by-step fixes for network, multi-user, and file damage issues.

When you are working in a multi-user environment and QuickBooks Desktop suddenly throws error -6240, it usually means the application hit a wall while trying to communicate with the company file over the network. This error is part of the broader -6000 series of company file errors. Rather than signaling an immediate disaster, a -6000-series code typically points to a breakdown in how QuickBooks accesses, locks, or reads your data file. Because these codes often share the same underlying triggers, the troubleshooting steps for -6240 will also resolve many neighboring errors (such as -6190, -6123, or -6000/-82).

What Error -6240 Means in Plain English

Error -6240 specifically occurs when one workstation is unable to open or interact with the company file because the network connection dropped, or because the file's network descriptor files are out of sync. In a multi-user setup, QuickBooks relies on a host computer to act as a server, directing traffic to the .qbw file. If a workstation tries to access the file while the host is busy, restarting, or if the network experiences a momentary hiccup, QuickBooks flags the access failure as a -6240 error.

Common Causes

Several factors can trigger this error, most of which relate to your network or temporary file states:

Network configuration files (.ND) are corrupted: The Network Descriptor (.ND) files tell QuickBooks where the company file lives on the network. If they are damaged, workstations cannot find the file.
Transaction log file (.TLG) mismatches: If the .TLG file becomes desynchronized from the main company file, QuickBooks may refuse access to prevent data corruption.
Database Server Manager is not running: The QuickBooks Database Server Manager must be actively running on the host computer to route multi-user traffic.
Firewall or antivirus blocking: Security software can occasionally block internal network ports that QuickBooks uses to communicate between computers.
Actual company file damage: In rarer cases, the .qbw file itself has structural damage that prevents it from opening.

How to Fix Error -6240 Yourself

You can resolve this error entirely on your own, without needing an active Intuit support plan or upgrading your software. Follow these steps in order:

Run a local-copy test: Create a new folder directly on your C: drive (e.g., C:\QBTest). Copy your company file (.qbw) and paste it into this new local folder. Open QuickBooks while holding down the Ctrl key (to open without a company file), then browse to and open the .qbw file from the C:\QBTest folder. If it opens without error, the problem is your network or hosting setup, not the file itself.
Rename the .ND and .TLG files: If the local test worked, go back to the original folder where your company file is stored. Locate the files ending in .ND and .TLG (they will have the same name as your company file). Right-click each one and rename them to .ND.OLD and .TLG.OLD. QuickBooks will automatically rebuild fresh, undamaged versions of these files the next time you open the database.
Rescan with Database Server Manager: On the computer acting as your server, open the Start menu, find QuickBooks Database Server Manager, and run a full folder scan on the directory holding your company file. This forces the server to update its network routing.
Run Verify and Rebuild: Open your company file in single-user mode. Go to File > Utilities > Verify Data. If QuickBooks detects damage, proceed to File > Utilities > Rebuild Data. You may need to run the Rebuild utility two or three times until it reports no further issues.

Preventing the Error from Recurring

To keep your Desktop installation stable long-term, ensure that hosting is turned on only on the server computer and turned off on all workstations (check under File > Utilities > Host Multi-User Access). Keep your firewall configured to allow QuickBooks through, and avoid storing your company file in a cloud-synced folder (like OneDrive, Dropbox, or Google Drive), as these sync locks will routinely trigger -6000-series errors.

When the Company File Itself Is Damaged

If the file fails to open even during your local-copy test (Step 1), or if the Verify/Rebuild utility repeatedly fails to fix the error, the .qbw file itself is likely damaged. When internal utilities cannot repair the structural damage, you will need targeted file repair. For repairing damaged QuickBooks company files, reaching out to a dedicated file-repair service is the most reliable way to extract and rebuild your data without being forced to upgrade or abandon your current Desktop setup.