cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Level 2

H202 Error after QB Migration to New Server (Multi-User, Domain, Server, Non-Domain PCs, Virtualized)

We are doing a QuickBooks migration from single computer (Windows 10) hosting QuickBooks as a "server" (in a Workgroup - Computer Name = QB) to a new server (Server 2019) virtualized on a new domain setup. Currently the accounting team is connecting to QuickBooks through a mapped drive to the computer's name (QB) in the same subnet. The accounting team computers are not on a domain yet. First we verified data on all the company files then moved just the company files over to the new server. We then re-mapped the end users drive to the new server using a CNAME that points to the new accounting server. Each end user computer DNS is pointing to the new domain controller so it can reach. Every time we opened a company file off the new server with the "open file in muti-user mode" we would get this H202 error. We have tried everything in this thread https://quickbooks.intuit.com/learn-support/en-us/open-programs/how-to-fix-error-h202-and-h505/01/18... and nothing is working. We did a ton of research and implemented tons of fixes, changes, etc. and still nothing is working.

Solved
Best answer 01-28-2020

Best Answers
Highlighted
Level 2

H202 Error after QB Migration to New Server (Multi-User, Domain, Server, Non-Domain PCs, Virtualized)

The only way to fix H202 for us was to remap the end users drive to the server name exactly what was in DNS (FQDN) that is hosting the company files. Creating a different DNS record (CNAME) that doesn't match the server name doesn't work. For example, if the server name is SEA-QB01, you have to map the end users drive exactly like that plus the domain.com (SEA-QB01.domain.com). If you do a CNAME like QB>SEA-QB01 that doesn't work. Even setting up another A record that points to the new server's IP address didn't work. Mapping to IP address didn't work either.

View solution in original post

1 Comment
Highlighted
Level 2

H202 Error after QB Migration to New Server (Multi-User, Domain, Server, Non-Domain PCs, Virtualized)

The only way to fix H202 for us was to remap the end users drive to the server name exactly what was in DNS (FQDN) that is hosting the company files. Creating a different DNS record (CNAME) that doesn't match the server name doesn't work. For example, if the server name is SEA-QB01, you have to map the end users drive exactly like that plus the domain.com (SEA-QB01.domain.com). If you do a CNAME like QB>SEA-QB01 that doesn't work. Even setting up another A record that points to the new server's IP address didn't work. Mapping to IP address didn't work either.

View solution in original post

Need to get in touch?

Contact us