Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I was able to open quickbooks just fine, but when I try to switch to multi-user mode, it gives me error H202.

  • Quickbooks Database Server Manager is running correctly on the file server.
  • The Quickbooks Connection Diagnostic Tool reports no errors and opens the file just fine.
  • I'm using Quickbooks 2012 (oddly, this never happened under Quickbooks 2010)

qb diagnostic tool output

share|improve this question
I've also seen this issue when trying to access a Quickbooks file from a mapped drive. Accessing it via a UNC path is a workaround for that, which may be related. –  Bigbio2002 Feb 14 '14 at 21:10

2 Answers 2

I gleaned some info from a guy that used WireShark to track down his problem with error H202.

Apparently if you open the file as \\fileserver.mydomain.com\fileshare\quickbooks.qbw, Quickbooks may have problems reaching the database server to switch to multi-user mode.

However, if you open the file as \\fileserver\fileshare\quickbooks.qbw, Quickbooks should work just fine. i.e. don't use the fully qualified domain name, use the NETBIOS name.

In our case this meant editing the lmhosts.sam file located at c:\windows\system32\drivers\etc to include the line FILESERVER #PRE

(where is the ip of the fileserver your QB file is on and FILESERVER is the NETBIOS name of the server)

You can also see that this is your problem from Quickbooks point of view if you specify the full name in the "Change hosting server" field on the diagnostic tool.

share|improve this answer

Michael's answer above drove me to a resolution for us as well. We were getting H202 error in multi-user environment unless we had a user logged on to the company file at the host server first and then the clients could log on fine. We are/were using a CNAME instead of the actual hostname of the host server. So we had a friendly CNAME of quickbooks so they could map as \quickbooks\\companyfile, but with this we experienced the errors mentioned. So I just switched to use the actual hostname of the computer and this seems to resolve this issue. Very strange that it works fine without error using the CNAME if someone is logged on at the host server first though.

share|improve this answer

protected by Community Jul 4 '14 at 0:47

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.