QBDSM Not Running or Not Scanning

Primary H202 cause — QB Database Server Manager on the host computer isn't running, or is running but hasn't scanned the folder containing the company file. Workstations can't connect because QBDSM's port 8019 isn't active for this company file. Open QBDSM on the host → Scan Folders → Start Scan.

Firewall Blocking Port 8019 on Host

Windows Firewall on the host computer blocks inbound connections on port 8019. The workstation's QB sends a connection request but it's silently dropped. QBDSM's Scan Folders automatically opens the required ports — run it on the host. If a third-party firewall is installed, add QBDSM and QuickBooksDB to its exceptions.

QuickBooksDB Service Stopped on Host

The QuickBooksDB[XX] Windows service on the host has stopped — often after a Windows Update, system restart, or service crash. QBDSM can't function without this service. Services.msc on the host → QuickBooksDB[XX] → Start → set to Automatic startup.

Workstation Hosting Instead of Server

The workstation showing H202 has "Host Multi-User Access" enabled — it's trying to be both a client and the host simultaneously. When QB switches to multi-user, it tries to connect to the server but its own hosting status creates a conflict. File → Utilities → Stop Hosting Multi-User Access on the workstation.

Incorrect QB Version on Workstation

The workstation's QB version doesn't match the server's QB version. When switching to multi-user, QB versions must be identical across all machines. A version mismatch prevents QBDSM from recognising the connection request. Update the older machine to match.

DNS Resolution Failure

QB uses the server's hostname to establish the multi-user connection. If DNS can't resolve the server hostname from the workstation (common when the server was renamed or the DNS entry is stale), H202 appears. Try using the server's IP address directly in the QB company file path instead of the hostname.