QuickBooks Error 6123: what it means & how to fix it.
Error 6123, 0 means QuickBooks Desktop can’t open or restore the company file because the connection to it is broken — one of the most common 6000-series errors, and one that often appears after a Windows or QuickBooks update, when restoring a backup, or when opening a file over a network. Below: the causes in order of likelihood, the six-step self-fix, and when to call a Certified ProAdvisor. Independent firm, not affiliated with Intuit Inc.
Error 6123, 0 appears when QuickBooks Desktop loses or cannot establish the connection to the company file — usually while opening a file, restoring a backup, or opening a file over a network. The error frequently surfaces right after a Windows or QuickBooks update, or when a file is moved or restored across machines. Six causes account for the large majority, and the self-fix steps work in order of likelihood; QuickBooks Tool Hub resolves Error 6123 in many cases. Error 6123 is a QuickBooks Desktop and Enterprise error — it does not appear in QuickBooks Online.
Reference maintained by the Certified QuickBooks ProAdvisor team at TechBrot Inc., an independent firm — not Intuit’s software support. Not affiliated with Intuit Inc.
Error 6123, in five questions.
What is QuickBooks Error 6123?
A QuickBooks company-file connection error (a 6000-series code, usually shown as “Error 6123, 0”): QuickBooks Desktop can’t open or restore the company file because its connection to that file is broken. It often appears when opening a file, restoring a backup, or opening a file over a network. Exclusive to QuickBooks Desktop and Enterprise — it does not occur in QuickBooks Online.
What causes Error 6123?
Six causes account for the large majority: (1) a damaged network connection or multi-user/hosting setup; (2) a firewall or antivirus blocking QuickBooks; (3) opening a file from a different QuickBooks version or a restored backup; (4) damaged .ND/.TLG files or a damaged company file; (5) Windows user-permission issues; (6) a file moved or restored across machines.
Can I fix Error 6123 myself?
Often yes, in order of likelihood: run QuickBooks Tool Hub (Quick Fix My File, then File Doctor); rename the .ND and .TLG files; confirm hosting/multi-user configuration; check firewall and antivirus; try opening a sample file or a local copy; restore from a clean backup. Tool Hub alone clears Error 6123 in many cases.
When does Error 6123 need a ProAdvisor?
When self-fix doesn’t resolve it within an hour or two, the error recurs within days, it appears alongside other 6000-series codes, you can’t open the file even locally, or the file is genuinely damaged — a signal the company file itself needs professional repair.
How is Error 6123 related to other 6000-series codes?
The 6000-series are all company-file errors — QuickBooks can’t open or access the file. 6123, 0 is a broken-connection error tied to network paths, hosting, security software, version/restore mismatches, or file damage. Codes like 6000 77, 6000 83, and 6190 share the same diagnostic approach: repair the connection, then the file.
Certified QuickBooks ProAdvisor credentials.
4
core QuickBooks platforms certified — Desktop, Enterprise, Online (Level 2), Payroll
L2
QuickBooks Online ProAdvisor tier (the highest)
Yearly
Annual Intuit re-certification
- Error 6123 is a Desktop/Enterprise company-file error — resolving it takes fluency in hosting, network paths, .ND/.TLG files, and file-integrity repair.
- Every ProAdvisor holds active Desktop and Enterprise certifications; Intuit’s public ProAdvisor directory lists active ProAdvisors for verification.
- Operational experience to diagnose Error 6123 past the documented surface steps — not a script-reading queue.
Error 6123, plainly.
Error 6123, 0 appears when QuickBooks Desktop can’t open or restore the company file because the connection to that file is broken. You most often see it while opening a file, restoring a backup, or opening a file stored on another computer over a network — and it commonly shows up immediately after a Windows or QuickBooks update, or after a file has been moved or restored across machines. The error is QuickBooks telling you it reached for the file and the path to it failed, whether that’s a network/hosting issue, a security program blocking access, a version or restore mismatch, or genuine damage to the file or its supporting .ND/.TLG files.
The good news is that Error 6123 is highly fixable, and the self-fix steps below work in order of likelihood — running QuickBooks Tool Hub (Quick Fix My File, then File Doctor) resolves it in many cases before deeper troubleshooting is needed. If self-fix doesn’t resolve it within an hour or two, or the error recurs within days, a Certified ProAdvisor diagnostic identifies the deeper cause — typically configuration or file-integrity damage past the documented surface steps. Error 6123 is a QuickBooks Desktop and Enterprise error; it does not appear in QuickBooks Online.
Six common causes, in order of likelihood.
The self-fix steps address these in the same order — so working through them sequentially resolves Error 6123 efficiently.
Cause 01 · Damaged network connection or hosting setup
The most common cause. When the company file lives on another computer or server, a broken network connection or a misconfigured multi-user/hosting setup stops QuickBooks from reaching the file — Error 6123, 0. Opening the file over an unstable network path is a frequent trigger.
Cause 02 · Firewall or antivirus blocking QuickBooks
Windows Firewall or third-party antivirus blocks the executables or ports QuickBooks needs to reach the company file. This often appears right after a security-software or Windows update changes the rules. The fix is explicit exceptions for the QuickBooks program files and ports.
Cause 03 · Different QuickBooks version or restored backup
Opening a file created in a newer QuickBooks year-version, or restoring a backup made on a different machine or version, can produce Error 6123, 0. The file and the program disagree about version or location, and the connection fails.
Cause 04 · Damaged .ND/.TLG files or company file
A corrupted network-data (.ND) or transaction-log (.TLG) file — or genuine integrity damage to the company (.QBW) file itself — breaks the connection QuickBooks needs to open it. This is where surface steps stop working and a diagnostic is warranted.
Cause 05 · Windows user-permission issues
The Windows account QuickBooks runs under lacks the permissions needed to read or write in the folder holding the company file. Permission changes after an update, a new user profile, or a relocated folder can all surface as Error 6123.
Cause 06 · File moved or restored across machines
Moving the company file to a new computer, or restoring it onto different hardware, can break the path and the supporting files QuickBooks expects — producing Error 6123, 0 the first time the file is opened on the new machine.
How to fix Error 6123 yourself.
Six steps, in order. Most Error 6123 cases clear within the first two — if all six don’t resolve it, stop and book a diagnostic.
Run QuickBooks Tool Hub (Quick Fix My File, then File Doctor)
Open QuickBooks Tool Hub → Company File Issues → Quick Fix My File, then run QuickBooks File Doctor. This alone resolves Error 6123 in many cases by repairing the connection, hosting, and file settings automatically. Run it on the computer that stores the file when possible.
Rename the .ND and .TLG files
In the folder with your company file, rename the matching .ND and .TLG files (add .OLD to the end). QuickBooks rebuilds them automatically on the next open. This clears corruption in those supporting files without touching the company file itself.
Confirm hosting / multi-user configuration
If the file is shared, make sure only the host computer is set to host multi-user access and that Database Server Manager is running there. A workstation mistakenly set to host, or a stopped service, breaks the connection that Error 6123 reports.
Check firewall and antivirus
Add exceptions for the QuickBooks program files and ports in Windows Firewall and any third-party antivirus, or temporarily disable the security software to test. If the file opens with protection off, create permanent rules so the block doesn’t return after a reboot.
Try a sample file or a local copy
Open a QuickBooks sample file to confirm the program itself works. Then copy your company file to the local Desktop and open it there. If the local copy opens, the issue is the network path, permissions, or hosting — not the file. If the sample fails too, the install needs repair.
Restore from a clean backup, then escalate
If Error 6123 persists, restore from a known-good backup created before the error began. If the error survives even a clean restore, stop — continued retries can mask deeper damage. A Certified ProAdvisor diagnostic identifies the underlying cause and resolves it against a written scope.
Self-fix didn’t clear Error 6123?
A Certified ProAdvisor diagnoses the deeper cause — typically a $1,200–$3,000 fixed-fee scope. Independent firm.
Three signals it’s a ProAdvisor call.
It persists after all six steps
You’ve worked the ordered fix and Error 6123 still blocks the file. The cause is past the documented surface — usually network/permission configuration or genuine company-file integrity damage.
It keeps coming back
Error 6123 clears, then returns within days. A recurring error signals an underlying configuration, security-software, or file-integrity problem that a one-time fix masks rather than resolves.
It’s appearing alongside other 6000-series codes
Error 6123 alongside 6000 77, 6000 83, 6190, or other 6000-series codes points to deeper company-file integrity problems — the moment to stop self-fixing and have the file assessed before damage progresses.
A Certified ProAdvisor diagnoses past the surface.
When the documented steps don’t hold, the cause is usually past the surface — a damaged network-data (.ND) or transaction-log (.TLG) file, a version or restore mismatch, a security program that re-blocks access after each reboot, or genuine company-file integrity damage. A Certified ProAdvisor with active Desktop and Enterprise certifications diagnoses the actual root cause, fixes it against a written scope, and verifies the file opens cleanly before closing. Independent firm — not Intuit, and not Intuit’s software support.
Diagnostic
30-minute diagnostic, usually scheduled within a day
$1,200–$3,000
typical fixed-fee scope for focused Error 6123 resolution
Independent
Certified ProAdvisor firm — not Intuit, not Intuit’s software support
What people ask about Error 6123.
Is this Intuit’s official support?
What is QuickBooks Error 6123?
What causes QuickBooks Error 6123?
Can I fix QuickBooks Error 6123 myself?
When does Error 6123 require a ProAdvisor?
How is Error 6123 related to the other 6000-series errors?
Does Error 6123 appear in QuickBooks Online?
Self-fix didn’t resolve it?
Self-fix didn’t work? Book a diagnostic.
If Error 6123 persists after the six steps, recurs within days, or shows up alongside other 6000-series codes, a 30-minute diagnostic surfaces the real cause — typically a $1,200–$3,000 fixed-fee scope for focused resolution. Independent ProAdvisor firm, written scope before any work begins.