QuickBooks Error 6123 on Windows 11 — Step-by-Step Fix
QuickBooks error 6123 means QuickBooks failed to open or connect to the company file. On Windows 11, this error most commonly appears after a system update disrupts the QuickBooks database connection, or when a company file stored on a network drive loses its hosting configuration. The full message reads: “Error -6123, 0: Connection to the QuickBooks company file has been lost.” This guide walks through every fix in order.
- Root cause: QuickBooks error 6123 is triggered by a broken connection to the company file — caused by a stopped database service, firewall blocking, network path change, or file corruption
- Fastest fix: Run QuickBooks File Doctor from Tool Hub → it diagnoses and repairs the database connection in most cases within 5 minutes
What Causes QuickBooks Error 6123 on Windows 11?
Error 6123 is specifically a database connection error, not a file corruption error — your data is almost always intact. The connection breaks for one of these reasons:
- Windows 11 update broke the database service: Major Windows 11 updates can stop the QuickBooks Database Server Manager service or reset firewall rules that allow QuickBooks to communicate on the network.
- Company file moved or renamed: If the .QBW file was moved to a different folder, or the drive letter of a network location changed, QuickBooks cannot find the path it last used.
- Multi-user hosting conflict: If two computers on the network both have hosting mode turned on, error 6123 appears when a workstation tries to open the file being hosted by both machines simultaneously.
- Damaged .ND or .TLG file: QuickBooks creates a Network Descriptor (.ND) file alongside every company file. If this file is damaged, the database connection fails with error 6123 even though the company file itself is fine.
How to Fix QuickBooks Error 6123 on Windows 11: Step-by-Step
Step 1 — Run QuickBooks File Doctor (5 minutes)
- Download and open QuickBooks Tool Hub from Intuit’s support site.
- Click Company File Issues → Run QuickBooks File Doctor.
- Select your company file from the dropdown — if it does not appear, click Browse and navigate to the .QBW file.
- Choose “Check your file and network” → click Continue.
- Enter your QuickBooks Admin password → click Next.
- Wait for the scan to complete (3–5 minutes) → restart QuickBooks and try opening the file.
File Doctor repairs damaged .ND files, restores broken network connections, and fixes the most common causes of error 6123 automatically. This resolves the issue in the majority of cases on the first attempt.
Step 2 — Delete and Recreate the .ND File
- Navigate to the folder where your company file (.QBW) is stored.
- Look for a file with the same name as your company file but ending in .ND (for example, MyCompany.QBW.ND).
- Right-click the .ND file → Delete (or rename it to .ND.OLD to keep a backup).
- Open QuickBooks on the host computer → go to File → Utilities → Host Multi-User Access.
- QuickBooks will automatically recreate a fresh .ND file.
- Try opening the company file again from a workstation.
The .ND file is a small configuration file — deleting it does not affect your company data at all. QuickBooks rebuilds it instantly when hosting mode is activated on the host computer.
Step 3 — Restart the QuickBooks Database Server Manager
- On the host computer (the machine that stores the company file), press Windows + R → type
services.msc→ press Enter. - Find QuickBooksDB34 (the number varies by version — 34 for 2024, 33 for 2023, 32 for 2022).
- Right-click → Restart.
- Right-click → Properties → set Startup type to Automatic → click OK.
- Return to any workstation and try opening the company file.
Step 4 — Open the Company File Locally on the Host Computer
- Go directly to the host computer that stores the .QBW file.
- Open QuickBooks on that machine.
- Go to File → Open or Restore Company → Open a company file.
- Navigate to the local folder (not a network path) and open the .QBW file directly.
- If it opens without error locally, the problem is network-related (firewall or sharing permissions), not the file itself.
Opening locally confirms whether the company file is intact. If it opens on the host, move to Step 5 to fix the network connection. If it fails locally too, skip to Step 6. For errors that prevent the company file from being found at all, see our guide on QuickBooks company file not found.
Step 5 — Re-Add QuickBooks Firewall Exceptions on Windows 11
- On the host computer, open Windows Defender Firewall → Advanced settings.
- Click Inbound Rules → New Rule → Port → TCP.
- Enter ports:
8019, 56728, 55378, 55379, 55380, 55381, 55382→ click Next. - Select Allow the connection → check all three profiles → name the rule QuickBooks Ports → Finish.
- Repeat for Outbound Rules.
- Also open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager → click Scan Folders → add the folder with your company file → Scan.
Step 6 — Restore the Company File from Backup
- If the file fails to open even locally, go to File → Open or Restore Company → Restore a backup copy.
- Choose Local backup → browse to your most recent .QBB backup file.
- Restore it to a new file name (e.g., MyCompany_Restored.QBW) to avoid overwriting anything.
- Open the restored file and verify your data is intact.
QuickBooks creates automatic local backups by default. Check Documents\Intuit\QuickBooks\Company Files\Backup for recent .QBB files. For related multi-user errors on Windows 11, see our guide on QuickBooks error H202.
Still Not Working?
- Check that only one computer has hosting on: Open QuickBooks on every computer on the network → File → Utilities. Any machine showing “Stop Hosting Multi-User Access” has hosting turned on. Turn it off on all machines except the designated host.
- Move the company file to C:\Users\Public\Documents\Intuit\QuickBooks: Intuit recommends this location. Files stored in deeper custom folders or on drives with restricted permissions are more prone to error 6123. Moving the file to the standard path and re-scanning in Database Server Manager often resolves persistent errors.
- Run QuickBooks as Administrator: Right-click the QuickBooks shortcut → Run as administrator. Windows 11’s stricter UAC policies sometimes block QuickBooks from accessing network paths without elevated permissions.
Prevent QuickBooks Error 6123 in the Future
- Enable automatic backups: Go to File → Back Up Company → Create Local Backup → Options → set automatic backup every 1–5 saves. A recent backup makes recovery from any 6123 incident trivial.
- Re-scan after Windows 11 updates: After any major Windows 11 update, open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager → Scan Folders. This refreshes the .ND file and confirms the database connection is still working before the error appears.
- Keep the QuickBooks version current: Intuit releases compatibility patches within weeks of major Windows 11 updates. Go to Help → Update QuickBooks Desktop after any Windows feature update to get the latest Windows 11 fixes.
Frequently Asked Questions
Does QuickBooks error 6123 mean my company file is corrupted?
Not usually. Error 6123 is a connection error, not a file corruption error. It means QuickBooks cannot reach the company file — but the file itself is almost always intact. Confirm this by opening the file directly on the host computer (Step 4). If it opens locally without error, your data is fine and the problem is a network or configuration issue, not file damage.
Why does error 6123 appear only on Windows 11 and not on Windows 10?
Windows 11 introduced stricter firewall rules, tighter UAC (User Account Control) policies, and changed how network services handle authentication. These changes can block QuickBooks’ database connection even when the same setup worked perfectly on Windows 10. Re-adding firewall exceptions (Step 5) and running as Administrator resolves most Windows 11-specific 6123 occurrences.
Can I fix error 6123 without IT support?
Yes — all six steps above require only basic Windows navigation. QuickBooks File Doctor (Step 1) is entirely automated. Deleting the .ND file (Step 2) takes 30 seconds. Restarting the database service (Step 3) uses the standard Windows Services interface. Most users resolve error 6123 within 10–15 minutes using Steps 1–3 alone.
How do I know if my QuickBooks backup is recent enough to restore from?
Open Windows Explorer → navigate to Documents\Intuit\QuickBooks\Company Files\Backup. Sort by Date Modified. QuickBooks names backup files with the date embedded: CompanyName (Backup Jun 14 2026).QBB. The most recent file is your best restore point. If your last backup is more than a few days old, contact your accountant before restoring to understand what transactions may need to be re-entered.
Frequently Asked Questions
What Causes QuickBooks Error 6123 on Windows 11?
Error 6123 is specifically a database connection error, not a file corruption error — your data is almost always intact. The connection breaks for one of these reasons:



