H202 is a multi-user connection error: a workstation is trying to open a company file hosted elsewhere, but QuickBooks cannot complete the connection to the host/server.
Use the evidence below to identify the failing layer before you change files, reinstall software or alter a production server.
What this error means in practice
H202 is a multi-user connection error: a workstation is trying to open a company file hosted elsewhere, but QuickBooks cannot complete the connection to the host/server.
The useful SEO/AEO answer is not simply “run a repair tool.” The key is to determine whether the error belongs to the application, company file, Windows/network, payroll/update or license/subscription layer. That avoids random fixes and creates a repeatable troubleshooting path.
Typical signals
- The file opens locally on the server but not from one or more workstations.
- The error appears when switching to multi-user mode.
- Windows can sometimes see the server even though QuickBooks cannot open the company file.
Most likely causes
Step-by-step diagnostic path
- Confirm exactly which computer stores the .QBW file and designate that machine as the intended host.
- On every workstation, verify hosting is not enabled; only the intended server/host should host the company file.
- From Windows, confirm the workstation can reach the server and access the shared company-file folder.
- On the server, confirm the appropriate QuickBooksDBXX service and QBCFMonitorService are running.
- Run Database Server Manager/Tool Hub network diagnostics on the server and rescan the company-file folder.
- If the file was moved or the .ND file is suspect, recreate the network descriptor through the supported Database Server Manager process.
- Review firewall rules only after basic Windows connectivity is confirmed.
What your test result tells you
| What you observe | What it suggests | Next move |
|---|---|---|
| A local server copy opens, workstation copy fails | Network/hosting layer | Check host role, share access and DB services |
| Windows share cannot be opened | Windows/network layer | Fix name resolution/permissions before QuickBooks |
| Only one workstation fails | Endpoint-specific layer | Compare that workstation with a working one |
Common mistakes to avoid
- Enabling hosting on every workstation.
- Changing firewall rules before confirming the server name/share actually works.
- Moving the production .QBW file repeatedly without a verified backup.
- Assuming H202 proves the company file itself is corrupt.
How the environment changes the diagnosis
On a single Windows computer, there is no server path to troubleshoot, so multi-user errors should immediately raise the question of whether the file is actually being opened from another machine or hosted environment. In a normal office network, document the server name, share name and company-file folder. In a hosted desktop environment, the hosting provider may control the server, firewall and service layer; in that case local workstation changes may not fix the underlying host problem.
Do not treat a mapped drive letter as proof that the network is healthy. Two users can map the same drive letter to different underlying paths, and Windows can cache credentials even when QuickBooks database communication is failing. The more reliable comparison is the actual host name, share path, permissions and whether the same file opens from a known-working workstation.
Three practical scenarios
How to verify the issue is actually fixed
- Repeat the exact action that originally failed; do not rely only on the absence of an error at startup.
- Close and reopen QuickBooks once so you know the fix survives a normal restart of the application.
- If the issue was network-related, validate from at least one affected workstation and then another user before declaring the server fixed.
- If the issue involved payroll or company-file changes, review the resulting data before normal production work resumes.
- Write down the successful configuration and keep the backup/rollback copy until the business has completed a normal work cycle.
Data-safety boundary
When to stop and escalate
Stop self-troubleshooting when the next step could change payroll filings, direct-deposit transmission, bank activity, company-file integrity, subscription ownership or a production Windows server you cannot restore. Account and entitlement issues should be handled through the official product provider; operating-system or network issues may require a qualified IT administrator.
What to collect before asking for help
- QuickBooks product, year, edition and current release.
- Windows version/build and processor type where compatibility may matter.
- Exact error text/code and the action that triggered it.
- Company-file location: local PC, Windows server, hosted desktop or other location.
- Whether one user/file is affected or every user/file.
- The most recent update, migration, network or permission change.
Related diagnostic routes
Use these internal resources only when the result of the tests above points to that layer.
Multi-user troubleshooting
Use this page when the evidence points to this layer.
RelatedNetwork troubleshooting
Use this page when the evidence points to this layer.
RelatedFirewall guide
Use this page when the evidence points to this layer.
RelatedDatabase Server Manager
Use this page when the evidence points to this layer.
Primary sources and update context
Product procedures can change by QuickBooks release and service status. These official references were checked when this independent page was updated on 2026-09-05.
Independent editorial note: this page does not claim to replace Intuit, Microsoft, a payroll professional or your network administrator. It explains how to isolate the issue and when to use the official workflow.