QuickBooks Desktop users may occasionally face multi-user errors while trying to access a company file on another system. Error H505 is one such issue that occurs when QuickBooks cannot establish a proper connection with the server hosting the company file. This is a common multi-user hosting error and belongs to the H-series of errors, including H101, H202, and H303.
Although this error doesn’t damage your company files, it prevents access until network, firewall, or hosting settings are correctly configured.
What Causes QuickBooks Error H505?Several factors can trigger Error H505, including:
Incorrect hosting configuration on the server or workstation.
Corrupted or damaged .ND files associated with the company file.
Incorrect DNS settings on the network.
QuickBooks services such as QuickBooksDBXX or QBCFMonitorService not running.
Multiple IP addresses or inability of the Database Server Manager to locate the server.
Firewall or antivirus blocking QuickBooks from accessing the company file.
You can identify this error by these common signs:
QuickBooks cannot switch to multi-user mode.
Program crashes or freezes when accessing a company file.
Slow system performance when opening QuickBooks.
Error message appears:
"Problem with multi-user hosting setup: Error code H505: This company file is on another computer, and QuickBooks needs help connecting."
Before attempting any fixes, ensure the following:
Backup your company file.
Update QuickBooks Desktop to the latest version.
Run Quick Fix My Program in the QuickBooks Tool Hub.
Launch the QuickBooks Database Server Manager.
Configure firewall settings to allow QuickBooks access.
Method 1: Use QuickBooks File Doctor Tool
Install and open QuickBooks Tool Hub on the server system.
Go to Company File Issues → Run QuickBooks File Doctor.
Select the company file and allow the tool to diagnose and repair network issues.
Method 2: Create a New Folder for the Company File
On the server, create a new folder with full permissions.
Copy the .QBW company file to this folder.
Open QuickBooks in multi-user mode and check if the error is resolved.
Method 3: Configure Firewall Ports
Open Control Panel → System and Security → Windows Firewall → Advanced Settings.
Create Inbound and Outbound rules for QuickBooks TCP ports.
QuickBooks 2015: 8019, 56725, 55363–55367
QuickBooks 2016: 8019, 56726, 55368–55372
QuickBooks 2017: 8019, 56727, 55373–55377
QuickBooks 2018: 8019, 56728, 55378–55382
Allow the connection and restart QuickBooks.
Method 4: Change QuickBooks Hosting Settings
On all systems, open QuickBooks → File → Utilities.
Stop hosting multi-user access on all systems.
Enable hosting only on the server where the company file resides.
Method 5: Verify QuickBooks Services
Press Windows + R, type services.msc, and press Enter.
Locate QuickBooksDBXX and QBCFMonitorService.
Ensure Startup type is set to Automatic and the service is running.
Set Recovery options to restart the service on failure.
Method 6: Edit the Hosts File
Find the server IP address and name using ipconfig /all in Command Prompt.
Open C:\Windows\System32\Drivers\etc\hosts with Notepad.
Add entries for each workstation and server:
[Server IP] [Server Name]
Save changes and reopen QuickBooks in multi-user mode.
Method 7: Use QuickBooks Database Server Manager
Install QuickBooks Database Server Manager on the server.
Open Tool Hub → Network Issues → QuickBooks Database Server Manager.
Start scan for the company file folder.
After scanning, open QuickBooks in multi-user mode.
Method 8: Ensure Network Discovery is On
Open Control Panel → Network and Sharing Center.
Go to Change Advanced Sharing Settings.
Turn on Network Discovery and File and Printer Sharing.
Method 9: Use a UNC Path Instead of Mapped Drive
Always use a UNC path (\\ServerName\Share\Company.QBW) rather than a mapped drive.
If mapped drive fails, recreate it with proper credentials.
Following these methods will resolve Error H505 and restore multi-user access. If issues persist, consult QuickBooks Enterprise support or a certified IT professional for server-level troubleshooting.