QuickBooks Error H304 - Workstation Cannot Reach the Hosting Computer

QuickBooks Error H304 blocks a workstation from opening a shared company file in multi-user mode; our engineers explain the triggers and the repair.

Error H304 appears on a workstation, never on the computer that stores the company file. QuickBooks has found the host across the network but cannot finish the conversation that opens the file for shared use. The fault sits in the hosting setup, the database service, or the connection files between the two machines.

What does the message say?

QuickBooks presents the H-series message with the code in brackets at the end. Most releases read:

You are trying to work with a company file that is located on another computer, and this copy of QuickBooks cannot reach the server on that computer. (H304)

Wording shifts slightly between releases, but the sense does not change. QuickBooks knows the file exists on another machine, and it cannot reach that machine's database service. The company file itself is usually fine.

What does H304 mean?

The H-series codes record how far the connection attempt gets. QuickBooks on a workstation never opens a shared file directly. It asks a database service on the host to hand out the file, and the codes describe where that request stalls.

H304 sits partway along. The workstation has found the host, but the host is not answering the way QuickBooks expects. The host computer usually needs additional installation and setup, or more than one machine is acting as the host at once. The two copies of QuickBooks simply disagree about who owns the file.

What triggers it?

A handful of situations produce this code, and upgrades account for most of the cases we see:

• Hosting is switched on at a workstation as well as at the host, so two servers compete for the file.
• QuickBooks Database Server Manager is missing on the host, or its Windows service has stopped.
• The .ND network file that maps the connection has been damaged, often by an abrupt shutdown.
• A firewall or antivirus update has started blocking the ports the database service uses.
• The company file sits on an external drive or a cloud-sync folder, so nothing is truly hosting it.

How do you fix it?

Work through these scenarios in order. Each targets a common trigger, and you can stop as soon as multi-user mode opens.

More than one computer is hosting. This is the most common cause.

1. On every computer except the one that stores the file, open QuickBooks without the company file.
2. Choose File, then Utilities.
3. If you see Stop Hosting Multi-User Access, select it. That machine has been acting as a second host.
4. If you see Host Multi-User Access, leave it alone; hosting is already off there.
5. Repeat on each workstation, then restart QuickBooks on the host and try the file from a workstation.

The database service on the host is missing or stopped.

1. Open QuickBooks Database Server Manager on the host. It installs from the same installer as your QuickBooks release.
2. Scan the folder that holds the company file, adding the folder to the list if it is empty.
3. In the Windows Services list, find the service named QuickBooksDB followed by two digits.
4. Set its startup type to Automatic, start it, and confirm it stays running.
5. Open the company file from a workstation in multi-user mode.

The .ND connection file is damaged.

1. On the workstation showing the error, open the folder that holds the company file, browsing through the network if the file sits on another computer's drive.
2. Find the file that matches your company file name and ends in .ND.
3. Rename it so the name ends in .OLD.
4. Open Database Server Manager on the host, scan the folder again, and open the file from the workstation. QuickBooks writes a fresh .ND on its own.

A firewall is blocking the ports. QuickBooks File Doctor, which ships with the QuickBooks Tool Hub, resets firewall permissions for you. Install the Tool Hub on the affected workstation, run File Doctor, and choose the network and hosting check. Enter the admin password when asked, then let the test run to the end.

Folder permissions are too tight.

1. Right-click the folder that holds the company file and open its sharing settings.
2. Give the QBSDataUser group that QuickBooks creates full control there and under the Windows security tab.
3. From the workstation, open the file through the network location rather than a mapped drive letter.

Keeping it from returning

A few habits keep the code away once the file opens.

• Keep hosting switched on only at the machine that stores the file, and check File, Utilities after any new installation.
• Re-scan the file folder in Database Server Manager whenever the file moves or the folder is renamed.
• Leave the QuickBooksDB service set to Automatic so a reboot always brings it back.
• Expect the database ports to change with each release year, and renew the firewall rules after every upgrade.
• Keep the file on the host's local drive; external disks and cloud-sync folders invite repeat H-series errors.

If the code survives the hosting checks, the service scan, and a rebuilt .ND file, note the exact message wording and the QuickBooks release shown at the top of the window. Our engineers use both details to narrow the cause quickly.