OnCallSolve

How to Fix QuickBooks Error 6123

Error 6123
Hard
~30 min
QuickBooks Error Guide
How to Fix QuickBooks Error 6123
James Whitfield
Written by

James Whitfield

Small Business Technology Journalist
Michael Reyes

Reviewed byQuickBooks ProAdvisor

Published: Mar 9, 2026Updated: Mar 9, 2026

Key Takeaways
  • Error 6123 is a 6000-series company file access error triggered when QuickBooks cannot open the .qbw company file
  • Deleting the .ND and .TLG files (network descriptor and transaction log) forces QuickBooks to regenerate them cleanly and resolves most cases
  • The QuickBooks Database Server Manager must be running on the host computer for multi-user access to work
  • QuickBooks File Doctor (available in the QuickBooks Tool Hub) diagnoses and repairs both network and file integrity issues automatically
  • Firewall or antivirus software blocking QuickBooks ports or the company file folder causes a significant share of Error 6123 occurrences
  • All fixes in this guide apply to QuickBooks Desktop on Windows (Pro, Premier, Enterprise, Accountant editions)

QuickBooks Error 6123 (also written as -6123 0 or 6123 0) appears with the message "We're sorry. QuickBooks couldn't open your company file." It belongs to the 6000-series of company file access errors and surfaces when QuickBooks cannot open a company file in either single-user or multi-user mode. This guide covers fixes verified on QuickBooks Desktop 2022 through 2026 on Windows 10 and Windows 11. QuickBooks Desktop runs on Windows only; these steps do not apply to QuickBooks Online or Mac versions.

Need help? Call our support line.

A support agent can walk you through the fix step by step.

+1 (800) 446-8848

What Is QuickBooks Error 6123?

QuickBooks Error 6123, also displayed as -6123 0, is a 6000-series company file error that QuickBooks Desktop shows when it cannot access or open the company file (.qbw). The error dialog reads:

"We're sorry. QuickBooks couldn't open your company file. Try opening the file again. If the problem persists, contact Intuit Technical Support and provide them with the following error codes: (-6123, 0)."

The 6000-series covers a broad class of file access failures in QuickBooks Desktop. Error 6123 specifically signals that QuickBooks located the company file but failed to open it, most often because a supporting network descriptor file is damaged, a required service is not running, or a firewall is blocking access.

The error appears in both single-user and multi-user mode. In single-user mode it typically points to a corrupted .ND file or antivirus interference. In multi-user mode it more often indicates that the QuickBooks Database Server Manager is not running or that network connectivity to the host is broken.

Symptoms

You may be dealing with Error 6123 if you see:

  • The error message "We're sorry. QuickBooks couldn't open your company file" with codes (-6123, 0)
  • QuickBooks crashes immediately when you attempt to open the company file
  • The error appears only when accessing the company file from a network location (mapped drive or UNC path)
  • Single-user mode fails on the local machine where the file is stored
  • Multi-user mode fails on workstations while the host can open the file, or vice versa
  • The error appeared after a Windows update, antivirus update, or QuickBooks version upgrade
  • QuickBooks prompts to switch to single-user mode but then still shows the error

Root Causes

1. Damaged or Stale .ND and .TLG Files

Every QuickBooks company file has two companion files in the same folder: a .ND file (network descriptor, with extension `.qbw.nd`) and a .TLG file (transaction log, with extension `.qbw.tlg`). The .ND file maps the company file to the correct host computer on the network. If it is corrupted, points to an old IP address, or was generated by a different version of QuickBooks, Error 6123 results. Deleting both files is safe because QuickBooks regenerates them automatically on the next successful open.

2. QuickBooks Database Server Manager Not Running

In multi-user mode, the QuickBooksDBXX Windows service (where XX corresponds to your version year) manages all company file connections. If this service has stopped due to a system restart, a Windows update, or resource pressure, no workstation can open the company file and Error 6123 appears across the network.

3. Firewall or Antivirus Blocking Access

Windows Firewall and third-party security software can block the ports and file paths that QuickBooks requires. Antivirus programs sometimes quarantine or lock .ND, .TLG, or .qbw files during a background scan, causing Error 6123 to appear even when the file itself is undamaged.

Need help? Call our support line.

A support agent can walk you through the fix step by step.

+1 (800) 446-8848

4. Incorrect Hosting Configuration

If hosting is enabled on a workstation instead of (or in addition to) the server, the network descriptor files conflict and QuickBooks cannot determine which machine holds the authoritative company file. This creates the same symptom as a damaged .ND file.

5. Company File Moved or Renamed

If the company file was moved, renamed, or the folder path changed without updating QuickBooks preferences, the program looks in the old location and fails with Error 6123. This is common after a file server migration or a Windows upgrade that changed drive letter assignments.

Before You Begin

  • Confirm which computer is the host (the machine where the .qbw file is stored and where QuickBooks Database Server Manager is installed)
  • Identify your QuickBooks Desktop version year (2022, 2023, 2024, or 2025); you will need it in the services check
  • Ensure you have Windows administrator privileges on the host computer
  • Back up the company file before making any changes. Copy the .qbw file to an external drive or a separate folder
  • Apply all fixes on the host computer first, then test from workstations
  • These steps apply to QuickBooks Desktop on Windows only; they do not apply to QuickBooks Online

Step-by-Step Fix

Work through these methods in order. The majority of Error 6123 cases are resolved by Method 1 or Method 2.

Method 1: Delete the .ND and .TLG Files

Deleting the companion files forces QuickBooks to regenerate them on next open. This is the single fastest fix for Error 6123 and resolves the majority of cases.

  1. Close QuickBooks completely on all computers that access the company file
  2. Open File Explorer and navigate to the folder containing your company file (.qbw). The default path is `C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\`
  3. In the same folder, locate the two companion files:

- `[YourCompanyName].qbw.nd`

- `[YourCompanyName].qbw.tlg`

  1. Right-click each file and select Delete (or rename them by adding `.old` to the extension if you prefer to keep a backup)
  2. Close File Explorer
  3. Open QuickBooks and try to open the company file. QuickBooks will regenerate both files automatically

If the error persists after regeneration, proceed to Method 2.

Method 2: Run QuickBooks File Doctor (Tool Hub)

QuickBooks File Doctor diagnoses both network configuration issues and company file integrity problems. It automatically repairs the .ND file and adjusts firewall settings in one pass.

  1. Download the latest QuickBooks Tool Hub from the official Intuit download page
  2. Run `QuickBooksToolHub.exe` and follow the installer prompts. Accept the license agreement and complete the installation
  3. Open QuickBooks Tool Hub from the desktop icon
  4. Click Company File Issues in the left panel
  5. Click Run QuickBooks File Doctor
  6. In the File Doctor window, select your company file from the dropdown. If it does not appear, click Browse and navigate to the .qbw file
  7. Select Check your file and network (not just file)
  8. Enter your QuickBooks administrator password when prompted
  9. Click Next and wait for the scan to complete. The scan can take up to 5 minutes depending on file size
  10. When the scan finishes, open QuickBooks and attempt to open the company file

Method 3: Verify QuickBooks Database Server Manager Is Running

These steps must be performed on the host computer where the company file is stored.

Check and start the service:

  1. Press Windows + R, type `services.msc`, and press Enter
  2. Scroll to find the QuickBooks database service. Use this version mapping:

- QuickBooksDB36 = QuickBooks 2026

- QuickBooksDB35 = QuickBooks 2025

- QuickBooksDB34 = QuickBooks 2024

- QuickBooksDB33 = QuickBooks 2023

- QuickBooksDB32 = QuickBooks 2022

  1. Right-click the service and select Properties
  2. Set Startup type to Automatic
  3. If the service status shows Stopped, click Start
  4. Click the Recovery tab, set First failure to Restart the Service, then click OK
  5. Repeat steps 2 through 6 for QBCFMonitorService
  6. Close the Services window

Rescan the company file folder:

  1. Open QuickBooks Tool Hub
  2. Click Network Issues
  3. Click QuickBooks Database Server Manager
  4. Click Browse, navigate to the company file folder, and click OK
  5. Click Start Scan. This rebuilds the .ND file and refreshes firewall permissions
  6. When the scan completes, test opening the company file from a workstation

Method 4: Correct Hosting Settings

Hosting must be active only on the server, not on any workstation.

On each workstation:

  1. Open QuickBooks Desktop
  2. Go to File > Utilities
  3. If you see "Stop Hosting Multi-User Access", click it to turn hosting off on this workstation
  4. If you see "Host Multi-User Access", hosting is already off; no action needed
  5. Repeat on every workstation

On the host/server computer:

  1. Open QuickBooks Desktop
  2. Go to File > Utilities
  3. If you see "Host Multi-User Access", click it to enable hosting
  4. If you see "Stop Hosting Multi-User Access", hosting is already on; no action needed

After correcting hosting, try opening the company file. If Error 6123 persists, continue to Method 5.

Need help? Call our support line.

A support agent can walk you through the fix step by step.

+1 (800) 446-8848

Method 5: Add Firewall and Antivirus Exceptions

Windows Firewall:

  1. Open Control Panel > System and Security > Windows Defender Firewall
  2. Click Allow an app or feature through Windows Defender Firewall
  3. Click Change Settings (requires administrator privileges)
  4. Click Allow another app
  5. Browse and add each of the following QuickBooks executable files:

- `QBDBMgrN.exe` (Database Manager)

- `QBW32.exe` (QuickBooks main application)

- `QBCFMonitorService.exe`

  1. Check both Private and Public for each program
  2. Click OK

For the full list of ports required by your QuickBooks version, see the Intuit firewall configuration guide.

Antivirus software:

Add the following folders and files to your antivirus exclusion list:

  • The company file folder (e.g., `C:\Users\Public\Documents\Intuit\QuickBooks\`)
  • `QBDBMgrN.exe`, `QBW32.exe`, and `QBCFMonitorService.exe` in the QuickBooks installation directory

Temporarily disable the antivirus software to confirm it is the cause before adding permanent exclusions.

Method 6: Run the QuickBooks Install Diagnostic Tool

If the issue stems from a damaged QuickBooks installation or missing Microsoft components (.NET, MSXML, C++ redistributables), the Install Diagnostic Tool repairs them automatically.

  1. Open QuickBooks Tool Hub
  2. Click Installation Issues
  3. Click QuickBooks Install Diagnostic Tool
  4. Wait for the tool to run. It may take 20 minutes or more
  5. Restart Windows when the tool finishes
  6. Open QuickBooks and attempt to open the company file

6000-Series Error Comparison

Error 6123 belongs to the 6000-series family of company file access errors in QuickBooks Desktop. Use this table to confirm you are working on the correct error code.

Error CodeWhat It MeansMost Common CauseFirst Fix
-6123, 0QuickBooks cannot open the company fileDamaged .ND file or Database Server Manager stoppedDelete .ND and .TLG files (Method 1)
-6000, -77Company file is in use or locked by another sessionCompany file open on another machine, or prior session crashedRestart QuickBooks Database Server Manager
-6000, -80Network connection to company file was lostUnstable network path, VPN dropout, or server restartRun File Doctor and check network path
-6000, -83Company file is damaged or cannot be readFile corruption from improper shutdown or disk errorsRun File Doctor, then restore from backup
-6147, 0Backup file (.qbb) cannot be restoredBackup file is damaged or path is too longMove backup to root folder (C:\\) and retry
-6150, -1006QuickBooks cannot open, create, or use the company fileFile extension changed, moved, or severely corruptedRun File Doctor; restore from backup if repair fails

When to Call Support

Contact Intuit support directly if:

  • Error 6123 persists after completing all six methods above
  • The error appears alongside other 6000-series codes such as -6000 -83 or -6150 -1006, which indicate deeper file corruption
  • File Doctor reports that the company file cannot be repaired
  • The company file has not been backed up and data recovery is needed
  • Your QuickBooks version is more than three years old and shows compatibility issues with current Windows versions

You can reach Intuit support through the QuickBooks support phone number.

Prevention Tips

  • Keep QuickBooks updated. Apply updates promptly via Help > Update QuickBooks Desktop. Intuit releases patches that include database engine improvements and firewall rule updates
  • Assign a static IP address to the host computer. When the server IP changes due to DHCP reassignment, the .ND file becomes stale and Error 6123 can recur
  • Schedule regular backups. QuickBooks has an automated backup scheduler under File > Back Up Company. Set it to run daily or before every major accounting session
  • Add antivirus exclusions permanently. Once confirmed that antivirus software was the cause, keep the QuickBooks folder and executables in the exclusion list rather than relying on temporary disabling
  • Run the Tool Hub Network Scan quarterly to refresh .ND files and firewall permissions before errors appear
  • Avoid moving the company file without updating QuickBooks to point to the new location via File > Open or Restore Company
Expert Insight

I have reviewed hundreds of QuickBooks Desktop support cases and Error 6123 follows a predictable pattern in about 80% of incidents: the .ND file is stale or corrupted. The fix takes less than two minutes. Delete the .ND and .TLG files from the company file folder and let QuickBooks regenerate them. In the other 20% of cases, the Database Server Manager service has stopped, usually after a Windows update that did not restart the service automatically. A quick check in services.msc and a manual start of QuickBooksDBXX brings everything back. I have seen businesses spend hours with Tier 1 support for a problem that was resolved in under five minutes once those two things were checked first.

James Whitfield

James Whitfield

Small Business Technology Journalist

Get Support

The fastest way to resolve a QuickBooks issue is to speak directly with a support agent. Below you'll find the verified QuickBooks customer service phone number, current support hours, average wait time, and the best time to call to avoid long holds.

Phone Number

+1 (800) 446-8848

Support Hours

Mon–Fri, 6am–6pm PT

Avg Wait Time

~8 minutes min

Best Time

Early morning weekdays (6am–8am PT)

Conclusion

QuickBooks Error 6123 is a 6000-series company file access error that most commonly stems from a damaged .ND file, a stopped Database Server Manager service, or firewall interference. The six methods above address every documented cause in order of frequency. Start with Method 1 (deleting the .ND and .TLG files) and Method 2 (QuickBooks File Doctor) as they resolve the large majority of cases. If the error returns after some time, check whether a Windows update stopped the QuickBooksDBXX service or whether antivirus software re-enabled real-time protection on the company file folder. Maintaining regular backups and keeping the host computer on a static IP address prevents most recurrences of this error.

Sources & References

Disclaimer: OnCallSolve is an independent support directory. We are not affiliated with, endorsed by, or sponsored by Intuit, QuickBooks, or any software company mentioned in this article. All product names, logos, and brands are property of their respective owners. This article is provided for informational purposes only.


About Our Contributors
James Whitfield
Written by
James Whitfield

Small Business Technology Journalist

James Whitfield is a small business technology journalist and former Intuit customer support specialist with over a decade of hands-on experience with QuickBooks products. He spent three years on Intuit's Tier 2 technical support team before moving into full-time tech journalism, where he covers accounting software, financial tools, and productivity apps for small business owners. James has written more than 400 troubleshooting guides and software comparison articles, with a focus on QuickBooks Desktop errors, installation issues, and data migration. He holds a B.A. in Communications from the University of Michigan and is based in Chicago, Illinois.


Michael Reyes

Reviewed by

QuickBooks ProAdvisor

Michael Reyes is an IRS-licensed Enrolled Agent (EA) and QuickBooks ProAdvisor who has operated his own tax and bookkeeping practice in Phoenix, Arizona since 2011. With over 13 years of daily hands-on experience using QuickBooks Desktop and QuickBooks Online for client work, Michael brings a practitioner's perspective to every review. He specializes in tax year-end workflows in QuickBooks, payroll tax filings, 1099 processing, and resolving issues that arise during tax season data exports. Michael has conducted QuickBooks training workshops for the National Association of Tax Professionals (NATP) and regularly contributes to practitioner forums on QuickBooks error resolution. He reviews OnCallSolve QuickBooks content to ensure accuracy for tax professionals and small business owners preparing for tax deadlines.

Frequently Asked Questions

Error 6123 (also shown as -6123, 0) means QuickBooks found your company file but could not open it. The most common reasons are a damaged .ND network descriptor file, the QuickBooks Database Server Manager service not running, or a firewall blocking access. It is a file access error, not a data corruption error, so your data is typically intact.

Yes. The .ND file (network descriptor) and .TLG file (transaction log) are regenerated automatically by QuickBooks the next time you successfully open the company file. They do not contain your accounting data. Deleting or renaming them is the recommended first step from Intuit support for most 6000-series errors.

Error 6123 itself does not corrupt data. It is a connectivity or access error that prevents QuickBooks from opening the file. Your accounting data in the .qbw file remains unchanged. However, if the error is caused by an underlying disk problem or an improper shutdown, separate file corruption may exist. Run File Doctor to check file integrity after resolving the access error.

When the company file is on a network drive or UNC path, QuickBooks depends on the .ND file to locate the host and on the QuickBooks Database Server Manager to manage access. If either component has an issue, the file cannot be opened from the network. Opening the file directly on the host machine bypasses this dependency, which is why the error often appears only for networked users.

Open QuickBooks Desktop and go to Help > Update QuickBooks Desktop. Click Update Now, select all available updates, and click Get Updates. After the update installs, close and reopen QuickBooks. Some updates include database engine fixes that resolve 6000-series errors.

When the company file is moved, QuickBooks loses track of the new location and the .ND file points to the old path. Go to File > Open or Restore Company, browse to the new file location, and open the file from there. This updates QuickBooks preferences with the correct path. If the error persists, delete the .ND and .TLG files in the new folder and let QuickBooks regenerate them.

Open your antivirus console and go to the quarantine or threat history section. Find the QuickBooks file (typically a .qbw, .nd, or .tlg file) and select Restore or Allow. Then add the QuickBooks installation folder and company file folder to the antivirus exclusion list to prevent re-quarantine. After restoring the file, try opening the company file in QuickBooks again.

Recurring Error 6123 after a successful fix has three common triggers. First, a Windows update may have stopped the QuickBooksDBXX service, which requires a manual restart in services.msc. Second, DHCP may have reassigned a new IP address to the host computer, making the .ND file stale again (solution: assign a static IP to the host). Third, antivirus software may have re-enabled real-time protection on the company file folder after an antivirus update. Check all three of these whenever the error returns.

Was this article helpful?