Fix QuickBooks Desktop Error -6123, 0 (Company File Connection)

Last reviewed 2026-07-03 3 min read

Resolve QuickBooks Desktop error -6123, 0 when you cannot open or connect to your company file. Learn the causes and how to fix it offline without upgradin

When you try to open, update, or back up your company file in QuickBooks Desktop and the software suddenly loses its connection, you might encounter Error -6123, 0. This typically means QuickBooks cannot establish a stable connection to your .qbw file. Fortunately, you can usually resolve this issue locally and keep your Desktop environment running exactly as it is.

Understanding the -6000 Error Family

Error -6123, 0 belongs to the broader -6000 series of QuickBooks errors. Codes in this family (which includes nearby variants like -6000, -77, -82, and -318) all point to the same general problem: QuickBooks is being blocked from reading or writing to your company file. The specific suffix (, 0) helps narrow down the exact point of failure, which is usually a network glitch, a damaged configuration file, or a firewall block rather than a problem with the accounting data itself.

Common Causes of Error -6123, 0

Before jumping into repairs, it helps to understand what triggers this disconnect. The most frequent culprits are:

Damaged network data files: QuickBooks uses .ND (Network Data) and .TLG (Transaction Log) files to manage multi-user access and database connections. If these auxiliary files become corrupted, the main company file cannot open.
Firewall or antivirus interference: Your computer's security software may mistakenly identify QuickBooks' background processes as a threat and sever the connection.
Hosting configuration errors: If multiple computers are trying to host multi-user access simultaneously, the connection will fail.
Damaged company file: In more severe cases, the .qbw file itself has sustained data corruption.

How to Fix Error -6123, 0

We recommend working through these steps in order. They apply generally to QuickBooks Pro, Premier, and Enterprise, though the exact wording of menu options can vary slightly depending on your version.

Test a Local Copy: First, determine if the problem is with the file or your network. Copy the company file from its current location (especially if it lives on a server or network drive) and paste it directly onto your local Desktop. Open it from there. If it opens successfully, your company file is fine, and the issue is a network or firewall configuration problem.
Rename the .ND and .TLG Files: If the file is local and still throwing the error, navigate to the folder containing your .qbw file. You will see files with the exact same name but with .ND and .TLG extensions. Right-click each one and rename them (for example, add .OLD to the end, turning company.QBW.ND into company.QBW.ND.OLD). QuickBooks will automatically recreate fresh, uncorrupted versions of these files the next time you open the company file.
Rescan with Database Server Manager: If you operate in multi-user mode, you need to ensure the server is properly configured to share the file. Open QuickBooks Database Server Manager on the machine hosting the files, go to the Scan Folders tab, and run a scan. This forces QuickBooks to re-index the company file and reset network permissions.
Run Verify and Rebuild: If the error persists, internal data damage may be present. Open your company file in single-user mode, go to the File menu, select Utilities, and choose Verify Data. If QuickBooks finds problems, it will prompt you to run Rebuild Data. The Rebuild utility will attempt to repair structural damage within the file.

Preventing the Error from Recurring

To keep your Desktop installation stable, make sure your firewall is configured to allow QuickBooks through. If you run a multi-user setup, verify that the "Host Multi-User Access" setting is only activated on the single primary server computer, and turned off on all workstations. Running the Verify Data utility once a month can also catch minor data inconsistencies before they escalate into full connection failures.

When the Company File is Damaged

If you have completed all the local steps above—especially running Verify and Rebuild multiple times—and QuickBooks still throws Error -6123, 0, the company file itself is likely severely corrupted. At this stage, restoring from a recent backup is the fastest route, but if your backups are also outdated or throwing errors, you will need dedicated repair tools to extract the data from the damaged .qbw file.