Step-by-Step Fix for QuickBooks Error 6123 (No Tech Skills Needed)

QuickBooks Error 6123 appears when QuickBooks loses its connection to your company file — usually during an attempt to open, restore, or back it up. The full message reads: “Error -6123, 0: Connection to the QuickBooks company file has been lost.” It shows up most often in multi-user environments or when the file lives on a network drive, but it can also hit single-user setups after a Windows update or an unexpected shutdown. The fix rarely requires reinstalling anything.

What Causes QuickBooks Error 6123?

QuickBooks Error 6123 is almost always a file access problem — either QuickBooks cannot find the file, cannot open it due to permissions, or the file itself has been corrupted. The most common specific causes are:

• Damaged .ND file: Every QuickBooks company file has a companion .ND (Network Descriptor) file that tells QuickBooks where to find the company file on a network. If the .ND file is corrupted — which happens after crashes, Windows updates, or abrupt shutdowns — QuickBooks throws Error 6123 when trying to connect.
• QuickBooks Database Server Manager not running: In multi-user setups, the Database Server Manager on the host computer manages connections. If it is stopped or crashed, all client computers see Error 6123 when they try to open the company file.
• Firewall or antivirus blocking QuickBooks ports: QuickBooks needs specific network ports open (8019, 56728, 55378-55382). If Windows Firewall or a third-party antivirus blocks them, the connection fails with Error 6123.
• Company file stored on an external or USB drive: QuickBooks does not support storing company files on removable drives. If the drive was disconnected during a session or between sessions, Error 6123 occurs.
• File path permissions: If the Windows account running QuickBooks does not have full read/write access to the folder where the company file is stored, the 6123 error appears on every open attempt.
• Corrupted company file (.QBW): In cases where the .QBW file itself has internal damage, QuickBooks may fail to complete the connection and report Error 6123 rather than a more specific data error.

How to Fix QuickBooks Error 6123: Step-by-Step

Step 1: Run QuickBooks File Doctor (5 minutes)

Download and install QuickBooks Tool Hub from Intuit’s website, then open it. Click Company File Issues → Run QuickBooks File Doctor. When it opens, select your company file from the dropdown (or browse to it), choose Check your file and network, enter your QuickBooks Admin password, and click Next. File Doctor scans for .ND file damage, network connection issues, and file-level corruption simultaneously. This single step resolves Error 6123 in the majority of cases.

Step 2: Rename the .ND and .TG Files (2 minutes)

Navigate to the folder where your QuickBooks company file (.QBW) is stored. You will see two companion files with the same name but different extensions: CompanyFileName.ND and CompanyFileName.TG. Right-click each and rename them by adding “.old” to the end (e.g., CompanyFileName.ND.old). These files will be automatically recreated the next time QuickBooks opens. This forces QuickBooks to build a fresh network descriptor, which clears most .ND-related causes of Error 6123. Restart QuickBooks and try opening your company file.

Step 3: Copy the Company File to the Desktop (3 minutes)

If you are accessing the file over a network, copy the .QBW file to the local Desktop of the computer you are working on. Try opening it from there. If it opens successfully, the problem is with the network path or the shared drive setup — not the file itself. This also rules out permissions issues related to the server folder. Once confirmed working locally, work with your IT setup to fix the network share or move the file to a supported location.

Step 4: Restart QuickBooks Database Server Manager (3 minutes)

On the host computer (the computer that stores the company file), open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager. If the service is listed as stopped, click Start. If it is already running, click Restart. Then click Scan Folders and add the folder where your company file is stored. This rebuilds the .ND file and re-registers the file with the Database Server Manager. After the scan completes, return to the client computer and try opening the company file again.

Step 5: Add QuickBooks Firewall Exceptions

Open Windows Firewall with Advanced Security (search for it in the Start menu). Check Inbound Rules for QuickBooks — the required ports are 8019, 56728, and 55378-55382. If these are not listed or are blocked, add new inbound rules for each port (TCP). Also add an exception for the QuickBooks executable (QBW32.exe) in both inbound and outbound rules. If you have a third-party antivirus like Norton, McAfee, or Bitdefender, add QuickBooks as a trusted application in its firewall settings as well. Restart QuickBooks after making these changes.

Step 6: Check Windows Folder Permissions

Right-click the folder containing your company file → Properties → Security tab. Verify that the Windows user account running QuickBooks has Full Control listed. If not, click Edit → select the user → check Full Control → click Apply. Also verify that the QBDataServiceUser account (created by QuickBooks Database Server Manager) has Full Control. Incomplete permissions cause Error 6123 on every open attempt.

Still Not Working After All Steps?

If Error 6123 persists after all six steps, the company file itself may have internal corruption beyond what File Doctor can repair. Use QuickBooks Auto Data Recovery (ADR): in the folder with your company file, look for a subfolder named QuickBooksAutoDataRecovery. It contains a backup copy of the file (the .QBW.adr file). Copy it to a new folder, remove the .adr extension so it becomes a .QBW file, and try opening it in QuickBooks. If ADR is not available, restore from the most recent backup (File → Restore Company → Restore a Backup Copy). After a successful restore, run a Verify Data check (File → Utilities → Verify Data) to confirm file integrity before resuming work.

Prevent QuickBooks Error 6123 in the Future

• Back up your company file daily. Use QuickBooks automatic backup (File → Back Up Company → Create Local Backup → Schedule Future Backups). Keep at least 3 recent backups. Error 6123 caused by file corruption is only truly recoverable with a clean backup.
• Never store the company file on an external or USB drive. Store it on a local hard drive or a stable server with a static network path. QuickBooks requires a consistent, persistent connection to the file location.
• Keep QuickBooks and Windows updated. After major Windows updates, the .ND file occasionally breaks. Running a quick File Doctor scan after any Windows feature update takes 5 minutes and prevents unexpected Error 6123 appearances. For a related file access issue, see our QuickBooks company file not found fix. If you are also seeing broader QuickBooks stability problems, our QuickBooks Error 6000 guide covers overlapping causes and solutions.

Frequently Asked Questions

What does QuickBooks Error 6123 mean exactly?

Error 6123, 0 means QuickBooks lost or cannot establish the connection to your company file. The “0” is a secondary code indicating the specific sub-type of connection failure. In practice it means QuickBooks found the file path but could not complete the open or restore operation — usually because the Network Descriptor file is damaged, the Database Server Manager is not active, or the file itself has corruption. It is a connection error, not a data loss event, in most cases.

How long does the Step-by-Step fix take?

Steps 1 through 4 — File Doctor, renaming .ND/.TG files, testing locally, and restarting Database Server Manager — take about 15 minutes total and resolve Error 6123 for most users. Steps 5 and 6 (firewall exceptions and permissions) add another 10-15 minutes if needed. The entire process from start to working company file access typically takes under 30 minutes, and none of the steps require reinstalling QuickBooks or Windows.

Will fixing Error 6123 affect my QuickBooks data?

No. Renaming the .ND and .TG files, restarting Database Server Manager, running File Doctor, and adjusting firewall or permissions settings do not touch the company file data. Your transactions, accounts, and reports are stored in the .QBW file, which none of these steps modify. The only step that touches the .QBW file is Auto Data Recovery or a backup restore — but those are only used if the file is genuinely corrupted, and they replace it with a known-good copy.

Can QuickBooks Error 6123 cause data loss?

In the vast majority of cases, no — Error 6123 is an access failure, not a data corruption event. QuickBooks simply cannot open or connect to the file. However, if the error was triggered by an abrupt shutdown or drive failure, there is a small risk that the company file itself sustained damage during that event. This is why running File Doctor and then a Verify Data check after resolving the error is good practice — it confirms the file is clean before you continue entering transactions.