QuickBooks Multi-User Mode Error Guide
How to Fix QuickBooks Error H202
You went to switch QuickBooks to multi-user mode — something that normally takes two clicks — and instead got: "This company file is on another computer, and QuickBooks needs some help connecting." Error H202. Your team is locked out of the company file.
At QuickFix Bookkeeping, H202 is one of the most consistently misdiagnosed errors in QuickBooks Desktop — not because it is hard to fix, but because most guides miss the cause that Intuit's own documentation does not clearly flag. Knowing what actually broke on your network is the difference between a 5-minute fix and an afternoon of wasted troubleshooting.
The QuickFix Bookkeeping Distinction
Every H202 guide tells you to restart the Database Server Manager. Almost none tell you to check its version.
The version mismatch problem — and why it causes H202 every time
If the QuickBooks Desktop installed on your server is a different version year from the QuickBooks Database Server Manager running on that same server — H202 will appear on every workstation, every time, regardless of how many times you restart services or reconfigure the firewall. The Database Server Manager and the QuickBooks Desktop version must match exactly. A common scenario: a client upgrades workstations to QuickBooks 2024 but the server still runs the 2022 Database Server Manager. Multi-user fails immediately. The fix is upgrading the Database Server Manager on the server to match — not network troubleshooting.
Check this first — before touching firewall settings, services, or any other step below. Press F2 in QuickBooks on the server to see the version. Then check the Database Server Manager version in Tool Hub → Network Issues. If they differ — that is your answer.
What Is QuickBooks Error H202?
Error family
H202
H-Series · Multi-User Mode
Related: H101 · H303 · H505
What H202 means in plain English
H202 means a workstation cannot communicate with the server that is hosting the company file. The workstation knows the file exists on another machine — it just cannot reach it. The breakdown is always in one of four places: the network connection, the QuickBooks services running on the server, the firewall settings, or a version mismatch between components.
Your data is safe. H202 is a connection error — it does not corrupt or alter the company file. Multi-user access is blocked, but the file is intact on the server.
H-Series Error Quick Reference
H101
This computer not set up to host — but no other host found
H202
This page — workstation cannot reach the server hosting the file
H303
This computer set to host but file is on another machine
H505
User not authorised for multi-user access on this machine
H202 is by far the most common. All H-series errors are multi-user connection failures — but the fix depends on which code you see. If you are getting H303 or H505, see the linked guides at the bottom of this page.
What Causes QuickBooks Error H202?
🔢
Version Mismatch — DB Server Manager vs QuickBooks
The QuickBooks Database Server Manager on the server is a different version year from the QuickBooks Desktop installed on workstations. Every year's QuickBooks requires the matching version of the Database Server Manager — mixing 2022 and 2024 will always produce H202.
⚙️
QuickBooks Services Not Running on Server
The two Windows services QuickBooks depends on for multi-user mode — QuickBooksDBXX (the database manager) and QBCFMonitorService (the connection monitor) — are stopped, crashed, or not set to start automatically on the server.
🛡️
Firewall Blocking QuickBooks Ports
Windows Firewall or a third-party security product is blocking the ports QuickBooks uses for multi-user communication — primarily ports 8019 and the dynamic QuickBooks database ports (55373–55378 depending on version). No exceptions = no connection.
📡
DNS or Network Name Resolution Failure
The workstation cannot resolve the server's name to an IP address — meaning it cannot find the server on the network at all. This produces H202 even when both machines are on the same physical network and can ping each other by IP.
🖥️
Incorrect Hosting Configuration
A workstation is set to host the company file when it should not be, or the server does not have hosting enabled when it should. Only one machine — the designated server — should have hosting active. Multiple machines hosting causes H202 across the entire network.
📋
Incorrect Windows Hosts File
The Windows hosts file on workstations does not contain the correct server name-to-IP mapping. QuickBooks uses this file to locate the server — an outdated or missing entry means the workstation cannot establish the connection.
How H202 Shows Up — Recognising the Error
01
Error message on workstation when switching to multi-user mode
The full message reads: "This company file is on another computer, and QuickBooks needs some help connecting. For assistance, see Help and Support." with the H202 code displayed below.
02
Only certain workstations are affected
Some users can access the company file in multi-user mode while others cannot. This points to a permissions, DNS, or hosts file issue specific to the affected workstations rather than a server-wide problem.
03
All workstations get H202 simultaneously
If every workstation on the network gets H202 at the same time — especially after a server restart or a QuickBooks update — the cause is almost always a version mismatch or a QuickBooks service that stopped running on the server.
04
H202 appears every Monday or after weekends
A recurring H202 after weekends or after the server is powered down is a strong indicator that the QuickBooksDBXX service is not set to start automatically — it stops when the server reboots and nobody restarts it before Monday morning.
How to Fix QuickBooks Error H202 — Step by Step
Check the version mismatch first (Method 1). If versions match, work through Methods 2–6 in sequence.
METHOD 1
Verify Database Server Manager Version Matches QuickBooks
Check this before anything else
This is the cause Intuit's standard H202 guide underemphasises — and it is responsible for a significant number of persistent H202 cases that do not respond to standard troubleshooting. Takes two minutes to check.
1
On the server computer, open QuickBooks Desktop. Press F2 to open the Product Information window. Note the version year and release number shown — for example, QuickBooks Desktop Pro 2024, Release R5.
2
Open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager. Check the version shown at the top of the Database Server Manager window.
3
If the versions do not match year for year — download and install the Database Server Manager for the correct year from Intuit's official website. Restart the server after installation and test multi-user access.
QuickFix tip: This version mismatch is most likely to occur after one of two events: a workstation upgrade where only the workstations were updated to a newer QuickBooks year but the server's Database Server Manager was left on the old version, or the reverse — the server was updated but workstations were not. Either direction produces the same H202 result.
METHOD 2
Restart QuickBooks Services on the Server
Fixes Monday morning H202
The two QuickBooks Windows services must be running on the server for multi-user mode to function. If either has stopped — after a server restart, a Windows update, or a crash — H202 appears on all workstations simultaneously.
1
On the server computer, press Windows + R → type services.msc → press Enter.
2
Find QuickBooksDBXX (where XX is your version year — e.g. QuickBooksDB34 for 2024) and QBCFMonitorService. For each: right-click → Restart. If either shows as Stopped, right-click → Start.
3
Double-click each service to open Properties. Set Startup type to Automatic for both services. This ensures they start automatically after every server reboot — permanently eliminating the Monday morning H202 problem.
4
Go to each service → Log On tab → ensure both services are running under an account with administrator permissions. Click Apply then OK. Test multi-user access from a workstation.
METHOD 3
Run Database Server Manager Scan and Check Hosting
Fixes hosting misconfiguration
The Database Server Manager needs to actively scan and recognise the company file folder to enable multi-user access. It also automatically configures firewall port exceptions during the scan — making this a two-in-one fix.
1
On the server, open QuickBooks Tool Hub → Network Issues → QuickBooks Database Server Manager.
2
If your company file folder is listed — click Start Scan. If it is not listed — click Browse, navigate to the company file folder, and then click Start Scan. Wait for it to complete.
3
Check hosting on workstations: On each workstation, open QuickBooks → File → Utilities. If it shows "Stop Hosting Multi-User Access" — click it to disable hosting on that workstation. Workstations must never host — only the server.
4
After scanning and fixing hosting, test multi-user mode from each workstation. Go to File → Switch to Multi-User Mode and confirm the company file opens without H202.
METHOD 4
Configure Firewall Ports for QuickBooks
If firewall is blocking communication
Windows Firewall — and third-party security products — frequently block the ports QuickBooks uses for multi-user communication. Adding explicit exceptions eliminates the block permanently without disabling firewall protection.
1
Quick test: Temporarily disable Windows Firewall on the server and attempt multi-user access from a workstation. If H202 clears immediately — the firewall was the cause. Re-enable the firewall and proceed to add exceptions rather than leaving it disabled.
2
On the server, go to Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule. Add port exceptions for: Port 8019 (QuickBooks communication), Ports 55373–55378 (QuickBooks dynamic database ports). Set each as TCP, Allow the Connection, apply to all profiles.
3
Repeat for Outbound Rules with the same ports. Also add program exceptions for QBW32.exe, QBDBMgrN.exe, and QBCFMonitorService.exe from the QuickBooks installation folder.
QuickFix tip: Running the Database Server Manager scan from Method 3 automatically configures firewall exceptions for QuickBooks — which is why we recommend running Method 3 first even when you suspect a firewall issue. If it does not fully resolve the problem, Method 4's manual port configuration ensures nothing was missed.
METHOD 5
Ping the Server and Update the Windows Hosts File
For DNS / name resolution failures
If the workstation cannot find the server by name — even when both machines are on the same network — adding the server's IP and name to the Windows hosts file on each workstation resolves the name resolution issue permanently.
1
Get the server IP: On the server, open Command Prompt and type ipconfig /all. Note the IPv4 Address and the Host Name.
2
Test connectivity: On each affected workstation, open Command Prompt and type ping [servername]. If the ping fails or shows packet loss, proceed to the next step. If it succeeds — name resolution is fine; the problem is services or firewall.
3
On each workstation, open Notepad as Administrator. Open the file: C:\Windows\System32\drivers\etc\hosts. At the bottom, add a new line: [Server IP address] [Server name]. Save and close.
4
Reopen QuickBooks on the workstation and test multi-user mode. The hosts file entry gives the workstation a direct map to the server that bypasses DNS entirely.
METHOD 6
Set Correct Folder Permissions for QuickBooks Data Service User
For persistent H202 on specific workstations
The QuickBooks Data Service user account — created automatically when QuickBooks is installed — must have Full Control over the company file folder. Without it, the Database Server Manager cannot read and serve the file to workstations.
1
On the server, navigate to the folder containing the company file. Right-click it → Properties → Security → Edit.
2
Check whether QBDataServiceUserXX (where XX matches your QuickBooks version) is listed. If not — click Add, type QBDataServiceUser, click Check Names, and add the account. Set it to Full Control.
3
Click Apply → OK. Restart the QuickBooksDBXX service from services.msc and test multi-user mode from workstations.
Quick Reference — Which Fix For Your Situation?
| Your situation |
Most likely cause |
Start with |
| Happened after upgrading QuickBooks on workstations |
Version mismatch |
Method 1 — version check |
| All workstations get H202 every Monday |
Services not set to auto-start |
Method 2 — restart services |
| Multiple machines may be hosting |
Hosting misconfiguration |
Method 3 — DB Server Manager |
| New antivirus or firewall recently installed |
Firewall blocking ports |
Method 4 — firewall ports |
| Ping test fails or shows packet loss |
DNS / name resolution |
Method 5 — hosts file |
| Only certain users affected on specific workstations |
Folder permissions |
Method 6 — QB data service user |
Frequently Asked Questions About Error H202
Is my company file at risk when H202 appears?
No. H202 is a connection error — it means the workstation cannot reach the server hosting the file, but the file itself on the server is completely safe and unaffected. No data is lost or corrupted by H202. The only impact is that multi-user access is blocked until the connection issue is resolved.
Can one person still work while H202 is active?
Yes. If the file is accessible on the server computer directly — or if one workstation can still reach it — that machine can open it in single-user mode while you troubleshoot the network issue. However, no other users can access the file simultaneously in this workaround. Do not run payroll or process critical transactions in single-user mode during troubleshooting unless absolutely necessary.
What is the difference between H202, H101, H303, and H505?
All four are H-series multi-user connection errors, but each points to a different specific failure. H101 means this computer is not set up to host and cannot find a host on the network. H202 — this page — means a workstation cannot connect to the server hosting the file. H303 means this computer is set up to host but the file is stored on a different machine. H505 means the user account is not authorised for multi-user access. The fixes overlap significantly but differ in key steps — particularly around which machine needs attention first.
How do I permanently prevent H202 from recurring?
Four practices eliminate most recurring H202 situations. Set both QuickBooks Windows services to Automatic startup so they survive server reboots. Keep the Database Server Manager version in sync with QuickBooks Desktop — update both together whenever you upgrade QuickBooks year versions. Add QuickBooks firewall exceptions permanently rather than temporarily disabling the firewall. And maintain a static IP address for the server rather than relying on DHCP — if the server's IP changes, workstations lose their connection and hosts file entries become stale. At QuickFix Bookkeeping, we configure all four of these as standard during any new multi-user QuickBooks setup for clients.
Related H-Series and Multi-User Errors
Team Locked Out of QuickBooks?
H202 Still Blocking Multi-User Access
After Six Methods?
Certified Intuit ProAdvisors · QuickBooks Network Specialists
Persistent H202 errors almost always point to a network configuration issue that needs hands-on diagnosis — whether that is a version mismatch, a firewall policy that cannot be changed from the workstation, or a Windows domain permission problem. At QuickFix Bookkeeping, we resolve multi-user access errors for businesses daily and can diagnose your exact configuration remotely in a single session.
Book a Free 30-Minute Consultation
No obligation. Same-day response. Your team back in QuickBooks today.
