QuickBooks Desktop Errors H202 and H505: Restoring Multi-User Access
Errors H202 and H505 stop QuickBooks Desktop workstations from reaching the company file host; the accepted fix rebuilds that connection.
Multi-user failures in QuickBooks Desktop keep surfacing in community threads under a familiar pair of codes: H202 and H505. The error appears the moment a user switches a company file to multi-user mode. Single-user access on the host machine usually keeps working, which tells you the file is fine and the network path is not. The codes H101 and H303 belong to the same family, and the accepted fix treats all four together.
What do H202 and H505 actually mean?
Both codes point to one condition: a workstation cannot reach the computer hosting the company file. Something between the two machines is blocking the connection. The culprit is usually a firewall rule, a hosting setting enabled in the wrong place, or a server that never had the Database Server Manager installed. The accepted answer, credited to Intuit, starts with tool-based repair and falls back to manual network work. We have broken out both routes below.
Fix H202 with the QuickBooks Tool Hub
The first pass happens on the server, meaning the computer that stores your company files. Install the QuickBooks Tool Hub there if it is not already present. Open the hub, choose Network Issues, and select QuickBooks Database Server Manager. If QuickBooks itself is absent from the server, the manager prompts you to install it.
The manager lists company file folders. Confirm yours appears, browse to it if it does not, then start the scan. The scan also repairs firewall permissions on its own, which is why it comes before any manual rule editing. Close the manager when the scan finishes.
Next, return to the hub and choose Company File Issues, then run QuickBooks File Doctor. The tool can take a minute to appear. If it never opens, search for QuickBooks Desktop File Doc and launch it directly.
Finish by opening QuickBooks on each workstation that showed H202 and switching to multi-user mode from the File menu. Check the server as well if it doubles as a workstation.
The accepted answer also covers how the Database Server Manager gets installed. You can put the full Desktop program on the server, or choose a server-only install that skips the full application. Either way, install it once for each version of QuickBooks in use, since versions do not share one manager.
The manual network checks that settle it
When the tools are not enough, four checks carry the fix. First, hosting belongs on the server alone. In QuickBooks, open the File menu, then Utilities. On the server, the menu should offer to stop hosting, which means hosting is already on. On a workstation, the menu should offer to start it. If a workstation offers to stop hosting, turn hosting off there.
Second, test the connection. Ping the server from a workstation by name, then by its numeric address. If the address answers and the name does not, name resolution is broken. Adding the server’s address and name to the Windows hosts file on each workstation clears it.
Third, check the ports. Multi-user traffic runs over TCP port 8019 plus a small block of ports the Database Server Manager assigns by version year, drawn from the 55300s in recent releases. Firewall rules on the server must allow that traffic in both directions for every installed version. Restart the server once the rules are in place so the changes take hold.
Fourth, check the folder. The folder holding the company file needs Windows sharing turned on, with full permission for every user who opens the file.
The H505 steps, in order
H505, along with H101 and H303, gets its own sequence in the accepted answer, and it overlaps heavily with the manual work above. Confirm hosting sits only on the server. Run the same ping tests. Open the same firewall ports. Set the same folder permissions.
One extra habit helps with H505 in particular. Open the company file by typing the server name and shared folder directly, rather than through a mapped drive letter. Mapped drives can fail to reconnect at sign-in, and H505 often follows that failure.
Two cases the tools cannot reach
Two situations sit outside this repair. The Database Server Manager does not support Network Attached Storage devices, because the manager must run on the Windows computer doing the hosting. A NAS box cannot run it. Files stored on a NAS need a supported host instead.
Hosted setups are the other exception. Books running through Rightworks or another Intuit-affiliated hosting provider fall to that provider’s own support desk, since the local tools never touch those environments.
After any of these fixes, the test is simple. Open the file on a workstation and switch to multi-user mode. If the switch holds on every machine, the block is gone.