QuickBooks Error H202: Causes and Fixes for Multi-User Mode

Error H202 is one of the multi-user hosting codes in QuickBooks Desktop. It appears when a workstation asks to open a company file and cannot reach the computer that hosts it. QuickBooks stops at the code instead of opening the file. We see it most often after something changes on the office network, the host machine, or the security software.

What does Error H202 mean?

In multi-user mode, one computer holds the company file and runs the database service that feeds it to the other machines. Error H202 means your workstation asked for the file and the service never answered. The code belongs to the same family as H101, H103, and H505, which all point to this kind of block. It can affect one workstation or the whole office at once.

What causes the H202 block?

A short list covers nearly every case:

• Hosting is turned on at more than one computer, so the workstations conflict with the real host.
• A firewall or security program is blocking the ports the database service listens on.
• The network data file, the .ND file that helps QuickBooks find the company file, is damaged or stale.
• The QuickBooks Database Server Manager is not running, or it has not scanned the folder holding the file.
• The host computer is offline, asleep, or unreachable on the network.

Does Tool Hub clear Error H202?

The Tool Hub is Intuit’s free repair suite for Desktop, and its Network Issues tab is the right place to start. Intuit publishes the installer as a free download on its own site, so grab the current build from there. Install it on the affected workstation, open the Network Issues tab, and run the network repair on offer, which most releases call QuickBooks File Doctor. The scan checks hosting setup, firewall permissions, and the network data file, then repairs what it can reach. Let it finish, since a large file takes a while. One run clears H202 in many cases, but not all, because no scan can reconfigure a network it cannot see.

Which manual fixes should follow?

Work down this list on the machines involved:

1. Confirm hosting on each computer. In QuickBooks Desktop, open the File menu and look under Utilities. The host should show hosting on, and workstations should show it off. Hosting on several machines is a classic trigger.
2. Rescan with the Database Server Manager. On the host, open the QuickBooks Database Server Manager and scan the folder that holds the company file. A scan rebuilds the network data files and shows the service where the file lives.
3. Rename the network data file. With QuickBooks closed everywhere, find the file that shares the company file’s name and ends in .ND, then add OLD to the end of its name. QuickBooks builds a fresh one at the next open. Never rename the .QBW file itself.
4. Test the route to the host. Ping the host computer by name from the workstation. If that fails, the fault sits below QuickBooks, in the network, the DNS, a VPN, or the host’s power settings.
5. Let the database service through the firewall. Allow QuickBooks and its database manager in Windows Firewall and in any third-party security software, on the host above all.

Could the company file itself be damaged?

Usually not. H202 points at the path to the file, not the file, and most offices recover once hosting and the firewall are corrected. The exception follows a crash, a forced shutdown, or a file moved between computers. There, the company file or its network data may be hurt, and the same code can hide that damage. If every step above leaves H202 in place, treat the file as suspect and work from your most recent backup.

Persistent H202 points to file damage

When hosting, the firewall, and the server manager all check out, what remains is damage inside the file or its network data. That is repair work rather than setup work. Our QuickBooks error code repair service rebuilds damaged company files and handles codes like H202 that survive the normal setup fixes. Get the file assessed before anyone re-enters data by hand, because a rebuild is usually the faster and safer route back to multi-user access.