Very sorry i have been slammed at work. 

Yes, i just spun up a Hyper-V Windows 10 VM on static IP with a shared folder for just 2022 files. Then mapped it to their workstations and installed QB Database Server 2022 on the Windows 10 VM and let it run it on the host. It runs it just like a server and have not had issues yet. Only thing is to try and limit the upgrade to 2022 until all of their clients or books can move over. Once they can, you can move all the files back to their main server, remove all old QB Database installs and install 2022 or 2023 by that time. 

Thank you for the reply. 

So the issue still exists in scenarios where previous years of DBMgr (2019/20/21) is installed alongside QB22 DBMgr it sounds like.  We are able to replicate the same issue.

@RCV 

This is simply not accurate.  Why would you say it's fixed when it isn't fixed? 

Having QB22 DBMgr installed alongside previous years of QB DBMgr does not work at this moment.

I have not tried any update or the solution they say here yet but just reading through it sounds like a basic script they have to reply with that does not pertain to this situation. I gave up with their support so the VM solution was the best for us and our client at the moment. Hope they can get this fixed soon! 

Thanks Bobby, that's what I figured had to happen since their data base managers is no longer capable of connecting to data location across a network now.... not sure why...

So I have a Terminal server that when I installed 2022 on I chose the way I normally do where it usually doesn't install the DBM but the DARN thing actually installed the 2022 DBM and the Monitor services on that machine so with your info all I have to do is house those 2022 files locally on the Terminal server and start all the services back up.

Thanks for the actual help Bobby.

Step 1: Use QuickBooks Database Server Manager
As the first step, start by opening QuickBooks Database Server Manager on the server computer
Go to the Start menu and type ‘Database.’
If no folder location is found, use the Browse option to go to the folder that stores the company file(s).
Now, press the OK button. Follow it by clicking the Scan button.
If the above-given steps are followed word to word, the firewall permissions will get repaired.

Now, the user needs to check whether the multi-user mode not working problem has resolved or not. If not, users should follow the next step.

Step 2: Check Host Mode on each of the User Computers
Now, open the QuickBooks File menu on the user computer, followed by opening utilities.
Note that if Host Multi-User Access appears on the list, the user needs to move to the next computer. This simply denotes that the particular computer is not the system hosting the company file.
If Stop Hosting Multi-User Access appears on the list, one has to disable hosting, followed by enabling QuickBooks single user mode.
Once it is ensured that hosting mode is off on all the user computers, one should scan for the QuickBooks multi user mode not working error.

Step 3: Check whether QuickBooks services are running
Make sure that Quickbooks DBXX (here XX is representing the year of QuickBooks) and QBCF Monitor Service is in running state on the server computer. To use the multi-user mode of QuickBooks services, follow the below pointers.

1. Initiate the first step by typing ‘services.msc’ in the windows search bar. Move ahead and press the Enter key.
2. Look out for QuickBooks DBXX service to appear in the Services window. If this does not appear, then follow these given steps –

Make sure that the database server manager is installed on the server properly
Look out for the corresponding, up-to-date Database Server Manager. As every year after the installation of QuickBooks Desktop on the user’s computer, the Manager also gets an upgrade.
In case, the entire program is running on the computer, one needs to ensure that hosting is enabled on the server.
3. The next step should involve double-clicking the QuickBooks DBXX service. Once the service gets started, it should show either Running or Start option.
4. In the following step, select ‘Restart the QuickBooksDBXX Service’ for the first, second and subsequent failures under the Recovery tab.
5. Simply repeat the points 1,2,3, and 4 as mentioned above for the QBCF Monitor Service.

Having followed all the aforesaid steps, the user requires to open QuickBooks in multi-user mode on each of the work computers. This is to check if the ‘QuickBooks multi user mode not working’ issue has been resolved or not.

If the problem persists and the error message appears, the user needs to check the membership of QuickBooks DBXX service. The membership service should have all the required permissions and it should be a part of the administrator group.

So....

Great step by step for trouble shooting Data base managers.... but a little useless as it pertains to mixing 32bit and 64 bit data base managers on the same host or server.  (Read the other 2 pages for reference of the issue)

Since you obviously host VM's for a desktop experience and the use of QB versions, have you found some other way to mix a 32 bit data base manager and the 64 bit data base manager and maintain functionality of multi user mode for versions 2022 through 2020 all installed on the same host with out loosing multi user functionality for the 2021  through 2020 or even older versions once 2022 is properly installed and the 2022 data base manager is functioning normally?

We have all found that 2022 breaks Multi user functionality for versions 2021 and older once the 2022 data base manager is installed but 2022 multi user mode functions fine.

What are your findings?

I have the same issue and I installed the R4 version of Quickbooks 2022

It seems Quickbooks 2022 is 64 bit and installs to C:\Program Files folder where all previous versions are 32 bit and install to the C:\Program Files (x86) folder.

-- So if you are having issues with Multi-User Mode for Quickbooks Desktop 2022 and get the H202 error you have to use the 64bit "QuickBooks Database Server Manager" to run a scan to fix Windows firewall issues:

"C:\Program Files\CommonFiles\Intuit\QuickBooks\QBServerUtilityMgr.exe"

-- With earlier versions of Quickbooks that are installed on the same server you use the 32bit  "QuickBooks Database Server Manager":

"C\Program Files (x86)\Common Files\Intuit\QuickBooks\QBServerUtilityMgr.exe"

*** To know you have the proper version of QBServerUtilityMgr.exe running for Quickbooks 2022 go to the "Port Monitor" tab and you will see all your versions of Quickbooks that you have installed as well as the ports they are using.  If Quickbooks Database Manager 2022 is not listed there then you are using the older 32 bit version for all previous versions of Quickbooks from 2021 down.

I hope this works for you,

Ben Perry

It seems Quickbooks 2022 is 64 bit and installs to C:\Program Files folder where all previous versions are 32 bit and install to the C:\Program Files (x86) folder.

-- So if you are having issues with Multi-User Mode for Quickbooks Desktop 2022 and get the H202 error you have to use the 64bit "QuickBooks Database Server Manager" to run a scan to fix Windows firewall issues:

"C:\Program Files\CommonFiles\Intuit\QuickBooks\QBServerUtilityMgr.exe"

-- With earlier versions of Quickbooks that are installed on the same server you use the 32bit  "QuickBooks Database Server Manager":

"C\Program Files (x86)\Common Files\Intuit\QuickBooks\QBServerUtilityMgr.exe"

*** To know you have the proper version of QBServerUtilityMgr.exe running for Quickbooks 2022 go to the "Port Monitor" tab and you will see all your versions of Quickbooks that you have installed as well as the ports they are using.  If Quickbooks Database Manager 2022 is not listed there then you are using the older 32 bit version for all previous versions of Quickbooks from 2021 down.

I hope this helps,

Ben Perry

SysAdmin

I had it do 2020 and 2022 both programs.  Can't work with Abort every two minutes.  Have worked with QUICK BOOKS for 40 years.  Never had these problems EVER!  Need an update that works for free or I'm heading somewhere else.  Carol   [email address removed]

Hi there, @cpw111. Let's work this so you can access QuickBooks Desktop (QBDT) without having the program exit automatically.

You'll want to run QuickBooks Install Diagnostic Tool (QBInstall Tool). This feature will help you identify possible component issues related to the program. To begin, here's how:

1. Open the QuickBooks Tool Hub, then select Installation Issues.
2. Select QuickBooks Install Diagnostic Tool. Let the tool run. It can take up to 20 minutes.
3. When the tool finishes, restart your computer and start QuickBooks Desktop, then open your data file.
4. Update your QuickBooks to the latest release. This makes sure you have the most recent fixes and security update.

If the issues persist, I'd recommend using the QuickBooks Tools Hub. It automatically searches and fixes existing problems with the program you've installed. Please see this article for more information: Fix issues when QuickBooks has stopped working.

In addition, here's an article that contains other available troubleshooting steps to help you resolve issues in QBDT: Repair your QuickBooks Desktop for Windows.

Know that I'm with you on getting this resolved, @cpw111. Please let me know how it goes. I'll be more than happy to assist you again if you have any additional QuickBooks-related concerns. Take care!

Any update on this?

Hello, @jk8.

Can you tell me more about the information that you're trying to get an update on? That will surely help us provide an accurate solution to the concern that you're having.

You can click the Reply button below to add more details.

I'm looking forward to hearing from you soon! Take care and have a wonderful day!

QB Team,

I think we are just looking for a simple answer to the question many of us had/have. Maybe it got fixed... who really knows -- but I have surely not seen a seen a concise answer. It is exhausting, honestly.

The issue:

If you have a computer running QB DB Manager versions 19/20/21 -- to host multi-user access... a pretty common setup). When you install QB 2022 (and the related QB DB Manager) IN ADDITION TO 19/20/21... it breaks the ability to host multi-user access on the earlier versions.

If you read through the thread, I think you will better understand the issue. 

I would imagine that Intuit has a lab where this has been tested.

Again, we just gave up on it. I don't know if it is still an issue for others.

no, definitely not fixed yet.  still happening with 2022 & 2023 installed alongside any of the 32-bit versions.

Additionally, Dec of 2021, on this thread, it was said by an Intuit employee that there was ongoing work for this issue. The investigation was referenced as INV-63789.  

Any update on how that turned out?

Welcome back, @jk8.

The investigation of the multi-user errors was already resolved and tagged as closed last March 2022. Let me share the resolution given to resolve the issue.

This issue was resolved by updating your QuickBooks Desktop to R3 or higher release. If it doesn't work, you'll need to reinstall QuickBooks by running the installer as Admin. 

You may also need to open the Database Server Manager through the start menu and run as an admin by not opening through the QuickBooks Tool Hub.

If you get the same result, I recommend contacting our QuickBooks Support Team. This way, they can further check on this issue and provide in-depth troubleshooting steps to get this resolved. They can also reopen the investigation if other users are experiencing the same.

Come back to this post and let me know how it goes, @jk8. I want to make sure you're taken care of.

Hello Mark --

I guess I will need to believe you --- when I have several hours free (ha!) I will need to see if I can create a new environment where this actually works the way Intuit says it should/does.

I did just take look at the Desktop/Enterprise 2022 release notes, and I saw no mention of this:

https://quickbooks.intuit.com/learn-support/en-us/help-article/update-products/release-notes-quickbo... -- and I am pretty sure when I was working on this issue, I was installing R3 or greater (being that was released in Nov 21).

P.S. I did call QB Support on more than one occasion, and unfortunately, I was pretty disappointed by the support I received, and that is when I turned the QB Community for additional help.

TO ALL FUTURE READERS OF THIS THREAD

The issue is related to mixing 64bit and 32 files and programs on the same server or workstation environment.

Several of us that have responded are IT guys who figured out they were trying to control 32bit files with their new 64bit data base manager.

QUICKBOOKS / Intuit have made ONE post in this thread that confirms this.

The rest of the responses you get are going to be from Help desk people who read from a script based off of Higher-level techs or QB /Intuit Policy.

The fix for this is rather simple and will only be needed for 1 more year as of Jan 2023. You need two server or workstation environments. One to house all 32bits software and files, and the other for 64bit software and files. You can do this with a server physical or Virtual, a desktop physical or virtual. Just make sure its on the same network as the system housing the 2021 and previous installations.

You MUST Uninstall any 2022 or 2023 versions off the system running the 2021 or older QuickBooks. Disable any data base manger services for 2022 and 2023. Usually, the uninstall stops them but doesn’t disable them.

On a separate system, install QuickBooks 2022 and or 2023 along with the Data base manager. You will need to tell the data base manager to scan the folder just like on the 32bit systems in the past.

Next move any 2022 or 2023 files to the server or workstation environment that contains the 2022 and or 2023 software and Data base Manager. We have a dedicated folder our QuickBooks files on both systems. I then share them to everyone on the network. Next, I map the shared folder as mapped drives to the staffs PC’s. This way they can get to the file locations easy.

This follows all the rules QB set up for the Data base managers, the files are housed on the server or PC with the data base manager, and it is the only instance of data base manager on the network. YES, the 32bit and 64bit CAN NOT see each other even though they are on the same network, and it just works.

I currently have this arrangement along with several others in this thread and it functions for Multiuser mode for 32 bit and 64bit files at the same time.

It would be nice if Intuit QuickBooks would bother to test it and make Tech bulletin on it but they can’t be bothered while they are busy racking in all that dough we throw at um. This arrangement does work for now but next May, versions of  2021 go extinct so this will no longer be required as all modern versions will be 64bit and there will no longer be 32 bit versions installed.

Appreciate that, Kershinator

2 server setup is ridiculous, but I do understand why you went that route.

Ultimately we found that if QBFC install is 32-bit it needs to be removed.  Replaced with 64-bit by doing a program repair (22 or 23).

Then ran ToolHub options under Program Problems tab.  Then rebooted.

Successfully hosting 32 & 64-bit DbMgr's now and able to swap to multi-user mode without issues in both.

Thank you for posting and I am glad it is working for you! Your post is very hopeful. However, I am still struggling to get both 32 and 64-bit DbMgr on the same server. Has anyone else get this to work? How is it running thus far? any issues?

1. How do you remove QBFC? This is the QBFCMonitorService correct? do you remove it via registry or just do a 22 or 23 repair?

2. Which option did you run in ToolHub quick fix or diag tools? Both do not seem to work however.

Any additional insights are much appreciated!

Thank you!

Thanks for sharing more details about the error you encountered, @ryannguyen. I can point you in the right direction to resolve this issue in QuickBooks Desktop.

Let us call our support team to resolve the error encountered in your company. 

Follow the steps below:

1. On your QuickBooks account, go to the Help section.
2. Choose Contact Us.
3. State your concern, then select Continue.
4. Enter your code and select Continue.
5. Select to chat with us or Have us call you.

Alternatively, you might want to create a backup of your financial files; we can utilize this article for the steps by step process: Back up your QuickBooks Desktop company file.

Alternatively, please refer to this helpful page about the operating system, hardware, software, and other requirements to run QuickBooks Desktop:

• System requirements for QuickBooks Desktop 2022.
• System requirements for QuickBooks Desktop 2023.

Please let me know how it goes after calling our phone representatives. We are happy to assist you again. Have a pleasant day.

Thank you, ChristineJoieR! Please provide the solution here if any. I am sure many of us would like to know as well. It is very much  an inconvenience to have to spin up 2 QB hosting servers, each for 32bit and 64bit DbMgr. Not accounting the cost of server maintenance, backup, DR replication .... etc. 

Sorry for the delay in responding on this.  Answers to your previous questions below.

•  How do you remove QBFC? This is the QBFCMonitorService correct? do you remove it via registry or just do a 22 or 23 repair?  sc delete command (sc delete QBCFMonitorService).  With 64bit and 32bit installed side by side, QBFC can run as either architecture.  if you happen to go look at the path to executable on the service itself, it will be pointing to Program Files (x86) on machines not working with 32bit and 64bit installed side by side.  Once the service is gone, you can run the program repair (in add/remove programs) with 64bit version of QB.  That will reinstall the QBFC service but will now be utilizing the 64bit version of the service.  Can verify by looking at the same Path to executable property on the service after the changes.

•  Which option did you run in ToolHub quick fix or diag tools? Both do not seem to work however.
  Won't hurt to run both, but the 'Quickbooks Program Diagnostic Tool' should suffice.
  
  Hope this helps you get it resolved!