QuickBooks Error 6123, 0 When Opening a Company File or Backup

Error 6123, 0 stops QuickBooks Desktop from opening a company file or restoring a backup; here is how our engineers get the file open without data loss.

Error 6123, 0 stops QuickBooks Desktop the moment it tries to open a company file or restore a backup. The wording sounds like data loss, but the file is usually intact. Our engineers treat it as a connection and housekeeping fault first, and as internal damage only after the simpler causes are ruled out.

What causes error 6123, 0?

Three triggers cover most of the cases we see.

The first is the network path. When a company file sits on a share, QuickBooks reaches it through a companion with the .ND extension, which records which machine hosts the database. A stale pointer, or one aimed at a machine that no longer hosts, breaks the handshake and produces this error.

A damaged restore target is the second. QuickBooks writes the restored file into whatever folder you choose. Bad sectors, broken permissions, or a cloud sync client locking files mid-write will abort the restore and report the same code.

Companions out of sync form the third. The .TLG transaction log grows beside the company file and records every entry since the last backup. If the pairing breaks, because one file was copied without the other, QuickBooks refuses to proceed rather than risk mismatched data.

Before you touch the file

Copy, never move. Put a working copy of the backup, and of the company file if one exists, somewhere safe first. Everything below happens on copies.

Get everyone out. If the file opens at all, switch to single-user mode from the File menu, then close it. If it will not open, confirm no other machine has it open and that hosting is off on workstations.

Have the admin password for the backup ready, because restore will ask for it. When we rename companion files, we rename rather than delete, so the step can always be undone.

Copy the backup to a local folder

  1. On the machine with QuickBooks installed, create a new folder on the local hard drive. Keep it outside any folder a cloud sync client watches.
  2. Copy the .QBB backup into that folder. Copy it; do not move it.
  3. If the original .QBW still exists on the share, copy it too, together with its two companions: the .ND file and the .TLG file.

Rename the companion files

  1. In Windows, turn on file name extensions if they are hidden, so you can see what you are renaming.
  2. Find the .ND and .TLG files that share the company file's name. Rename each by adding OLD to the end of the extension. Do not delete them.
  3. QuickBooks will build a fresh .ND the next time the file opens, and start a clean log beside it.

One caution on the .TLG. If the original company file holds transactions recorded after the last backup, that log is the only record of them. Keep the renamed pair together in their folder. Our QuickBooks transaction log recovery service can still read a renamed log, but only if it stays beside its own .QBW.

Restore into a fresh folder

  1. Open QuickBooks and choose Open or Restore Company from the File menu. Pick Restore a backup copy, then Local backup.
  2. Browse to the .QBB you copied in step 2.
  3. When asked where to save, choose another new folder created for this restore. Do not restore over the old location, and do not use the folder the last restore failed in.
  4. Enter the admin password when prompted and let the restore finish. Large files take a while; interrupting one mid-write is how damaged targets get created.
  5. Open the restored file in single-user mode first, before anyone else touches it.

Signs the restore worked

  • The file opens with no error, and a new .TLG appears beside it within moments.
  • A balance sheet and a profit and loss report for a recent period both run without complaint.
  • Verify Data, found under the File menu within Utilities, comes back clean with no rebuild prompt.
  • Spot balances and recent transaction dates match what you expect from the books.

Knowing when to stop

If the local copy restores cleanly, the fault was the path or the folder. Treat the original location as suspect until it is checked. If the file must return to the network, set it up on the host machine fresh rather than copying the old companions back.

Stop instead of pushing on if any of these happen. The same error returns with the backup on local disk in a fresh folder. The restore dies partway through, or QuickBooks calls the backup invalid. The restored file throws C= errors or an unrecoverable error. Verify demands rebuild after rebuild without clearing.

At that point the backup itself is the patient, and loop-restoring it against a failing folder only deepens the trouble. Our QuickBooks error code repair service handles the -6000 family directly. A backup that refuses to restore on any machine is a recovery problem, and emergency QuickBooks data recovery is built for exactly that.

Renaming companions and restoring to a clean folder never touches the books themselves. The risk sits in repeated attempts against a bad target. Stop early, keep the .QBW and its renamed .TLG together, and the data stays recoverable.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.