QuickBooks

QuickBooks Error 6123, 0: "Connection to the Company File Has Been Lost" — Fixed

Published June 10, 2026 · by The FixHub Team

Error 6123, 0 — “Connection to the QuickBooks company file has been lost” — shows up at the worst times: when you open a file, upgrade to a new QuickBooks version, or restore a backup. Despite the alarming wording, it’s almost always a fixable network/file-path problem, not lost data. Work these in order.

Why it happens

  • A damaged .ND (network data) or .TLG (transaction log) file
  • Opening the company file from a USB drive, external drive, or cloud-synced folder (Dropbox/OneDrive)
  • Multiple QuickBooks Database Server services running (e.g. after upgrading versions)
  • Antivirus/firewall interrupting the file connection
  • General company-file damage

Fix 1: Rename the .ND and .TLG files

These rebuild automatically, so this is safe and resolves a large share of 6123 cases:

  1. Open the folder containing your .qbw company file.
  2. Find the files with the same name ending in .ND and .TLG.
  3. Right-click each → Rename → add .OLD to the end.
  4. Reopen QuickBooks. (Same first step used for the 6000-series errors — they’re cousins.)

Fix 2: Move the file off external/cloud storage

6123 loves removable and synced drives. If your .qbw lives on a USB stick, external drive, or a OneDrive/Dropbox folder:

  1. Copy the company file to a local folder like C:\QuickBooks\.
  2. Open it from there.

Cloud-sync folders are a frequent, overlooked cause — the sync client locks the file mid-write and QuickBooks loses the connection.

Fix 3: Run the Tool Hub (Quick Fix + File Doctor)

  1. Install the QuickBooks Tool Hub.
  2. Program Problems → Quick Fix my Program (clears stuck QuickBooks processes).
  3. Company File Issues → Run QuickBooks File Doctor → select your file → check it.

Fix 4: Restore from backup (after an upgrade)

If 6123 hit while upgrading the file to a newer QuickBooks version, the in-place conversion may have stumbled. Instead:

  1. Open the new QuickBooks version first.
  2. File → Open or Restore Company → Restore a backup copy, and restore your .qbb from a local folder.

This converts cleanly from backup rather than from the live file.

Fix 5: Check for duplicate database services

After installing a new year’s version, old QuickBooksDBXX services can linger and fight over the file:

  1. Win+Rservices.msc.
  2. Look for multiple QuickBooksDBXX entries (XX = version number).
  3. The current version’s service should be Running; older orphaned ones can be stopped.

For multi-user setups, also re-run Database Server Manager on the server — same step as the H202 fix.

FAQ

Is my data gone? Almost never — 6123 is a connection/path problem. Fixes 1–2 recover the file in most cases without touching your data.

It only happens when upgrading. Use the restore-from-backup route (Fix 4) instead of upgrading the live file.

Antivirus involved? Temporarily disable third-party AV and retry; if it works, add QuickBooks (.exe, and the file folder) to the AV’s exclusions.

Sources: Intuit — How to fix Error 6123, 0