Persistant H2O2 error

gbkillen · ‎August 15, 2025

I had Quickbooks 2022 Enterprise installed on Windows Server 2012R2 with 3 users accessing any of 3 different company files. Multi-user mode worked. Since server 2012 is end of life, we replaced it with a 2022 Server, backed up data files, and restored to the new server. Moved DC and DNS roles to the new server and made sure the domain was healthy, and names were resolving. Then I installed QB 2022 desktop in Multi-user hosting mode. Multi-user mode isn't working but users can open files from server in single user mode. My first call to QB level 1 support. it was suggested we update to version 2024. we did this, confirmed services were running, firewall was open, share permissions OK, Multi-user hosting wasn't enabled on any other PC's, Tried tool hub etc. No change. I went through a 2nd support call and finally a 3rd to level 2 support this time of about 4 hours. They finally gave up and told me it was my network.
This is where it gets interesting. If client workstation opens a file in single user mode it doesn't show open in Database manager. If a 2nd person tries to open this Company file they are told the file is open, they need to switch to Multi-user. then it fails with H2O2 error. But if I open the company file on the server first, it will show the connection in database manager, then another user can open in Multi-user as well. and the additional users also show up in database manager. I have even been able to take a file, open on server first, then a 2nd user open, then a 3rd user. then close file the on server and it will stay in Multi-user mode until everyone closes file. Another odd behavior is when I run Tool Hub and click on the database server manager icon. I get an error "The Quickbooks Database Manager cannot run until it has been setup on this computer. " I even get this if the database manager gui is onscreen and shows as running.
At this point I don't know whether to just remove entirely and install Hosting only mode. We don't really need QB desktop on the server. Another randon thought. The servers hostaname is 16 Characters, I think I saw where Quickbooks truncated it and last the last character. If this is a possible issue the server can be renamed.

Tori B · ‎August 15, 2025

Thanks for all those details, @gbkillen.

How are you doing today? I hope all is well.

I'm glad you mentioned the server characters being 16. Windows NETBIOS names are max 15 characters, and QuickBooks uses the NETBIOS name in its .ND files for peer-to-peer connections. If your server’s hostname is 16 characters, the .ND file is storing a truncated name, which can cause exactly the kind of “network can’t find host” errors you’re seeing.

If the truncated name doesn’t resolve in DNS, QuickBooks can’t make the connection unless the Database service is already open from a local session.

With that being said, yes, let's go ahead and get that server name changed to 15 characters.

If you still notice an issue after renaming the server, you can completely uninstall all QuickBooks components from the server. When you initially installed it, there could have been an issue that caused it to install incorrectly.

Here's how:

Open the Control Panel. Click on Programs, uninstall QB Desktop and QuickBooks Database Server Manager.
Delete:
- C:\Program Files\Intuit
- C:\Program Files (x86)\Intuit
- C:\ProgramData\Intuit folders

Now, let's reinstall: Install QuickBooks Database Server Manager.

Once reinstalled, it's important to scan the folder that contains the company file. Here's how:

Go to the Scan Folders tab.
Select Browse. Then select the folders that hold your company files (QBW).
Tap on OK when you're finished.
When you’re ready, hit Start Scan.

On each client computer:

Delete the old .ND and .TLG files for the company
Open the file from the network share in multi-user mode

I also wanted to mention, you're right with your thinking. If no one will use QuickBooks on the server itself, you can install Hosting Only mode.

That should do the trick. If you still have issues, please don't hesitate to let me know. I'm happy to help. Take care!

gbkillen · ‎August 18, 2025

I suspected the long hostname could be the issue. Since this is a Domain Controller in a production environment I need some time to implement the rename when things can be rebooted. But I will get it done and report back.

Thanks,

gbkillen · ‎August 18, 2025

I suspected the long hostname could have been the issue. Since this is a Domain Controller in a production environment I will need to plan the rename when things can be rebooted. But I will reply with the results.

Thanks,

Topics

Training

Community

Resources

Persistant H2O2 error