Why is my QuickBooks Desktop Pro 2022 Error 6123?

Common causes include software issues, connectivity problems, and settings misconfigurations. Follow our guide to fix your QuickBooks Desktop Pro 2022.

How do I fix QuickBooks Desktop Pro 2022 Error 6123?

Start by restarting your device, checking connections, and updating firmware. Our step-by-step guide provides detailed instructions.

When should I call support for my QuickBooks Desktop Pro 2022?

If troubleshooting doesn't resolve the issue, or you encounter persistent errors, contact a certified QuickBooks technician.

QuickBooks Desktop Pro 2022 Error 6123

QuickBooks Desktop Pro 2022 Error 6123 typically appears when you're trying to open a company file, restoring a backup, or accessing your data over a network connection. This error is accompanied by the message "Connection to the QuickBooks company file has been lost" and can stop your workflow completely. The good news is that Error 6123 is usually fixable with a few targeted troubleshooting steps. This guide walks you through proven solutions to restore access to your company file and get back to managing your business finances.

What Causes Error 6123 in QuickBooks Desktop Pro 2022?

Several factors can trigger QuickBooks Desktop Pro 2022 Error 6123. Understanding the root cause helps you choose the most effective fix. Common causes include damaged network data files (.ND), corrupted company files, firewall or antivirus blocking QuickBooks communication, outdated QuickBooks Desktop Pro 2022 software, and issues with the QuickBooks Database Server Manager. Sometimes, the error occurs after renaming a company file or moving it to a new location without updating the file path properly.

Step-by-Step Solutions to Fix Error 6123

Restart Your Computer and Server: Begin by restarting the computer where your company file is stored, plus any workstations showing the error. This clears temporary glitches in network connections and releases locked file processes. Wait for the host computer to fully boot before attempting to open QuickBooks again.

Rename the Network Data (.ND) and Transaction Log (.TLG) Files: Navigate to your company file folder. Locate files with the same name as your company file but with .ND and .TLG extensions. Right-click each file, select Rename, and add ".old" to the end (for example, CompanyFile.qbw.ND becomes CompanyFile.qbw.ND.old). QuickBooks will rebuild these files automatically the next time you open your company file.

Move Your Company File to a Local Drive: If your file is on a network or external drive, copy it to your computer's local C: drive. Create a new folder directly on the C: drive, such as C:\QBTest, and paste your company file there. Try opening the file from this new location. If it opens successfully, the issue is with your network configuration rather than the file itself.

Use the QuickBooks File Doctor Tool: Download and run the QuickBooks Tool Hub if you haven't already. Open the Tool Hub, select Company File Issues, then click Run QuickBooks File Doctor. Choose your company file from the dropdown or browse to locate it. Select Check your file and network, then Continue. Enter your QuickBooks admin password and click Next. The scan may take up to 15 minutes depending on file size.

Update QuickBooks Desktop Pro 2022 to the Latest Release: Open QuickBooks on the host computer and go to Help > Update QuickBooks Desktop. Click Update Now, then Get Updates. Restart QuickBooks when prompted to install the updates. Also ensure all workstations are running the same QuickBooks version to prevent compatibility conflicts that trigger QuickBooks Desktop Pro 2022 Error 6123.

Configure Firewall and Antivirus Settings: Add QuickBooks as an exception in your Windows Firewall and any third-party antivirus software. Go to Windows Security > Firewall & network protection > Allow an app through firewall. Make sure QuickBooks Desktop Pro 2022 and QuickBooks Database Server Manager are checked for both Private and Public networks. If using antivirus software, consult your vendor's documentation for adding program exceptions.

Warning: Before attempting any repair procedures, create a backup of your company file. Go to File > Back Up Company > Create Local Backup and follow the prompts. Never rename your actual .qbw company file—only rename the .ND and .TLG support files. Working without a backup puts your financial data at risk if repairs go wrong.

Preventing Error 6123 in the Future

To minimize recurrence of QuickBooks Desktop Pro 2022 Error 6123, establish consistent maintenance habits. Run the QuickBooks File Doctor monthly to catch minor corruption early. Keep your software updated with the latest patches from Intuit. Store company files on reliable local or network drives with stable connections. Avoid renaming company files or moving them between locations without properly updating QuickBooks. Consider hosting your file on a dedicated server rather than a shared workstation to reduce network strain. Regular backups protect your data and give you a clean restore point if errors develop.

Still Need Help With Your QuickBooks Device?

If these steps didn't resolve the Error 6123 issue, our certified technicians can help.

Get Free Support Now →

Frequently Asked Questions

Can I fix Error 6123 without the QuickBooks Tool Hub?

Yes, manual fixes like renaming .ND and .TLG files, moving your company file locally, and updating firewall settings can resolve the error without using the Tool Hub. However, the File Doctor tool automates many repairs and is recommended for faster diagnosis.

Will I lose data when renaming .ND and .TLG files?

No, these are support files that QuickBooks rebuilds automatically. Your actual financial data resides in the .qbw company file, which you should never rename. The .ND file stores network configuration, and the .TLG file tracks transactions for recovery purposes.

Why does Error 6123 keep coming back after I fix it?

Recurring Error 6123 usually indicates an underlying network instability, outdated software, or persistent file damage. Check that all workstations run identical QuickBooks versions, verify your network hardware is functioning properly, and consider having your company file evaluated for deeper corruption if problems persist.