QuickBooks Error H202: Repair the Host Before the File

Multi-user mode fails with error H202 and users cannot open the company file; this playbook traces the fault and returns every workstation to the file.

Error H202 appears the moment a workstation asks for the company file in multi-user mode and the machine holding it never answers. Our engineers trace it to the host far more often than to the data. The trap is reaching for Rebuild Data, which treats damage that usually is not there. This playbook protects the file first, isolates the fault, and returns every user to the books.

The right time to run this playbook

Run it when any workstation shows H202 while opening the file in multi-user mode, or when only users on the far side of the network from the host see it. Run it before anyone schedules another Rebuild Data pass. The near variants, H101 and H103, sit in the same place and answer to the same work. If the host itself cannot open the file at all, the problem is the data, not the connection, and this playbook is the wrong tool.

Hold off on Rebuild Data

Rebuild Data is a repair tool for a damaged database. H202 is a connection error: the workstation could not reach the database service that shares the file. Rebuilding healthy data buys nothing, takes hours on a large file, and adds a small risk on every pass.

Make a fresh backup copy first, always. Then open the file at the host in single-user mode and run Verify Data. A clean Verify is your evidence that the file is not the patient. Treat it as permission to leave the data alone. If Verify fails instead, stop here; our QuickBooks Verify and Rebuild repair service is the right next step, and the host work can resume once the file is sound.

Test the file on the host itself

  1. Sit at the machine that stores the company file and open it directly, in single-user mode, with no network involved.
  2. Press F2 and note the version and release shown in the Product Information window; every machine must match it.
  3. If the file opens and Verify passes, the data is cleared and the fault sits in the sharing layer.
  4. If the host cannot open the file, or Verify fails on it, this is data recovery work rather than networking. Our QuickBooks error code repair service covers that path.

Repair the host, one change at a time

  1. Confirm hosting is switched on at the host and off at every workstation. Check the Local Server Info section of the F2 window, or the File menu's Utilities entry. Only one machine should ever host.
  2. In Windows Services, find the QuickBooksDB service for your year. It should be running and set to start automatically. Restart it once with everyone logged out.
  3. Open QuickBooks Database Server Manager and scan the folder that holds the company file. The scan regenerates the network descriptor file that sits beside it.
  4. If the scan changes nothing, rename that descriptor file rather than deleting it, keeping the original so you can restore it, then rescan.
  5. Add firewall exceptions for the database service executable and the program folder. Each year's service listens on its own assigned port, so chasing numbers is fragile; the folder exception is not.
  6. From one workstation, browse to the host by its network name. If the raw address works where the name fails, the fault is name resolution, and that is a network fix rather than a QuickBooks one.

One change, then one retest, in that order. A single user opens the file in multi-user mode after each change, so you always know which change worked.

Bring every user back in

Start with one workstation and open the file in multi-user mode. Confirm the connection holds through real work: save an invoice, post a payment, run a report under load. Add the remaining users a few at a time, not all at once. Check F2 on a couple of workstations afterward; hosting must read off on every one. If the error returns only when many users connect together, suspect the database service failing under load, and restart it with everyone out before testing again.

Rollback points

Three exist, and none touches the company file itself. The backup copy made before the first Verify is the hard stop for anything data related. The renamed descriptor file is the second; restoring its original name undoes the rescan. Hosting mode is the third: change it only with all users logged out, and change it back if a step makes things worse. Nothing in this playbook writes to the file, so the file you start with is the file you end with.

A clean outcome

Every workstation opens the company file in multi-user mode and stays connected through a full stretch of normal work. Hosting reads on at the host and off everywhere else. A Database Server Manager scan lists the file where it lives, and a final Verify at the host still passes, proving the fix never put the data at risk. The error does not return after the host and the workstations have each been restarted once.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.