QuickBooks Error 6123: Fix the Database Connection Error (2026 Guide)

QuickBooks Error 6123 is one of the more disruptive errors you can encounter — it blocks you from opening your company file entirely. The full message usually reads: “Error -6123, 0: Connection to the QuickBooks company file has been lost” or “We’re sorry. QuickBooks encountered a problem.” It most commonly strikes in multi-user environments, but it can also happen on single-user setups after a Windows update or a network change. Here’s how to fix it.

What Causes QuickBooks Error 6123?

This error has several distinct triggers, and identifying the right one saves you a lot of time:

• QuickBooks Database Server Manager not running. In multi-user mode, every workstation connects to the company file through this service. If it stops or crashes, all connections break and error 6123 appears.
• Network interruption or unstable connection. If the company file sits on a server or shared drive, any brief network drop during a read/write operation can sever the connection and trigger this error.
• Firewall or antivirus blocking QuickBooks. Security software frequently blocks QuickBooks’ database ports (8019, 56728, 55378–55382), which prevents the software from reaching the company file.
• Company file moved or renamed while QuickBooks was open. Changing the file path or name while the software is running breaks the internal connection pointer.
• Damaged or corrupted company file (.QBW). File corruption — from an unexpected shutdown, storage failure, or incomplete backup restore — can trigger 6123 on every open attempt.
• Windows update disrupted QuickBooks services. Major Windows updates sometimes disable or reconfigure services that QuickBooks depends on, including the Database Server Manager.
• Multiple instances of QuickBooks running simultaneously. Running QuickBooks twice on the same machine can create file-lock conflicts that produce error 6123.

How to Fix QuickBooks Error 6123: Step-by-Step

Step 1 — Close All QuickBooks Processes

Before anything else, make sure QuickBooks is fully closed on every machine that accesses the company file. On each computer, press Ctrl + Shift + Esc to open Task Manager, click the Processes tab, and end any process named QBW32.exe, QBDBMgrN.exe, or QBCFMonitorService.exe. Then wait 30 seconds before proceeding.

Step 2 — Run QuickBooks File Doctor

QuickBooks File Doctor is Intuit’s built-in repair tool and handles the majority of 6123 cases automatically.

1. Download and install the QuickBooks Tool Hub from Intuit’s support site if you haven’t already.
2. Open QuickBooks Tool Hub and click Company File Issues.
3. Click Run QuickBooks File Doctor.
4. In the dropdown, select your company file. If it doesn’t appear, click Browse and locate it manually.
5. Select Check your file and click Continue.
6. Enter your QuickBooks admin password when prompted and click Next.
7. The scan takes 2–5 minutes depending on file size. Let it complete, then try reopening QuickBooks.

Step 3 — Restart QuickBooks Database Server Manager

This step is critical in multi-user setups. On the server machine (the computer that hosts the company file):

1. Open QuickBooks Tool Hub and click Network Issues.
2. Click QuickBooks Database Server Manager.
3. Click Start Scan to let it scan your company file folder.
4. Once the scan finishes, click Close and try reopening the company file from a workstation.

Alternatively, restart the service manually: press Windows + R, type services.msc, find QuickBooksDBXX (XX = your version year), right-click it, and select Restart.

Step 4 — Move the Company File to a Local Drive

This step isolates whether the issue is the file itself or the network path:

1. Copy your company file (.QBW) to a local folder on your C: drive — for example, C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\.
2. Open QuickBooks and go to File > Open or Restore Company.
3. Navigate to the local copy and open it.

If it opens without error, the problem is your network path or server configuration — not the file itself.

Step 5 — Add QuickBooks Firewall Exceptions

If the file opens locally but not over the network, your firewall is likely the culprit.

1. Open Windows Defender Firewall via the Control Panel.
2. Click Allow an app or feature through Windows Defender Firewall.
3. Click Allow another app and add the QuickBooks executable (QBW32.exe) and the Database Server Manager (QBDBMgrN.exe).
4. Also open inbound and outbound rules for ports 8019, 56728, 55378–55382.

If you use third-party antivirus software (Malwarebytes, Norton, Bitdefender), add QuickBooks to its exceptions list as well.

Step 6 — Restore From a Recent Backup

If the company file is genuinely corrupted and File Doctor can’t repair it:

1. Go to File > Open or Restore Company > Restore a backup copy.
2. Select Local backup and browse to your most recent .QBB backup file.
3. Choose a restore location and click Open.
4. Re-enter any transactions that occurred after the backup date.

This is why maintaining daily backups is non-negotiable. If you don’t have a recent backup, see the advanced section below.

Step 7 — Rename the .ND and .TLG Files

QuickBooks creates network descriptor (.ND) and transaction log (.TLG) files alongside every company file. These can become corrupted and block access.

1. Navigate to the folder where your company file (.QBW) is stored.
2. Find files with the same name as your company file but with .ND and .TLG extensions.
3. Right-click each one and rename it — add .old to the end (e.g., CompanyFile.qbw.nd.old).
4. QuickBooks will recreate these files automatically when you reopen it.

Still Not Working?

If all seven steps above haven’t resolved QuickBooks error 6123, try these advanced approaches:

• Reinstall QuickBooks Database Server Manager. In the QuickBooks installer, choose the Server installation option and let it reinstall the Database Server Manager fresh. This resolves deep service corruption that restarts and scans can’t fix.
• Use the QuickBooks Auto Data Recovery (ADR) tool. If your company file is corrupted beyond repair and you have no backup, ADR may be able to recover most of your data. It uses .QBW.adr and .TLG.adr files stored automatically by QuickBooks. Look for these in the same folder as your company file.
• Check your hosting setup. In QuickBooks, go to File > Utilities and make sure Host Multi-User Access is only enabled on the server machine — not on workstations. Having it enabled on multiple machines simultaneously can cause persistent 6123 errors. For related multi-user connection issues, see also our guide on QuickBooks Error 6000, which covers the full 6000 series of company file access errors.

Prevent QuickBooks Error 6123 in the Future

• Run daily automatic backups. Go to File > Back Up Company > Create Local Backup, then set a schedule. Even a single day of lost transactions is painful to reconstruct manually.
• Keep the Database Server Manager running as a service. Set it to start automatically: open services.msc, find QuickBooksDBXX, double-click it, and set Startup type to Automatic. This prevents it from silently stopping after a system restart.
• Never store the company file on a mapped drive. Always use a UNC path (\\ServerName\ShareName\) or store the file on the local server drive. Mapped drives lose their connection more frequently and are a common cause of 6123 in network environments.

QuickBooks error 6123 is fixable in the vast majority of cases — File Doctor and a Database Server Manager restart resolve it roughly 80% of the time. If your company file is damaged and you need a fresh, genuine installation of QuickBooks Desktop to restore from backup, legitimate one-time licenses are available at keys2024.store. For more on recovering lost company files in general, see our guide on QuickBooks company file not found — it covers the full range of file location and recovery scenarios.

Frequently Asked Questions

What causes QuickBooks Error 6123?

Error 6123 is caused by QuickBooks losing its connection to the company file. The most common triggers are the QuickBooks Database Server Manager not running, a network interruption, firewall ports being blocked, or a corrupted company file (.QBW).

How long does it take to fix QuickBooks Error 6123?

Most cases are resolved in 10–20 minutes using QuickBooks File Doctor and a Database Server Manager restart. If the company file is corrupted and requires a backup restore, the process depends on backup file size and how many transactions need to be re-entered.

Can QuickBooks Error 6123 cause data loss?

The error itself doesn’t cause data loss — it just prevents access. However, if the underlying cause is file corruption, some recent transactions may be unrecoverable unless you have a recent backup. This is why maintaining daily automatic backups is critical.

Does QuickBooks Error 6123 only happen in multi-user mode?

It’s most common in multi-user environments, but it can also occur on a single-user setup if the company file has been moved, renamed, or corrupted. The fix steps are the same regardless of setup — start with File Doctor and the .ND/.TLG rename method.