Quickbooks 6000, 83, H202 Error – Quickbooks Database Server Manager

Quickbooks database multi-user mode stopped working, H202 Error.

The scenario is that Quickbooks stopped working in mutl-user mode after years of working. The cause of the problem may have been because the server had it’s ip address changed. The Quickbooks server is a file server that also has the Quickbooks Database server manager installed on it. It had to be moved to another location and thus it’s ip address had been changed. Prior to this move , the Quickbooks server manager worked well for multi-user mode access to Quickbooks databases. The tests in included using newly created databases and old pre-existing databases. None could be used and accessed by multiple users.

QuickBooks Error H202 Multi-user mode Problem. Quick Books Database Manager

QuickBooks Error H202 Multi-user mode Problem. Quick Books Database Manager

H202 Error: Could not connect to Quickbooks database server

The server and client were able to communicate with no issues. No firewalls were preventing access, this was thoroughly vetted out and tested to not be the problem and but just using pings but also testing for listening ports and to be sure firewall exceptions were added for all ports even though windows firewall was already disabled for  the domain.

Quickbooks H202 Error

After trying an assortment of potential fixes, including running a repair installation of the Quickbooks Database server manager, a new install of a newer version of the server manager worked. The clients were version 13 of Quickbooks and the Database server manager was version 11. installing version 13 on the server fixed the problem immediately. Perhaps uninstalling and re-installing the existing version 11 may have worked but since version 13 was available, it was used instead and now it matches the client version of Quickbooks.




Move QuickBooks Database Files to New Server Computer

Migrate QuickBooks Enterprise Database to New Computer

Years ago just thinking about working with Quickbooks in regards to moving the company database made me un-easy. Although I am comfortable working with application databases and share, permissions, windows servers, etc., Quickbooks was always a hassle.

Just recently a customer who had Quickbooks Enterprise on server already, the mistake was originaly was that the server was an XP pro system.  It ran well but they outgrew the 10 connection limit imposed by Windows XP. This was the problem. SO, they purchased a low end HP server which was more than what they needed for this Quickbooks database move. The server is an HP ML 110 G7. It had a pair of SATA 1TB drives. I used the on-board SATA RAID and created a 1+0 mirrored RAID volume. This was more that enough for this small office and already they had a redundancy edge over their XP server.

Transfer Quickbooks Enterprise Database Files to Windows 2008 R2 Server

The operating system I installed was Windows Server 2008 R2 with SP1. This i was expecting to be a problem as Windows 2008 R2 is 64 bit. As it turns out, it was no problem at all.  The OS installed without issue. I used HP smart start 8 to begin the installation and once the HP smart Start requested the OS CD to be inserted it was soon complete after that. I ran through all windows updates and that completed flawlessly too.

Quickbooks Requires .NET Framework and IIS

Quickbooks enterprise requires IIS to be installed and although I did not know that until I ran the Quickbooks installation and it checked for IIS as a pre-requistite. Had I known, I would have installed it even before doing Operating system updates through windows updates. That’s just a preference of mine to have IIS or other roles, as many as possible  that will be required, installed before starting the updates. But anyway, there were no issues. I installed IIS with the options I usually use for other applications like Exchange except in this case I left out authentication options to simplify access to he IIS web site. The reason Quickbooks needs IIS is mainly because it requires .NET frame-work to be enabled. .NET frameworks 3.5 comes with the OS but the “feature” is not enabled. To enable it, IIS needs to be added and enabled.

Disable Quickbooks Services on Old Server

Once these issues were worked out, the Intuit Quickbooks installation was run again. I recall  in the past, there were separate installer files. Intuit has done a fantastic job in simplifying the installation. One installation installer file. Before starting the Quickbooks enterprise  installation, I had all users log off the running current old server. Once they were logged out of Quickbooks, I disabled the Quickbooks services on the old server. In this case there four services but one was already disabled. So 3 services for quickbooks were stopped and disabled from starting up.

Copying the Quickbooks My Company folder to New Server

The My Company files were copied over to the new share I had created on the 2008 R2 server for Quickbooks Enterprise. That file copy of course went fine. Their DB was near a GB. Once the quickbooks database and all associated files for the my company data were copied over, the installation continued with clicking next… I chose “run Quickbooks on this computer and share option”

Re-register Quickbooks on New Server

Have your Quickbooks software serial number and software code handy. Although you may have already registered your software this is considered a new install and therefore the software will require re-registration. Don;t worry however, if you do not have it handy, the Quickbooks software will run for 30 days unregistered. Another nice feature Intuit added to the whole process.

All Quickbooks Users Were Carried Over from Old Server Computer

Once the installation completed, I simply started the Quickbooks application on the server and opened the database using the local path, not a UNC path. It opened up just fine. From the workstations, I changed a drive letter that was previously mapped to the old server sahre to the new server share for Quickbooks. After the drive letter was re-mapped to the new server, Quickbooks started right up with no issues.. If you’re not using drive mappings, UNC paths are just fine. An example is \\servername \ sharename \ quickbookscompanyfolder \ companyfile.qab .

That was it, all workstaions openned the old database on the new server. Users did not have to be re-created on the new server for Quickbooks database access. All users that used the company  database ont he old server were able to log in to Quickbooks on the new server.