QuickBooks Error H202: Check the Host Before Rebuilding the File
Error H202 blocks workstations from opening a QuickBooks Desktop file in multi-user mode, and our engineers clear it, usually without any data repair.
Error H202 appears when a workstation opens a company file in multi-user mode and cannot reach the machine hosting it. The message points at the file, which is misleading. In nearly every case our engineers see, the data is intact and the connection is broken. Work through the host machine first, and leave data repair for later.
The error points at the connection, not the data
H202 means the database service on the host did not answer the workstation. QuickBooks reads this as a sharing failure and shows the code, but the records are rarely the issue. The giveaway is simple: the file opens normally at the host and fails everywhere else. That split tells you the company file is readable. What is broken is the path to it: the hosting mode, the folder scan, or the firewall on the host.
Back up first, then work at the host
Get the file safe before changing anything. Have every user close the company file and exit QuickBooks. At the host machine, open the file in single-user mode and take a backup from the File menu. Copy that backup to a drive you control.
Do the remaining steps at the host's own keyboard. Remote sessions can swallow firewall prompts, and you need to see those. Last, confirm which machine actually stores the file. Only that machine should ever host it.
Confirm hosting sits on one machine only
Hosting is a per-installation switch, and H202 thrives in a setup where two machines both believe they are the host.
- On the host, open QuickBooks and choose File > Utilities.
- If the menu offers Host Multi-User Access, hosting is off there. Select it once and confirm the prompts.
- If it offers Stop Hosting Multi-User Access instead, hosting is already on, which is correct for the host.
- Repeat the check at every workstation. Each one must offer Host Multi-User Access, meaning hosting is off there. If any seat offers Stop Hosting, turn hosting off at that seat.
- Press F2 with the file open. The Local Server Info block should point to the hosting machine, and every seat should agree on that machine.
When a workstation hosts by accident, the others chase its database service instead of the real one. The host refuses, and workstations report H202 even though the file is fine.
Rescan the folder with Database Server Manager
The Database Server Manager maintains the .nd descriptor file that workstations use to find the database. If it has never scanned the folder, or the scan is stale, workstations have no pointer to follow.
- On the host, open QuickBooks Database Server Manager.
- In the Scan Folders tab, add the folder that holds the company file.
- Run the scan and confirm the file appears in the results.
- If it does not appear, close QuickBooks, delete the .nd file that sits beside the company file, and scan again.
Deleting the .nd file is safe. It is a pointer, not data, and the scan rebuilds it. If the manager is missing from the host, it installs on its own from the QuickBooks installer; a full reinstall of the desktop program is not required.
Let the firewall pass the right ports
Multi-user traffic uses TCP port 8019, plus a short block of ports tied to the installed year of QuickBooks. You do not need the ranges by heart. Allow the programs instead, which covers the correct ports for your release.
- When you first switch hosting on, Windows shows a firewall prompt. Choose Allow.
- In Windows Defender Firewall, open the allowed apps list and confirm the QuickBooks entries for your year are checked.
- If a third-party security suite runs on the host, add the company file folder and the QuickBooks programs to its exceptions.
Security suites block the database service quietly. The failure then surfaces on workstations, which sends the search in the wrong direction.
Signs the fix took hold
Open the file from a workstation through the network share, not from a local copy. Switch to multi-user mode, then sign in from a second seat at the same time. If both sessions hold without H202, hosting is answering again.
Close QuickBooks everywhere and reopen the file from a workstation. A fix that survives a full close and reopen has stuck.
If H202 survives all three checks
Sometimes hosting, scanning, and the firewall all verify and the error persists. The next suspects sit deeper. The workstation may fail to resolve the host's name, the .nd file may carry an old server name, or the host may have two active network adapters. Opening the file through the host's IP address, rather than its name, tells you quickly whether name resolution is the culprit.
Recurring H202 on an aging or overloaded host is its own pattern. When the error returns month after month on tired hardware, hosting usually settles once the file moves to a machine with proper memory and disk.
And if the code changes, pay attention. A swap to H505 or a 6000-series error, or a file that will not open even at the host, points at the data layer rather than the network. Our engineers handle those cases through our QuickBooks error code repair service. Until the network checks are exhausted, hold off on Rebuild Data. It rewrites records inside a file that, in most H202 cases, was never the problem.