Hi there, I wonder if anyone can help. We host our company file on a server and have recently upgraded both of our workstations that access that company file to Quickbooks Desktop 2019. All went well but when I tried to switch to multi-user mode it came up with error H202. I followed the suggestions to deal with that but still no joy. We haven't changed anything on the server where the company file sits so access to it should be the same as it was when we were both running Quickbooks Desktop 2014.
I've printed off numerous help pages and run database scans, the intuit file doctor etc but nothing seems to be helping.
Has anyone else encountered this upon upgrade ?
Any help would be most welcome
Welcome to the Community, SueMapp. I'd be glad to lend a hand in fixing error H202.
To get this be fix, use the QuickBase Database Server Manager. Here's what you'll need to do:
That's it! For more detailed steps, I'm including a helpful article that you can check: https://quickbooks.intuit.com/community/Help-Articles/Error-H101-H202-H303-or-H505-when-opening-your....
I want to ensure that this is taken care of for you, so please feel free to let me know how it goes. Have a great day!
Hi there, thanks for coming back to me. I have tried this solution several times but it hasn't worked. I have two workstations running QB Desktop 2019 and only one user can get in at a time. I've run the scan several times to try and cure it so that we can work in multi-user mode but it doesn't make any difference. I've been googling various solutions but cannot fathom out why it now won't work. It was fine when we were running QB Premier 2014
Any other suggestions would be great, thanks
The error you are receiving relates to a network issue. Did you scan the folder where the files are located rather than the drive?
This can also be caused by the files being stored deep into the system (more than 4 folders deep). If the files are stored more than 4 folders deep you will have to move it to a different server location.
We recommend that your IT team check services.msc to ensure that the 2019 version of Database Server Manager is set to automatic start and is running while the DNS server is set to automatic delayed start. For this type of error we recommend that you contact our telephone support team, 0808 168 9535.
Hi there, thanks for your responses, I've checked the folder depth and the company file is located as - drive letter\shared folders\Quickbooks 2019\.QBW file - is this too long ?
Secondly I've rerun the scan and I still can't put QB into multi-user mode.
I've checked on the startup properties of both the Quickbooks Database Services and the DNS Server and corrected as advised
I've checked the version of the Database Server Manager and we are running 188.8.131.5284 (DB24)
Do we need an upgrade of this for it to work ?
It would seem on our previous install for 2014, the software is also on the server even though QB is never opened on the server, we have always just accessed the company file through our workstations so should this be taken off ?
The issue appears to be due to you using the 2014 version of the database server manager (DB24), you will need to run the 2019 server manager and scan for files using this instead. The 2019 server manager would show up as DB29 in the services list.
If you do not have it installed you can use the installer for QuickBooks 2019 and select custom install to select just the server manager to be installed.
I'm inquiring as to whether you were able to rectify the multi-user mode issue. We are having the same problem. The office usually has two users, sometimes three users. Our upgrade was from QB Premier 2016 to QB Premier 2019. The IT person tried the fixes, but without any luck.
Thanks for joining this conversation, @Daffodil.
Just to verify, did you already tried the steps provided by my colleagues above? If so and you're still getting the same results, I highly suggest getting in touch with our Phone Support team. They have tools such as screen-sharing (remote access) that can check your QuickBooks and perform other troubleshooting steps to help fix this.
Please refer to this article for the detailed steps on how to reach them: Contact the QuickBooks Desktop Customer Support Team.
Just in case, I'm also including these articles for additional resources:
Keep me posted on how the call goes by leaving a comment. I want to make sure this is taken care of for you.
Hi there, in the end we have deployed the Quickbooks Company File onto a user's machine and shared the file so that others can access it. We ensure this file is regularly backed up and that the machine is always on for when the users need it.
We had problems with the .net part of QB 2019 and our server wasn't playing ball so as we only have 2 users that need QB this seemed the best workaround.
Once the files were moved to the user's machine we were able to switch to multi-user and all has been well since.
I did this with help from QB support over the phone
Hope that helps
I am having issues of this kind on an existing installation running QB 2016 Premier Accountant version. The system was fine up to a few days ago, having been running for almost 2+ years now on this. Since a few days ago I'm getting Error H202 when users try to switch companies to multi-user mode. These companies were working fine in multi-user mode up to a few days ago.
The strange thing is that if I open the same company from the "server" first, switch it to multi-user mode and then go to a client PC, they can access the company in multi-user mode fine. But if the company is first opened on a client PC, the users cannot switch it to multi-user mode, but gets the H202 error.
The QB service account is local admin on the server.
The users have full access to the folder where the company files is.
I ran QB Database Server manager which is not finding anything wrong.
I temporarily disabled the firewall, same result.
I ran the QB Tool Hub + Database Server manager, no issues found, same problem.
QB Services are running in automatic mode.
I went through every step in great details of this link, again nothing resolved it:
Server is running Windows Server 2012 R2, clients all Windows 10 and QB is updated to the latest version everywhere.
The strange thing is that companies open in mutli-user mode if they are opened like that on the server first. In my mind, this shows that the server is ok, or almost. I need some guidance as for sure it was working properly a few days ago and I need to see if there is a fix.
Some screenshots attached:
Page 1 - the error if the client tries to set to multi-user first
Page 2 - if multi-user is set on server first, it works
Page 3 - if the company is opened in multi-user mode on the server, the client connects fine in multi-user mode
Hi sborgmt ,
Welcome to the community!
I'm sorry to hear that you are receiving an error H202 when trying to access multi user mode in QuickBooks desktop 2016.
I can see from your response that A) This is only occurring when the company file is opened from a workstation P.C, and B )That you have followed the article on the troubleshooting steps for this thoroughly.
The only thing which I can think of currently which may be worth checking if you haven't already, is when you're in services.msc can you check whether the DNS.server is set in it's properties to 'Delayed start' which is recommended.
If at all possible it may also be worth trying to change the mapping of the local files on the server to a different drive to be shared with the workstation P.C's and see if you have any more luck this way.
If neither of the above work, then I would suggest contacting our dedicated desktop support team on 0808 168 9535.
Hi, I found the issue to be the mapped share in DFS. If the data is opened from a mapped share in DFS the company does not switch to multi-user while if the company is opened through UNC directly \\server\share the companies switch to multi-user correctly.
The thing is that the user rarely needed a multi-user connection, and the introduction of DFS went unnoticed and the first time they needed a multi-user company it failed. Since time had passed I failed to make the connection with DFS... so the setup was fine, it's DFS that does not work well with QB.
Problem solved, so I'm letting you know in case someone else runs into the same issue with data on DFS.
Glad you are back on track.Thanks for letting us know how the problem was solved that is very useful for us and also we hope it helps any other Community users with the same issue