QuickBooks Error H510 -- Multi-User Hosting Configuration Fix

Error H510 blocks multi-user access when the server workstation hosting configuration is mismatched, and our engineers walk through resolving it step by step.

QuickBooks Error H510 is a multi-user hosting error that appears when a workstation tries to open a company file stored on another machine but cannot resolve the hosting path correctly. The error stops users from switching the file into multi-user mode and, in most cases, points to a hosting-configuration mismatch between the server workstation and the client machines trying to reach it.

What the Error Message Says

The full message typically reads:

Error Code: (-6105, -1005) or H510. QuickBooks cannot reach the company file on the host computer. The hosting configuration may be incorrect.

In some environments the message is shorter:

QuickBooks Error H510: An error occurred when QuickBooks tried to access the company file.

The exact wording varies by QuickBooks Desktop version and edition, but the error code H510 is consistent.

What the Code Means

H-series errors fall under the umbrella of multi-user or hosting errors. H510 specifically indicates that QuickBooks Database Server Manager on the host cannot properly route the file request from a client workstation. The database server is either not running, not configured as the host, or blocked from accepting inbound connections. Unlike file-damage errors (C-series), H510 is a connectivity and configuration problem — the company file itself is usually intact.

What Triggers It

Our engineers see H510 most often in these scenarios:

1. Hosting is enabled on more than one machine. Only the server workstation should have hosting turned on. When a client machine also has hosting enabled, QuickBooks gets conflicting information about which machine owns the file.

2. QuickBooks Database Server Manager is not running or has not scanned the folder containing the company file.

3. The company file folder lacks correct Windows folder permissions, preventing the database server from sharing the file.

4. Firewall or antivirus software is blocking QuickBooks ports, preventing the client from reaching the host.

5. The .ND (Network Descriptor) file is damaged or stale, causing QuickBooks to look for the host at the wrong address.

How to Fix It

Our engineers recommend working through these in the order shown, starting with the most common cause.

Scenario 1: Hosting is enabled on multiple machines

1. On the server workstation (the machine storing the company file), open QuickBooks, go to File ▸ Utilities. You should see Host Multi-User Access listed (not Stop Hosting Multi-User Access). If you see "Stop Hosting," hosting is already on — leave it.
2. On every other workstation, go to File ▸ Utilities. If you see Host Multi-User Access, do not click it — hosting is already off. If you see Stop Hosting Multi-User Access, click it to turn hosting off on that machine.
3. Restart all machines and try opening the file in multi-user mode again.

Scenario 2: Database Server Manager has not scanned the folder

1. On the server workstation, close QuickBooks.
2. Open QuickBooks Database Server Manager from the Windows Start menu.
3. Go to the Folders tab and click Browse. Select the folder containing your .QBW file.
4. Click Start Scan.
5. After the scan completes, open QuickBooks on a client workstation and attempt multi-user access.

Scenario 3: Damaged or stale .ND file

1. On the server workstation, close QuickBooks.
2. Navigate to the folder containing your company file.
3. Locate the file ending in .ND (it shares the name of your company file). Right-click and rename it to CompanyFileName.QBW.ND.OLD.
4. Open QuickBooks Database Server Manager and rescan the folder as described in Scenario 2.
5. Open QuickBooks and switch to multi-user mode. QuickBooks recreates a fresh .ND file automatically.

Scenario 4: Windows folder permissions

1. On the server workstation, right-click the folder containing the company file and select Properties ▸ Security.
2. Ensure the user group Everyone (or QBDataServiceUser) has Full Control or at minimum Read and Execute, List, and Write.
3. Click Apply ▸ OK and test from a client machine.

Scenario 5: Firewall blocking QuickBooks ports

1. Open Windows Defender Firewall (or your third-party firewall console) on the server workstation.
2. Add inbound and outbound rules for the following QuickBooks executables: QBDBMgrN.exe, QBW32.exe, and FileManagement.exe.
3. Ensure ports 8019 and 10172–10183 are open for inbound TCP traffic.
4. Restart the server workstation and test again.

How to Prevent It Recurring

• Keep hosting enabled only on the server workstation. Audit this after any new install or update, since QuickBooks updates can sometimes reset the setting.
• After any server workstation reboot, confirm the QuickBooksDB service is running in Windows Services before users connect.
• Rescan the company file folder in Database Server Manager after moving the file, renaming it, or installing a new QuickBooks version.
• If you replace or rebuild a workstation, verify hosting is off on the new machine before it opens the company file for the first time.
• Keep firewall rules for QuickBooks ports persistent across updates, and document them so they can be re-added quickly if security software is reinstalled.