ErrorVaultHQ

Solved Error

How to Fix: QuickBooks Error H202

Quick Fix

Fastest fix: Download and run the QuickBooks Tool Hub on the server computer, then use the Database Server Manager and File Doctor tools. 1. Close QuickBooks on every computer, then download and install the latest QuickBooks Tool Hub from Intuit's website. 2. Open Tool Hub, go to Network Issues, select QuickBooks Database Server Manager, choose your company file folder, and click Start Scan. 3. Then go to Company File Issues and run QuickBooks File Doctor, selecting your company file and choosing to check your network connection. 4. Open QuickBooks on each affected workstation and go to File > Switch to Multi-user Mode to test. This resolves the issue for most people because H202 is almost always a blocked connection between workstation and server, and these tools fix the most common causes automatically.

What Error H202 Means

QuickBooks Desktop error codes H202 and H505 (as well as H101 and H303) occur when something blocks the multi-user connection to your server computer, and these errors typically mean your workstations cannot communicate with the company file stored on the host server. The error typically displays a message that "This company file is on another computer, and QuickBooks needs some help connecting." This is a Windows-based, network/server-configuration issue — it is specific to QuickBooks Desktop's multi-user mode (not QuickBooks Online) and is most common on Windows networks with a dedicated server or host PC.

Common Causes

Based on documented cases, H202 is usually caused by one or more of these: QBCFMonitor or QuickBooksDBXX services not running on your server computer, damaged .ND and .TLG file components, incorrectly configured Firewall or Internet Security settings, company file hosting active on workstations instead of just the server, or the server's IP address not properly recognized by workstations. Less commonly, this can occur if the server's QB Database Manager is not the same version as the QB Desktop being used to open the file, or there's a network/DNS problem preventing the workstation from finding the server by name.

Step-by-Step Guide

Fix 1: Run the QuickBooks Tool Hub

  1. 1Close QuickBooks on all computers. The QuickBooks Tool Hub includes utilities designed to repair network and company file issues, and running the Database Server Manager and File Doctor from Tool Hub is often the fastest way to resolve Error H202. Close QuickBooks on all computers.
  2. 2Download and install the latest QuickBooks Tool Hub from Intuit's official site.
  3. 3Install QuickBooks Database Server Manager from Tool Hub. In Tool Hub, go to Network Issues, select QuickBooks Database Server Manager, and install it if prompted.
  4. 4Select company file folder and run scan. Select your company file folder (or browse to it) and click Start Scan.
  5. 5Run QuickBooks File Doctor from Tool Hub. From the tool hub, select Company File Issues, then select Run QuickBooks File Doctor.
  6. 6Check network and enter admin password in File Doctor. In QuickBooks File Doctor, select your company file from the dropdown menu (or Browse if you don't see it), select Check your Network and Continue, then enter your QuickBooks admin password and select Next.
  7. 7Switch to Multi-user Mode on each workstation. Open QuickBooks on each workstation where you see Error H202, then select File, then Switch to Multi-user Mode.

Fix 2: Confirm hosting settings are correct

  1. 1Verify hosting settings are correct on workstations. Only the server computer that actually stores the company file should host multi-user access. The Host Multi-User Access option should be turned off on your workstations, since these are the computers on your network that don't host your company files — your server computer should be the only one hosting. Check this via File > Utilities on each workstation — if you see "Host Multi-User Access" (not "Stop Hosting"), leave it unselected.

Fix 3: Make sure QuickBooks services are running on the server

  1. 1Open Services Manager on the server. On the server, press Windows+R, type services.msc, and press Enter.
  2. 2Set QuickBooksDBXX to run automatically and start it. Find and double-click QuickBooksDBXX on the list (XX notes your version of QuickBooks), choose Automatic for the Startup Type, and make sure the Service status is either Running or Started — if it's neither, select Start.
  3. 3Configure service recovery to restart automatically. Select Restart the Service from each of the dropdown menus: First failure, Second failure, and Subsequent failures (on the Recovery tab), so the service auto-recovers if it drops.
  4. 4Repeat service checks for QBCFMonitorService. Repeat the same check for the QBCFMonitorService.

Fix 4: Give services admin permissions and fix firewall settings

  1. 1Grant admin permissions and configure firewall exceptions. If you haven't already, give QuickBooksDBXX and QBCFMonitorService admin permissions on your server computer. Then make sure your server computer lets QuickBooks through your firewall — set up Windows firewall exceptions for QuickBooks Desktop. Ports commonly needed include ports 80, 8019, and the dynamic database ports for QuickBooks.

Fix 5: Test network connectivity between workstation and server

  1. 1Test network connectivity from workstation to server. Open Command Prompt on a workstation and ping the server by name. If you get a reply for each packet with no loss, your server is working fine and you can move to further solutions — but if there's packet loss or a very slow reply, stop and reach out to an IT professional for help with your network, since that points to a hardware/router/cabling problem rather than a QuickBooks setting.

Fix 6: Check for a version mismatch

  1. 1If the server's Database Server Manager is an older QuickBooks year version than the Desktop app opening the file, multi-user mode can break. One reported case found this occurs if the server QB Database Manager is not the same version as the QB Desktop, and it was resolved after upgrading the QB Database Manager on the server to match, after which multi-user mode worked correctly.

Fix 7: Try recreating the .ND network descriptor file

  1. 1Recreate the .ND network descriptor file. A damaged .ND file (the network descriptor QuickBooks uses to find the company file over the network) can also trigger H202. Closing QuickBooks, locating the .qbw.ND file in the company file folder, and renaming or deleting it (QuickBooks will recreate it) is a common advanced fix reported by users.

Fix 8: Move the company file to a new folder

  1. 1If nothing else works, try relocating the file: create a new folder on the server computer, move the QuickBooks company file to the new folder after providing adequate permissions, then open the company file in multi-user mode again from the new folder — if you can access the file from the new folder, the original folder was likely damaged; if you still can't open it, the issue is in the company file itself.

When to Get More Help

If you've run through Tool Hub, verified hosting settings, confirmed services are running, adjusted the firewall, and ping tests still show packet loss or timeouts, this is a network/hardware problem outside QuickBooks itself — involve an IT professional or your network administrator. If QuickBooks File Doctor reports it "couldn't fix your company file," or the error recurs unpredictably (e.g., every Monday after a server reboot, tied to dynamic port conflicts), this may require Intuit's official QuickBooks Desktop Support team, since it may be a technical issue that requires assistance from Intuit's Customer Care Team. Persistent recurring H202 on a virtual server has also been linked to port conflicts; some IT teams resolve it by refreshing the port assignment in QB Database Manager's Port tab, though this hasn't been found to be a truly permanent fix, as it seems to be QuickBooks and the server fighting over the port QuickBooks is trying to use.

Sources:

Heads up: this guide was drafted with AI assistance from the real sources listed below, and structured by our team for clarity. It may not cover every possible cause — if it doesn't fix your issue, let us know and we'll take a closer look. See how we create our fixes.

Was this fix helpful?

Related Error Fixes