Why restoring from USB causes 6123: QuickBooks requires a continuous, uninterrupted connection to the file during the entire restore operation. USB drives, external hard drives, and cloud storage (Dropbox, Google Drive) cannot guarantee this — the connection can microseconds-drop during the restore handshake, causing QB to fail with 6123. Copying the .QBB file to the local C: drive first takes 30 seconds and eliminates this cause entirely before any repair tools are needed.

Error code

6123, 0

6xxx Series · Connection Lost

Related: -6000 -83 · -6177 · -6150

What it means

Error 6123 means QuickBooks lost the connection to the company file during an operation — either the connection was never fully established, or it was interrupted mid-process. This is a connection stability error, not necessarily a file damage error. The company file is usually intact.

Your data is likely safe. In most 6123 cases the company file is undamaged — the connection failed before any write operation completed. Always try the path and connection fixes before assuming the file needs repair.

Restoring from USB or Cloud Storage

Most common cause — restoring a .QBB backup file directly from a USB drive, external hard drive, or cloud-synced folder. QB needs a stable uninterrupted connection throughout the restore — external storage cannot guarantee this. Copy the .QBB to C: drive first.

QuickBooks Database Server Manager Not Running

In multi-user mode, QBDSM manages the connection between workstations and the company file on the server. If QBDSM stopped, crashed, or was never configured for the company file folder, all workstations get 6123 when trying to connect.

Corrupt .ND or .TLG Files

A corrupted Network Descriptor (.ND) or Transaction Log (.TLG) file causes QuickBooks to lose the connection mid-open. Renaming both and letting QB regenerate them resolves this without touching the actual company file data.

Network Instability or Firewall Blocking

Brief packet loss on the network, or a firewall/antivirus product blocking QB's database port, interrupts the connection. Even a momentary network drop during a file open or restore is enough to trigger 6123.

Upgrading File Over a Network

Running the QuickBooks file upgrade process on a company file stored on a network share. The upgrade requires a direct, sustained local connection. Network latency during the upgrade breaks it with 6123. Always upgrade from a local copy.

Damaged Company File

Internal data damage prevents QB from completing the connection handshake. Less common than the path/network causes — check this after trying the faster fixes first. File Doctor and Verify/Rebuild address data-level damage.

METHOD 1 Copy the Backup File to Local C: Drive Before Restoring Scenario 1 — 6123 during backup restore · Do first

If 6123 appeared while restoring a .QBB backup, this is almost certainly the cause. Restoring directly from USB, external drive, or cloud storage is unreliable — copy the backup to the local C: drive first.

METHOD 2 Use a Portable Company File Instead of a Backup If .QBB restore keeps failing with 6123

A portable company file (.QBM) is a compressed, self-contained version of the company file designed specifically for transfer between computers. It uses a different mechanism than the standard backup restore — and bypasses the connection issue that causes 6123 in many cases.

METHOD 3 Run QBDSM Scan and Rename .ND / .TLG Files Scenario 2 — multi-user, workstations can't connect

If 6123 appears in multi-user mode with workstations unable to connect to the server, QBDSM is the first fix — it re-establishes the connection routing. Renaming the .ND and .TLG files forces QB to recreate both from scratch.

METHOD 4 Copy File Locally Before Upgrading to New QB Version Scenario 3 — 6123 during file upgrade

Upgrading a company file stored on a network share is the #1 cause of 6123 during upgrade. The upgrade process requires a direct sustained connection — network latency or drops break it. Always upgrade from a local copy.

METHOD 5 Run QuickBooks File Doctor All path / connection methods tried — possible file damage

If the file fails to open locally (eliminating path as the cause), File Doctor diagnoses and repairs both network configuration issues and minor file data damage that can cause 6123.

METHOD 6 Restore from Auto Data Recovery (.ADR) File If all other methods fail and no clean backup is available

QuickBooks automatically creates Auto Data Recovery (.ADR) backup files in the company file folder. If your .QBB backup is corrupt and File Doctor cannot repair the .QBW, an ADR file may allow you to recover data up to the last auto-save point.

How is Error 6123 different from Error 6000-83? Both stop QB from opening the file.

Both are 6xxx company file errors but they fail at different points. Error 6000-83 means QuickBooks reached the file but cannot read it — the path is correct but the file data is damaged or the filename is invalid. Error 6123 means the connection to the file was lost during an operation — either the path became unstable (USB storage, network drop) or the connection broke mid-process. Fix 6000-83 by fixing the file (File Doctor, Verify/Rebuild). Fix 6123 by fixing the connection stability (copy to local drive, QBDSM scan, rename .ND). The local drive test is the fastest diagnostic for both: if the file opens locally, it's a connection/path issue (6123 pattern). If it still fails locally, it's a file issue (6000-83 pattern).

Why does QuickBooks say the company file cannot be opened when I can see the file in Windows Explorer?

Seeing the file in Windows Explorer confirms it exists — but QuickBooks needs more than existence to open it. QB requires an uninterrupted connection for the duration of the file open handshake, read/write permissions for the QBDataServiceUser account on the folder, a valid .ND file that correctly maps the network location, and QuickBooks Database Server Manager running on the server in multi-user mode. Any one of these missing produces an error like 6123 even though the file is visible. Opening the file directly from inside QuickBooks (File → Open) rather than double-clicking the .QBW in Explorer also avoids a separate class of issues that can trigger 6123.

Can I prevent Error 6123 from happening in the future?

Three practices prevent the most common 6123 scenarios. For backups: always save backups to the local C: drive first, then copy to external storage after QB has finished the backup process — never set QuickBooks to save backups directly to USB or cloud. For upgrades: always upgrade from a local copy, never directly from a network share — copy the file locally, upgrade, then return it to the server. For multi-user: run the QBDSM scan after any server restart, server name change, or network reconfiguration. A 5-minute QBDSM scan after these events prevents the majority of multi-user 6123 errors that appear on the following workday.