What do you see on the workstation?

How QuickBooks multi-user works: One computer — the server — hosts the company file and runs QuickBooks Database Server Manager (QBDSM). QBDSM manages the connection between the server and all workstations over the local network. Workstations don't open the file directly — they connect through QBDSM. If QBDSM stops, has a stale .ND file, or the server's firewall blocks its ports, all workstations fail simultaneously. This is why the server and QBDSM are always the first things to check — not individual workstations.

Workstation Has Hosting Enabled

Most common cause of H101/H303 — one or more workstations has "Host Multi-User Access" enabled. Only the server should host. A workstation attempting to host creates a conflict where the file's authoritative location becomes ambiguous.

QBDSM Stopped or Not Scanning the Folder

Most common cause of silent single-user mode — QBDSM stopped after a Windows Update, server restart, or crash. Without QBDSM running and scanning the company file folder, workstations cannot connect and QB silently falls back to single-user.

Firewall Blocking QuickBooks Ports

Most common cause of H202/H505 — Windows Firewall or antivirus blocking the ports QBDSM uses to communicate between server and workstations. Common after a Windows Update that resets firewall rules or a new antivirus installation.

Stale or Corrupt .ND File

The Network Descriptor file (.ND) stores how workstations reach the company file. After a server name change, IP address change, or network reconfiguration, the .ND becomes stale — pointing to a path that no longer works.

QB Version Mismatch Across Computers

All computers on the network must run the same QuickBooks version and release. A workstation running QB 2023 R3 and the server running QB 2023 R1 creates protocol mismatches that silently break multi-user connectivity.

Folder Permissions Insufficient

The QBDataServiceUser account doesn't have Full Control on the company file folder. Common after a server OS reinstall, domain policy change, or migration to a new server. Without these permissions, QBDSM cannot manage the file for network users.

METHOD 1 Check Hosting — Turn It Off on All Workstations H101 · H303 · Hosting conflict — do this first

Incorrect hosting is the single most common multi-user problem. Only the server should host. Every workstation that has hosting enabled creates a conflict. Check every computer on the network — not just the ones showing errors.

METHOD 2 Restart QBDSM and Run a Fresh Scan No error but QB opens single-user · After server restart

QuickBooks Database Server Manager is the service that enables multi-user access. If it stopped — which happens silently after Windows Updates or server restarts — workstations fall back to single-user mode without any error message. Restarting and rescanning takes 3 minutes.

METHOD 3 Add QuickBooks Firewall Exceptions H202 · H505 · After Windows Update or new antivirus

Windows Firewall blocking QuickBooks' communication ports is the primary cause of H202 and H505. QuickBooks uses specific ports depending on the version — all must be open on the server's firewall.

METHOD 4 Rename .ND File and Run QBDSM Scan After server rename, IP change, or network reconfiguration

A stale .ND file routes workstations to the wrong server path. Renaming it forces QBDSM to generate a fresh one with the current correct server information.

METHOD 5 Fix Folder Permissions for QBDataServiceUser After server OS reinstall or domain policy change

QBDSM runs under the QBDataServiceUser Windows account. If this account lost its permissions on the company file folder, QBDSM cannot manage the file for network users — causing silent single-user fallback or H-series errors.

METHOD 6 Verify All Computers Are on the Same QB Version Intermittent failures · After updating QB on one machine only

Version mismatches between the server and workstations cause intermittent and hard-to-diagnose multi-user failures. All computers must run the identical QuickBooks release (same year AND same R-number).

METHOD 7 Run QuickBooks File Doctor All above tried — still failing

File Doctor diagnoses and repairs both network configuration issues and company file damage that can cause multi-user failures. Run it from the server computer for the most complete diagnosis.

Why does multi-user keep breaking after every server restart?

The most common cause of recurring multi-user failures after server restarts is QBDSM being set to Manual startup instead of Automatic. When the server restarts, QBDSM doesn't start automatically — workstations cannot connect until someone manually starts it. Fix this permanently: open services.msc on the server → find QuickBooksDB[XX] → right-click → Properties → set Startup type to Automatic → Apply. Also set QBCFMonitorService to Automatic. This one change eliminates the most common recurring multi-user failure pattern.

Do I need QuickBooks installed on the server, or just Database Server Manager?

You have two valid options. Option 1: install the full QuickBooks Desktop application on the server and enable hosting. Option 2: install only QuickBooks Database Server Manager (available as a separate free download from Intuit) on the server — no full QB installation required. QBDSM alone is sufficient for the server to host the company file for workstations. The advantage of QBDSM-only is that the server doesn't need a QuickBooks license and uses fewer resources. The advantage of full QB on the server is you can open the company file directly on the server itself as a third option. Both configurations work correctly for multi-user access.

How do H101, H202, H303, and H505 differ from each other?

All four are H-series multi-user errors but they identify different failure points. H101 means the workstation cannot connect because it is not set up to host and the file is on another computer — usually caused by incorrect hosting settings on workstations. H202 means the workstation cannot communicate with the server — usually caused by a firewall blocking ports or QBDSM not running. H303 means the workstation is set to host the file but has been told the file is on another computer — same cause as H101 but from the reverse perspective. H505 means the workstation is set to host but the file is on the server — hosting is wrongly enabled on the workstation. In practice: H101 and H303 → fix hosting. H202 and H505 → fix firewall and QBDSM. The fixes for all four are covered in Methods 1–3 above.