H202 frequent errors

I've got your back, @RJ4242.

Thank you for sharing the complete details of your concern about getting the error code H202.

The error means that something is blocking the multi-user connection to your server, and I'm glad to help fix this issue. The following steps outlined below will guide you through getting rid of the error:

Step 1: Follow the steps depend on how you host your company files.

Step 2: Download and install the QuickBooks Tools Hub on your server.

Step 3: From the Tools Hub, run the QuickBooks Database Server Manager on your server.

Step 4: Check the services on your server.

For instructions and detailed solutions for each step above, please refer to this article: How to fix Error H202 and H505.

Just a heads up, make sure to update QuickBooks Desktop  to its latest release. This is to keep the software updated and get new features and fixes.

Let me know how everything goes by clicking the Reply button below. I'm always around to help ensure your success. 

Apologies for the delay in responding.  I have followed the above steps, we had performed those prior to my initial posting.

This particular office has 3 users who work in QB.  All are up-to-date on the latest release.  None of the 3 are hosting multi-user mode.  At some point, they are just unable to enter multi-user mode.  The time varies, but after running QuickBooks Database Server Manager they are able to work in that mode.  This will last anywhere from 2 hours to 2 days before it just suddenly stops working and we have to run QB DSM again.  Very frustrating.  This is a brand new server and was not happening on the old server, so it's possible that something was not migrated or set up correctly, but it was basically done as many other server migrations we have done in the past.

Hello there, @RJ4242.

I'm grateful for the come information that you've given regarding this concern. I'd like to ensure that this gets resolved so you and your other users will be able to utilize the program on a multi-user mode with no issues.

To better isolate this matter, I recommend contacting our Customer Care Team. They'll be able to initiate a remote viewing session that can help determine the root cause of this problem since the resolution presented above didn't work.

To contact our support:

1. Click on Help at the top menu bar.
2. Press on QuickBooks Desktop Help. 
3. Select on the QuickBooks support link. 
4. Follow the instructions to connect with our representatives.

To add up, you can also check out this reference, which talks about fixing error H202 if the hosting company file is on a non-Windows Server  in case you need it in the future: Error H202: when hosting company file on a non-Windows Server.

Please let me know on how that call goes. I'll be around to assist you if you need more help. Take care!

I was finally able to work with QuickBooks support as you suggested.  We made a couple of changes to permissions on the QB folder, giving the QBDataServiceUser30 explicitly full permissions.  We also made changes to the service QBData30, changing the startup type from manual to automatic, changed the logon from the specific account QBDatatServiceUser30 to local system account, and checked the box to Allow service to interact with desktop.

2 days later, users are not able to go into multiuser mode.

Last night set an exclusion of the QB port number to prevent DNS from acquiring that port number.  We will see if that works.

I am curious if you ever found a resolution to this problem. I have this problem here at my own company and at 2 client company's. Its super frustrating and yes I've followed almost exactly the same path you took to get to the same point. I'd really love to find a resolution sooner rather than later. 

This is not the impression I want you to feel, @emillme2.

I appreciate you for following the steps above to resolve the error H202. I'm here to help you fix the problem by providing another workaround.

Updating QuickBooks Desktop and installing Database Server Manager is one of the initial steps to fix the dilemma. Since the actions above didn't work, let's try another step to isolate the error by editing the host's file. Follow these steps on your server computer first. Then, do the steps again on your workstations.

Before doing this, I'd suggest reaching out to an IT professional or refer to this Microsoft article to know more about DNS settings. Once confirmed, you can proceed with the instructions. 

1. Press Windows+R on your keyboard.
2. Type “cmd” in the Run window, then press Enter.
3. Type “ipconfig /all” (make sure there’s a space after ipconfig), then press Enter.
4. Take note of the hostname and IP address (or IPv4).
5. Close QuickBooks and Open the Windows Start menu on the server computer.
6. Choose Computer and go to either C:\Windows\System32\Drivers\Etc or C:\Windows\Syswow64\Drivers\Etc
7. Double-click the host file, then pick Notepad.
8. Enter the IP address followed by the computer name.

If the issue keeps going, I'd recommend communicating with our Technical Support. They have available tools to investigate the main cause of the error and provide another workaround. You can follow the steps presented by BetyJaneB above. Also, ensure to call them within business hours to address your concern quickly. 

In case you're using Windows Server 2012 Essentials R2, you can visit this article for other troubleshooting steps: How to fix Error H202 using Essentials R2.

Feel free to let me know if you have other questions about multi-user mode or how the call goes. I'm always there willing to help.  

Hi emillme2.  I was never able to resolve the issue.  I'm with an MSP and we have 4 or 5 customers who are having this issue.  I have one customer that it is affecting worse than the rest (almost daily) was the one I had QB support remote in and look at the issue.  Everything I tried with them did not resolve the problem.  It's an annoyance, but at least scanning the database is a quick workaround.  I just wish the problem could be resolved.  If you have any better luck, please post back, I'd love to stop doing this several times a week,

whoops, replied with the wrong account.  :)