QuickBooks Error 6120, 0
Let’s Dive in to see…
How to Fix QuickBooks Error=6120-0
QuickBooks Company File Error · 6000 Series
How to Fix QuickBooks Error 6120, 0
QuickBooks displays: "An error occurred when QuickBooks tried to access the company file (-6120, 0)"
From Intuit's own sub-code table: -6120, 0 means "the 8019 firewall port is blocked OR a workstation is hosting the company file." At QuickFix Bookkeeping, the diagnostic is to check both simultaneously: check hosting on all machines (takes 30 seconds), then check port 8019. The Port Monitor tab in QBDSM shows the exact dynamic port number to open — essential for QB 2019 and later.
The QuickFix Bookkeeping Distinction — Using the Port Monitor to Find Your Dynamic Port
QB 2019 and later use a dynamic port assigned during installation — not just 8019. You must look up the actual port to open in the firewall.
Finding your dynamic port — step by step:
1. On the server: Start → All Programs → QuickBooks → QuickBooks Database Server Manager. 2. Click the Port Monitor tab. 3. Find your QB Desktop version in the list. 4. Note the port number shown next to it (e.g., 56729). 5. That number — plus 8019 — are the two TCP ports to open in Windows Firewall as inbound rules. Both Private and Public profiles must allow these ports.
Fixed ports by QB version (for reference): QB 2018: 8019, 56728, 55378–55382 | QB 2017: 8019, 56727, 55373–55377 | QB 2019+: 8019 + dynamic port (check Port Monitor tab). For QB 2019 and later, do NOT guess the dynamic port — always read it from the Port Monitor tab. The dynamic port can change if you use the "Renew" option in QBDSM.
What Causes QuickBooks Error 6120, 0?
Firewall Port 8019 Blocked
Primary cause A — Windows Firewall or a third-party firewall blocks port 8019, which is QB's Database Server Manager's primary communication port. When workstations can't reach the server's QBDSM on port 8019, the multi-user file-sharing connection fails with -6120, 0. Opening port 8019 (and the dynamic port) as an inbound TCP rule on the server's firewall resolves this.
Workstation Hosting the Company File
Primary cause B — a workstation (not the server) has "Host Multi-User Access" enabled. The workstation's QBDSM tries to serve the company file but lacks the network authority to do so correctly, producing -6120, 0. Disabling hosting on the workstation (File → Utilities → Stop Hosting Multi-User Access) immediately resolves this cause.
Dynamic Port Not Open in Firewall (QB 2019+)
For QB 2019 and later, a second dynamic port (assigned during installation and viewable in QBDSM's Port Monitor tab) must also be open alongside 8019. If only 8019 is open but the dynamic port is blocked, -6120, 0 still appears. Always check both ports.
Damaged .ND or .TLG Files
If the .ND or .TLG files are corrupted while a firewall or hosting issue also exists, -6120, 0 can appear even after fixing the firewall/hosting. Rename both companion files → run QBDSM scan to rebuild them → retry opening the company file from the network.
Company File in a Non-Default or Damaged Folder
If the company file is stored in a folder that doesn't have proper sharing permissions (especially if not in the default QB company files folder), QBDSM can't serve it over the network. Moving the file to the default location (C:\Users\Public\Documents\Intuit\QuickBooks\Company Files\) or setting correct permissions resolves folder-based -6120, 0.
Invalid File Extension
Trying to open a file with an incorrect extension (.qbm, .qbw.adr) in a network context can produce -6120, 0 because QBDSM doesn't recognize the file format for network hosting. Ensure the company file has a .QBW extension before attempting multi-user access.
How to Fix QuickBooks Error 6120, 0
Check hosting on all machines first (60 seconds), then verify firewall ports using the Port Monitor tab in QBDSM.
Quick Reference
| Situation | Cause | Start with |
|---|---|---|
| Any -6120, 0 occurrence | Hosting or port 8019 blocked | Method 1 — check hosting on all machines first |
| Hosting correct — still -6120, 0 | Firewall blocking ports | Method 2 — Port Monitor + open 8019 + dynamic port |
| After hosting + firewall fixed — persists | Corrupted .ND / .TLG | Method 3 — rename .ND + .TLG + QBDSM rescan |
| Sample file also fails | QB installation damaged | Method 4 — File Doctor + repair QB |
Frequently Asked Questions
Related QuickBooks Errors
Error 6120, 0 Persisting After Opening Ports and Fixing Hosting?
Let QuickFix Bookkeeping Diagnose Your Network Setup.
Persistent -6120, 0 after opening ports and fixing hosting typically indicates another application is occupying port 8019 or the dynamic port — use netstat -ano | findstr 8019 in CMD to check for port conflicts.
No obligation. Same-day response.