QuickBooks Error 6123, 0: Troubleshooting Lost Connection to Company File

September 23, 2026 6 min read

QuickBooks Error 6123, 0 appears when QuickBooks Desktop attempts to restore a backup file (.qbb), open a company file across a local network, or upgrade a database to a newer annual release, only to experience an immediate connection interruption. This error indicates that the communication loop between the application client and the database engine has abruptly dropped.

Fast-Fix: The 45-Second Solution

To resolve Error 6123, 0 when restoring a backup, move the .qbb file directly to your local C:\ drive rather than running it from a flash drive or network path. If the error occurs when opening a network file, restart the QBCFMonitorService and QuickBooksDBXX services on your host computer, or run the “Quick Fix my Program” tool inside the QuickBooks Tool Hub.

Quick Status & Triage Snapshot

  • Data Risk Tier: Medium. Restores that terminate unexpectedly can leave incomplete files, but the source backup remains safe.
  • Multi-User Impact: Moderate to High. Often isolates a single workstation, but server-wide service stalls can impact all users.
  • Common Trigger: Restoring backups across mapped network drives, corrupted Windows user profiles, or aggressive antivirus software breaking the database socket connection.
  • Estimated Fix Time: 10 to 20 minutes.

Diagnostic Flowchart: 6123, 0 Decision Path

[Start: Error 6123, 0 Displays]
          │
          ▼
What were you doing when the error occurred?
  ├── Restoring a Backup (.qbb) ──> Copy .qbb to local C:\ drive, then restore directly to local disk.
  ├── Upgrading Company File    ──> Run Quick Fix My Program, upgrade locally, then move back to server.
  └── Opening File Over Network ──> Continue below.
          │
          ▼
Can you open the company file directly on the Server hosting it?
  ├── No  ──> Service failure. Restart QBCFMonitorService and Database Manager services.
  └── Yes ──> Workstation firewall or DNS issue. Configure Port 8019 and test communication.

Is Your Data at Risk?

  • If this occurred during a backup restoration: Your data is completely safe. The .qbb file is a read-only archive; it does not degrade because a restore attempt failed. Simply avoid restoring repeatedly into the same damaged target directory.
  • If this occurred during normal multi-user access: Data is rarely lost, though any transaction being written at the moment of the network break may need to be re-entered.
  • If this occurred during a version upgrade: Stop immediately. Do not attempt to force-upgrade the file multiple times. An interrupted database upgrade can corrupt the file’s internal database structure.

Technical Anatomy: What This Error Means

QuickBooks relies on a continuous client-server TCP handshake via port 8019 (and dynamic database ports assigned by the Database Server Manager). Error 6123, 0 is thrown when:

  1. The client sends an initialization command to the database engine.
  2. The engine responds, but the TCP socket is closed prematurely by an external filter (such as a deep-packet inspection antivirus utility).
  3. Alternatively, if a restore is taking place, the Windows operating system rejects the application’s request to write temporary uncompressed database clusters due to path length limitations or user account token restrictions.

Differential Diagnosis: Don’t Confuse This With…

Step-by-Step Repair Guide

Work through these steps in order, starting with the simplest diagnostic scenario.

Step 1: Move the File Locally (For Backup & Restore Errors)

If you encountered Error 6123, 0 while restoring a .qbb file:

  1. Close QuickBooks Desktop.
  2. Copy the .qbb file from your external flash drive, external hard drive, or network share.
  3. Paste the file directly into a simple local directory, such as C:\QuickBooks_Restores\.
  4. Open QuickBooks Desktop, select Open or restore an existing company, choose Restore a backup copy, and browse to C:\QuickBooks_Restores\.
  5. When prompted for the save location of the restored .qbw file, point it to your local hard drive first. Once restored successfully, you can copy the working .qbw file back to your server.

If your backup file issues persist, refer to External Drive Fix: Cannot Restore .QBB Files from USB or External Storage.

Step 2: Run “Quick Fix my Program” from Tool Hub

If the error occurs while trying to open a standard file on a workstation:

  1. Download and install the latest QuickBooks Tool Hub.
  2. Open the Tool Hub and select the Program Problems tab.
  3. Click on Quick Fix my Program.
  4. Allow the process to complete (this shuts down background background dependencies and clears temporary program registry caches).
  5. Restart your computer and try opening your company file again.

Step 3: Restart Host Database Services

If multiple computers fail with Error 6123, 0 when accessing a hosted file:

  1. Log in to the host server machine.
  2. Press Windows Key + R, type services.msc, and press Enter.
  3. Scroll through the services list and locate:
    • QuickBooksDB[XX] (where XX represents the software version, e.g., 34, 35, 36)
    • QBCFMonitorService
  4. Right-click QuickBooksDB[XX] and select Restart.
  5. Right-click QBCFMonitorService and select Restart.
  6. Ensure that both services are set to Automatic under their Startup type properties.

For more detailed network service configuration, see QBCFMonitorService: How to Fix Service Startup Errors on Your Server.

Step 4: Create a New Windows User Account

If Error 6123, 0 persists on a single machine, your Windows User Profile might be damaged, blocking database encryption tokens:

  1. Click Start > Settings > Accounts > Family & other users.
  2. Select Add someone else to this PC.
  3. Choose I don’t have this person’s sign-in information, then Add a user without a Microsoft account.
  4. Name the test account, assign it Administrator privileges, and log out of Windows.
  5. Log into the newly created profile, launch QuickBooks, and open the company file.

Hard Stop: When to Call an Expert

Discontinue manual troubleshooting if:

  • The error interrupts an automated database structural upgrade, and QuickBooks fails to reopen the file on both the old and new software versions.
  • The QuickBooks File Doctor utility halts with an unhandled exception or reports “Fatal Database Structural Breakdown.”
  • Your company file displays an erratic file size or has been quarantined by an endpoint security platform as suspect.

Closing the Books

QuickBooks Error 6123, 0 is typically a defensive disconnect triggered by a dropped network connection, strict security software, or an interrupted restore path. Your primary data remains protected. By isolating the file to a clean local directory or resetting the hosting background services, you can re-establish a stable connection without losing transactions or structural integrity.

QuickBooks Error 6190, -816: Resolving Transaction Log & File Discrepancies

October 2, 2026

QuickBooks Error 6176: Troubleshooting Firewall Blocks on Company File Paths

October 1, 2026

QuickBooks Error 6189, 816: Fix “Company File is Already in Use”

October 1, 2026