Sample workflow — not a specific client’s data
A real 6123 diagnostic
The written read-out that tells you whether it is a mismatch or genuine file damage.
Error 6123
QuickBooks error 6123: connection to the company file lost
Error 6123 means QuickBooks lost the connection to your company file, often while opening it or restoring a backup. Sometimes the cause is a network, antivirus, or multi-user version mismatch you can fix yourself. Sometimes it is genuine damage to the file, which needs repair. The first job is telling the two apart.
- We tell you: network fix or file repair
- Steps you can try yourself
- We escalate only real damage
Who this affects
6123 is the one error that really could go either way
6123 is unusual because it sits on the line between a simple fix and a serious one. You will often see it moving a file between computers, restoring a backup, or opening a file made in a different QuickBooks version. In those cases it is a mismatch you can resolve. But 6123 is also thrown by a genuinely damaged file, so it is the one error where you should not assume it is harmless.
Start here
6123 — a mismatch you can fix, or a damaged file?
MOVING OR RESTORING A FILE
Likely a DIY fix
Version mismatch, antivirus, or hosting during a restore causes many 6123s — the steps below clear them.
THE FILE WILL NOT OPEN AT ALL
Likely file damage
If 6123 blocks the file even on the machine that made it, with matching versions, corruption is the likely cause.
See file repairRead this as text
- MOVING OR RESTORING A FILE: Likely a DIY fix — Version mismatch, antivirus, or hosting during a restore causes many 6123s — the steps below clear them.
- THE FILE WILL NOT OPEN AT ALL: Likely file damage — If 6123 blocks the file even on the machine that made it, with matching versions, corruption is the likely cause.
Fix it yourself
The DIY fix for 6123, step by step
Work these in order. They rule out the network and version causes, which account for many 6123 messages, before you treat it as file damage.
-
Match the versions
Open the file with the same QuickBooks year and edition that created it. Restoring a newer file into an older program is a common 6123 trigger.
-
Restore locally
Copy the backup to the computer's local drive first, then restore. Restoring straight from a network drive or USB stick often drops the connection.
-
Pause antivirus
Temporarily turn off third-party antivirus and add QuickBooks as an exception. Security software can lock the file mid-restore and trigger 6123.
-
Turn off hosting during restore
On the machine doing the restore, switch hosting off so nothing else is holding the file, then restore into single-user mode.
-
Try the sample file
Open a QuickBooks sample company. If the sample opens but your file still throws 6123, the problem is your file, not the program.
When to call us
When 6123 means the file is damaged
If 6123 still blocks the file after you have matched versions, restored locally, and cleared antivirus — especially on the computer that created the file — the cause is the file itself. Repeated restore attempts on a damaged file can overwrite your last good backup, so stop there. A file repair recovers the data structure; a rescue is for a file that will not open or has already lost data. We work from a copy, read-only, so nothing gets worse while we diagnose.
How you can verify us
How we work
We test on a copy first, so a damaged file is never made worse. See what repair involves.
See QuickBooks file repairResponse commitment
A real specialist replies within one business day, in writing.
Questions about error 6123
Does 6123 always mean my file is corrupt?
No. Many 6123 messages come from a version mismatch, antivirus, or restoring over a network — all fixable without repair. But unlike most errors, 6123 is also a genuine corruption signal. If it persists after the simple steps, treat the file as damaged rather than retrying.
Why do I get 6123 when restoring a backup?
Restoring is where 6123 shows up most. Common causes are restoring a newer file into an older QuickBooks, restoring straight from a network drive or USB, or antivirus locking the file mid-restore. Restore locally, with matching versions and security paused, and it usually goes through.
Can I keep retrying the restore?
Not on a file you suspect is damaged. Each failed attempt can overwrite a good backup or write more bad data. Try the simple fixes once. If 6123 stays, stop and have the file diagnosed on a copy before you lose the last version that still opens.
Is 6123 different on multi-user setups?
It can be. In multi-user, 6123 often traces to a hosting or Database Server Manager conflict rather than a damaged file — closer to an H202 situation. Confirm hosting is set correctly on the server first. If single-user on the host still fails, then look at the file itself.
What is the difference between file repair and rescue for 6123?
File repair rebuilds the data structure of a file that still opens but throws errors. Rescue is for a file that will not open at all or has already lost data. 6123 can land in either camp, which is why we diagnose first and tell you which one your file actually needs.