Fix QuickBooks Error -6123, 0 When Opening a File or Restoring a Backup

Error -6123, 0 blocks QuickBooks Desktop from opening a company file or restoring a backup. Our steps isolate the network from the file and reopen it.

Error -6123, 0 stops QuickBooks Desktop at the door: the company file will not open, or a backup restore fails partway. The error belongs to the -6000 family, and it usually points at the connection between the program and the file, not the file itself. Our engineers clear it with three checks in order: rebuild the network support files, correct hosting, and test a local copy to split the network from the file.

The error points at the connection first

The -6123, 0 message fires when QuickBooks cannot reach the company file cleanly. Most often the file sits on a network share and one of its support files has gone stale. Two support files sit beside every company file. The .ND network descriptor tells QuickBooks how to reach the file over a network. The .TLG transaction log records the newest entries. A stale or mismatched .ND is the common trigger here. Less often, the company file or the backup is genuinely damaged.

Prepare before you rename anything

1. If the file still opens at all, run a fresh backup. If it will not open, copy the entire file set (.QBW, .QBB if present, .ND, .TLG) to a separate folder instead. Renaming is reversible, but guard the originals regardless.
2. Have every user exit QuickBooks, on every computer that touches the file, including the host. If the file opens intermittently, switch the host to single-user mode first so no one is mid-transaction.
3. Note the folder that holds the company file. You will return to it twice.
4. In Windows File Explorer, turn on file name extensions from the View menu. Hidden extensions lead to renames that change nothing.

Rename the .ND and .TLG files

1. In the company file folder, find the two files that share the company file's name. One ends in .ND, the other in .TLG.
2. Right-click the .ND file, choose Rename, and add .OLD so the name ends in .ND.OLD.
3. Repeat with the .TLG file so it ends in .TLG.OLD.
4. Leave both renamed files in the same folder. Renaming keeps their contents; deleting would not.
5. Reopen QuickBooks and open the company file. The program rebuilds the .ND on its own.

Treat the .TLG with respect. It holds the newest transactions that may not yet be inside the main file. If the company file later proves damaged, rename the .TLG back to its exact original name before any recovery attempt. That log can decide whether the most recent work survives.

Should hosting be on or off on each workstation?

Hosting decides which computer serves the file in multi-user mode. Only the machine that stores the company file should host it. Two hosts on one network will fight, and -6123, 0 is one way that fight surfaces.

1. On each computer that runs QuickBooks, open the File menu and choose Utilities.
2. Read the options. "Stop Hosting Multi-User Access" on screen means hosting is on for that machine; "Host Multi-User Access" means it is off.
3. On every machine except the host, choose Stop Hosting Multi-User Access and confirm the prompts. Let QuickBooks close and reopen if it asks.
4. On the host, run QuickBooks Database Server Manager from the Windows Start menu, and scan the folder holding the company file so it registers cleanly.

Test a local copy to split the network from the file

1. With QuickBooks closed everywhere, copy the .QBW file from its server folder to the local desktop of the machine reporting the error. Copy it; never move it.
2. Open QuickBooks, choose Open or Restore Company, then Open a Company File, and select the desktop copy.
3. If the local copy opens, the company file is sound. The fault sits in the path: folder permissions, a firewall rule, or the hosting setup.
4. If the local copy fails the same way, the file itself is the suspect.

Do not keep working in the desktop copy. Entries made there live on one machine only. Close it and delete it after the test, or the books will split in two. When the path is at fault, give the QuickBooks database user full control of the shared folder, and confirm the firewall allows the program on the host.

Two extra rules when the error appears during a restore

Restore to the local hard drive first, never to a network share or a USB device. Restore into a fresh folder that holds no company file of the same name. Open the restored file locally, confirm it works, then move it to the server and open it there.

Signs the fix worked

• The company file opens without the error, first in single-user mode and again with several users.
• The .ND file reappears beside the company file after the Database Server Manager scan finishes.
• A second workstation holds the file open across the network, even after both machines restart.

The limits of this workaround

These steps repair connections, not damage inside the data. Once the file reopens, run Verify Data from the File, Utilities menu. If Verify fails, or Rebuild fails to clear what it finds, the damage is internal and renamed support files will not touch it. Restores that fail from more than one backup point to a damaged backup file rather than the network.

For errors that survive these steps, our QuickBooks error code repair service covers the -6000 family directly. When a damaged file has a renamed log, recovering transactions from the .TLG transaction log can still bring back the most recent entries.

Open the file first, verify it second, and leave cleanup and performance work for after it holds.