
QuickBooks Error 6123 is one of the most disruptive company-file errors that QuickBooks Desktop users can encounter. In brief, this error appears when QuickBooks is unable to open, restore, or create a company file, typically because the file is stored on a network, is being accessed by multiple users simultaneously, or has been corrupted. The error message usually reads: “Error -6123, 0: Connection to the QuickBooks company file has been lost.”
The good news is that this error is fixable. With the right troubleshooting steps — ranging from running QuickBooks File Doctor to reconfiguring your network settings — most users can resolve it without data loss. This guide covers every verified cause and solution so you can get back to work quickly.
Also read in detail:- QuickBooks Error 6000 Series
What Is QuickBooks Error 6123?
QuickBooks Error 6123 belongs to the -6000 series of company-file errors, all of which relate to problems accessing the .QBW (QuickBooks for Windows) company file. Error 6123 specifically signals that the connection between QuickBooks and the company file was interrupted or could never be established.
This error commonly surfaces in the following scenarios:
- Opening a company file stored on a network drive or server.
- Restoring a company file backup (.QBB).
- Upgrading QuickBooks to a newer version.
- Moving or renaming the company file or its folder.
- Multiple users attempting to access the same file at the same time.
Common Causes of QuickBooks Error 6123
Understanding the root cause is the first step toward a permanent fix. Here are the most frequently identified causes:
1. Network or Hosting Configuration Issues
QuickBooks uses a Database Server Manager to share company files across a network. If the server is not configured correctly, or if the QuickBooksDBXX service (where XX is your version year) is not running, Error 6123 will appear every time a workstation tries to connect.
2. Damaged or Corrupted Company File
If the .QBW file or its transaction log (.TLG) file is corrupted, due to an improper shutdown, power failure, or disk error, QuickBooks cannot read the file and throws Error 6123.
3. Firewall or Security Software Blocking QuickBooks
Windows Firewall or third-party antivirus programs can block the ports QuickBooks uses to communicate. When these ports are blocked, the company-file connection is dropped, triggering the error.
4. Damaged .ND or .TLG Support Files
QuickBooks creates two support files alongside every company file: the Network Descriptor (.ND) and the Transaction Log (.TLG). If either of these becomes corrupted, the application cannot locate or lock the company file properly.
5. Insufficient Windows Permissions
If the Windows user account running QuickBooks does not have full Read/Write access to the folder where the company file is saved, the connection will fail. This is especially common after system migrations or Group Policy changes.
6. Company File Already Open on Another System
In a multi-user environment, if one workstation crashes while a file is open, the file can remain locked. Subsequent attempts to open it from any machine will produce Error 6123 until the lock is cleared.
How to Fix QuickBooks Error 6123: Step-by-Step Solutions
Work through the solutions below in order. Each fix targets a specific cause, so start from the top and stop once the error is resolved.
Fix 1: Run QuickBooks File Doctor
QuickBooks File Doctor is Intuit’s official diagnostic tool for company-file and network errors. It can automatically repair damaged files and fix network configuration issues.
- Download QuickBooks Tool Hub.
- Open QuickBooks Tool Hub and click Company File Issues.
- Click Run QuickBooks File Doctor.
- Select your company file from the drop-down menu.
- Choose Check your file and network, then click Continue.
- Enter your QuickBooks Admin password when prompted and let the scan complete.
Fix 2: Delete and Recreate the .ND and .TLG Files
These support files are safe to delete, QuickBooks will regenerate them automatically when you reopen the company file.
- Open File Explorer and navigate to the folder containing your company file.
- Look for files with the same name as your company file but with .ND and .TLG extensions.
- Right-click each file and select Rename. Add .OLD to the end of the file name, this acts as a backup instead of deleting.
- Open QuickBooks and try to access the company file. QuickBooks will create fresh .ND and .TLG files automatically.
Fix 3: Copy the Company File to a Local Drive
If your company file is stored on a network share, temporarily moving it to a local drive helps isolate whether the issue is network-related.
- Copy the .QBW file to your local desktop or the C:\Users\Public\Documents\Intuit\QuickBooks\Company Files folder.
- Open QuickBooks and choose File > Open or Restore Company.
- Browse to the local copy and open it.
- If the file opens successfully, the problem is with your network path or server configuration.
Fix 4: Configure Windows Firewall for QuickBooks
If a firewall is blocking QuickBooks ports, add the necessary exceptions:
- Open Windows Defender Firewall from the Control Panel.
- Click Advanced Settings > Inbound Rules > New Rule.
- Select Port > TCP, then enter the required port numbers, 8019.
- Select Allow the Connection and apply to all profiles.
- Name the rule (e.g., QuickBooks Ports) and click Finish.
- Repeat the steps to create an Outbound Rule for the same ports.
Fix 5: Set Correct Folder Permissions
Make sure the company file folder grants full control to QBDataServiceUserXX (the QuickBooks service account):
- Right-click the folder containing your company file and select Properties.
- Click the Security tab, then click Edit.
- Add QBDataServiceUserXX (replace XX with your QuickBooks version).
- Check Full Control under Allow and click Apply > OK.
How to Prevent QuickBooks Error 6123 in the Future?
Prevention is always better than a fix. Follow these best practices to minimize the risk of encountering this error again:
- Schedule automatic backups: Use QuickBooks’ built-in backup scheduler to create daily local or online backups of your company file.
- Use a stable network: Avoid accessing QuickBooks company files over unstable Wi-Fi connections; wired (Ethernet) connections are far more reliable.
- Close QuickBooks properly: Always use File > Close Company / Logoff before shutting down your computer or disconnecting from the network.
- Use QuickBooks-compatible UPS: A battery backup (Uninterruptible Power Supply) prevents abrupt shutdowns during power outages that can corrupt the company file.
- Limit simultaneous users: Only allow the number of concurrent users that your QuickBooks license supports; exceeding this causes connection conflicts.
- Keep Windows updated: Outdated Windows versions can introduce permission and security conflicts that affect QuickBooks file access.
Conclusion
QuickBooks Error 6123 can feel overwhelming, but with the structured troubleshooting steps outlined in this guide, the majority of users can resolve it in under an hour. Start with QuickBooks File Doctor, it handles the most common causes automatically. If that does not work, follow the manual steps: rename your .ND and .TLG files, check folder permissions, configure your firewall, and restart the Database Server Manager.
Should the error prove unresolvable through self-service steps, do not hesitate to reach out to at +1 (800) 217-0394 for expert assistance.
Advanced external solutions:- Fix error -6000 when opening a company file
FAQs
Can QuickBooks Error 6123 occur in single-user mode?
Yes, although it is more common in multi-user environments, it can also appear in single-user mode due to file corruption or system issues.
What is the QuickBooks File Doctor tool?
QuickBooks File Doctor is a built-in repair tool available in QuickBooks Tool Hub that helps fix company file and network-related issues automatically.
Does firewall configuration affect Error 6123?
Yes, firewall or antivirus settings can block QuickBooks from accessing the company file, leading to this error. Proper port configuration and exceptions are necessary.
Can a damaged company file cause Error 6123?
Yes, file corruption is one of the most common causes. Running repair tools or restoring a backup file can help resolve the issue.
Is it safe to restore a backup file to fix Error 6123?
Yes, restoring a recent backup is a safe and effective solution if the current company file is corrupted.

Brown Lopez is a Cloud Engineer and technical writer based in Austin, USA, who enjoys turning complex cloud ideas into clear, simple insights. With solid experience in cloud architecture and real-world projects, he loves creating practical content that helps professionals understand, build, and improve their cloud solutions with confidence.