QuickBooks Error 6120, 0

Let’s Dive in to see…

How to Fix QuickBooks Error=6120-0

QuickBooks Online

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.

METHOD 1 Check Hosting on All Machines Workstation hosting — fastest check
1

On every workstation: QB → File → Utilities. If "Stop Hosting Multi-User Access" appears → click it → Yes. Only the server should show this option as active. Also: on each machine press F2 → under Local Server Information → verify Hosting is OFF for workstations. After fixing all workstations: rename .ND + run QBDSM scan → retry opening the company file.

METHOD 2 Open Firewall Ports Using Port Monitor Port 8019 or dynamic port blocked
1

Find your dynamic port: on the server → QBDSM → Port Monitor tab → note the port number for your QB version (e.g., 56729).

2

Create firewall rules: Windows Firewall → Advanced Settings → Inbound Rules → New Rule → Port → TCP → Specific local ports → enter 8019, [dynamic port] (e.g., 8019, 56729) → Allow the connection → all profiles (Domain, Private, Public) → name it "QuickBooks Multi-User" → Finish. Repeat for Outbound Rules. Restart QBDSM service → retry from workstation.

METHOD 3 Rename .ND + .TLG + QBDSM Rescan Companion files corrupted alongside firewall/hosting issue
1

After fixing hosting and firewall: navigate to the company file folder → rename YourFile.QBW.ND → add .OLD → rename YourFile.QBW.TLG → add .OLD. Open QBDSM → Scan Folders → ensure company file folder is listed → Start Scan. QBDSM rebuilds both files with fresh network configuration. Try opening the company file from a workstation.

METHOD 4 Run File Doctor + Check Folder Permissions + Repair QB -6120, 0 persists after hosting and firewall fixed
1

Tool Hub → Company File Issues → Run QuickBooks File Doctor → Check your file and network → run. Folder permissions: right-click company file folder → Properties → Security → Edit → add QBDataServiceUser[XX] with Full Control → add Everyone with Full Control → Apply. Repair QB: if sample file also fails → Control Panel → Programs → QuickBooks → Repair.

Quick Reference

SituationCauseStart with
Any -6120, 0 occurrenceHosting or port 8019 blockedMethod 1 — check hosting on all machines first
Hosting correct — still -6120, 0Firewall blocking portsMethod 2 — Port Monitor + open 8019 + dynamic port
After hosting + firewall fixed — persistsCorrupted .ND / .TLGMethod 3 — rename .ND + .TLG + QBDSM rescan
Sample file also failsQB installation damagedMethod 4 — File Doctor + repair QB

Frequently Asked Questions

How is Error 6120, 0 different from Error 6073, 816?
Both can be caused by a workstation incorrectly hosting the company file, but the additional cause and primary focus differ. Error 6073-816 is specifically "more than one computer hosting simultaneously" — the definitive fix is disabling extra hosts. Error 6120, 0 adds a second distinct cause: "firewall port 8019 is blocked" — the error can appear even when hosting is perfectly configured if port 8019 is closed. The diagnostic path for -6120, 0 therefore always includes both a hosting check AND a firewall port check, while -6073, -816 focuses primarily on the hosting conflict. The Port Monitor tab in QBDSM is the 6120-specific tool — it's not needed for -6073 troubleshooting.
What is port 8019 and why does QB need it open?
Port 8019 is the primary TCP port used by QuickBooks Database Server Manager (QBDSM) — QB's multi-user file-sharing service — to listen for connection requests from workstations. When a workstation user opens QB and accesses a network-hosted company file, QB on that workstation sends a connection request to the server's QBDSM on port 8019. The QBDSM then handles the file-sharing session. If port 8019 is blocked by Windows Firewall or a third-party firewall, the workstation's connection request is dropped and QB reports -6120, 0 — it can't even establish the initial handshake with the QBDSM to begin opening the company file. This port is static across all QB versions; it never changes. The dynamic port (viewable in Port Monitor) is a second port used for data transfer after the initial connection on 8019 is established.

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.

Book a Free 30-Minute Consultation

No obligation. Same-day response.