QuickBooks Error H104 - Workstation Cannot Reach the Server

Error H104 leaves a QuickBooks workstation unable to reach the company file host in multi-user mode; our engineers explain the cause and the repair.

Error H104 appears on a workstation when QuickBooks cannot find the computer that holds the company file. Multi-user mode depends on every machine agreeing on who hosts the data. When that agreement breaks, some computers open the file and others cannot. We see it most often on small networks where hosting, firewall and name resolution settings have drifted out of step. It is almost always a settings problem, not damaged data.

The message you will see

On the workstation, the dialog usually reads:

Error H104: We're sorry, QuickBooks could not complete this action. Please try again or restart QuickBooks and open the company file again.

The wording varies a little between releases, but the H104 code is what matters for diagnosis. Single-user mode on the server still works, which is why many offices quietly abandon multi-user access. You do not have to.

What does the H104 code mean?

Every code in the H series describes one failure: QuickBooks on your workstation cannot reach the computer hosting the file. H104 is more specific. The workstation has reached the network but cannot get the network address of the host. Something is stopping it from resolving which machine holds the data.

Three things must line up for multi-user mode to work. The server runs the QuickBooks database service, and only the server hosts. Each workstation holds a healthy .ND file, the small configuration file that names the host. And the workstation can turn the host's computer name into an address. H104 means at least one of those links has snapped.

One quick check first: if the file opens normally in single-user mode on the server, the data is fine. The fault lies in the connection, not the company file.

What triggers error H104?

Four triggers account for nearly every H104 we diagnose:

  • A stale or damaged .ND file. It breaks when the server's name or network hardware changes, or when someone copied the file in from another machine.
  • Hosting switched on at a workstation. A second host gives QuickBooks conflicting answers about where the file lives.
  • Name resolution that cannot turn the server's computer name into an address. Small peer-to-peer networks often lack proper DNS.
  • A firewall or security suite blocking the ports the QuickBooks database service listens on.

Less often, the database service on the host has stopped. Rule that out first.

How do you fix error H104?

Work through the scenarios in order. Most networks are settled by the first two. Sign in as an administrator on each machine and close the company file everywhere first.

Rebuild the .ND file

  1. On the computer hosting the file, open the folder that holds the company file.
  2. Find the file with the same name as your company file and an .ND extension.
  3. Rename it so the extension reads .OLD instead of .ND.
  4. Restart the QuickBooks database service on the host, or reboot that machine.
  5. Open QuickBooks Database Server Manager on the host and rescan the folder that holds the company file.
  6. Move to a workstation and open the file. QuickBooks builds a fresh .ND file automatically.

If every workstation connects now, you are done.

Put hosting back on one computer

Only the server should host. Check each workstation:

  1. Open QuickBooks on the workstation and press F2. The Product Information window shows a Hosting line.
  2. It should read not hosting or local files only. If it says multi-user access, that machine is acting as a second host.
  3. Close the company file, then choose File, then Utilities, then Stop Hosting Multi-User Access.
  4. Repeat on every machine except the server.

On the server, the Hosting line should confirm multi-user access, and Database Server Manager should be scanning the file's folder.

Fix name resolution on the network

If the .ND file and hosting check out, test whether the workstation can find the server by name.

  1. On the workstation, open a Command Prompt and ping the server's computer name.
  2. If the name replies, name resolution works and you can skip this section.
  3. If the name fails but the server answers its IP address, open the file through the address instead. In the open dialog, type two backslashes, the server's IP, and the shared folder name.
  4. To make that permanent, add the server's name and address to the workstation's hosts file, or ask whoever manages your network to fix name resolution properly.

Open the path through the firewall

  1. On the host, open Windows Security and go to Firewall and network protection. Allow QuickBooks through, or create inbound and outbound rules for the ports shown in the Port Monitor tab of QuickBooks Database Server Manager.
  2. Repeat for any third-party security suite, which usually keeps its own port list.
  3. Reboot the host and reopen the file in multi-user mode from a workstation.

Third-party firewalls are the usual culprit, especially right after a security suite updates itself. If H104 reappears just after new software lands on the server, look there first.

Keeping H104 from returning

A little discipline keeps this error away. Host the file on exactly one machine and turn hosting off everywhere else. Keep the server's name and address stable; renaming the server invalidates every .ND file on the network at once. Run the same QuickBooks release and updates on all machines, because mismatched versions cause their own connection faults. When new security software goes in, add the QuickBooks ports before the first multi-user session, not after.

If a workstation ever shows H104 again, rename the .ND file first. It is the most common fault, and the fix takes minutes.

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.