Keeping QuickBooks Desktop Multi-User Mode Alive After a Server 2022 Upgrade
Moving to Server 2022 breaks QuickBooks multi-user access unless you reinstall the database manager, rebuild firewall rules, and reset folder permissions correctly.
Upgrading the host server from Windows Server 2016 or 2019 to Server 2022 is one of the most common reasons multi-user mode stops working in a long-term QuickBooks Desktop deployment. The OS upgrade itself does not damage your company file, but it reliably destroys three things QuickBooks depends on: the QuickBooksDB service registration, the inbound firewall rules that let workstations see the server, and the Windows folder permissions that let users open the file across the network. The good news is that all three are rebuildable without Intuit support, and once the procedure is done correctly, QuickBooks Desktop runs on Server 2022 the same way it ran on the previous OS.
What breaks during the OS upgrade
When Server 2022 installs—whether as an in-place upgrade or a clean install on new hardware—the QuickBooks Database Server Manager service typically disappears or fails to start. The old firewall exceptions do not carry over because Server 2022 resets its Windows Defender Firewall profile during setup. Shared-folder NTFS permissions also revert to defaults, meaning the QBDataServiceUser accounts that QuickBooks creates no longer have the access they need. Workstations will see errors like "The company file is on another computer, and that computer needs additional setup," H202, or a generic inability to switch to multi-user mode.
Step 1: Reinstall QuickBooks Database Server Manager
Log in to the Server 2022 machine as a local Administrator. Download the QuickBooks Desktop installer matching the exact year and edition your workstations run—do not mix versions. If your workstations run QuickBooks Desktop 2021, install the 2021 database server manager.
Run the installer and select the option for a server installation, not a workstation installation. When prompted, choose "I'll be using QuickBooks on this server" only if someone actually opens QuickBooks on the server console itself; otherwise select the server-only path. After installation completes, open Database Server Manager from the Start menu and run a full scan of the folder holding your company file. The scan must finish without errors and must list your .qbw file as successfully scanned. If the scan fails, note the error—persistent database manager failures often indicate a damaged install that requires a clean uninstall and reinstall using the QuickBooks Clean Install tool.
Step 2: Rebuild the firewall rules
Server 2022's Windows Defender Firewall blocks QuickBooks by default. Database Server Manager should create the necessary rules during installation, but verify them manually.
Open Windows Defender Firewall with Advanced Security. Under Inbound Rules, confirm that rules exist for QuickBooks through the following ports: 8019 (data file access), and the dynamic port range assigned to your specific company file (visible in the Database Server Manager scan log). Each QuickBooks version also uses a version-specific port—2019 uses 56728, 2020 uses 56729, 2021 uses 56730, 2022 uses 56731, and so on. Ensure the rule applies to all three profiles: Domain, Private, and Public.
If the rules are missing, the fastest fix is to run the QuickBooks File Doctor tool from the server, which attempts to re-create them automatically. If that tool is unavailable in your environment, create the inbound rules manually for the ports listed above, allowing TCP traffic for the version-specific port and both TCP and UDP for 8019.
Step 3: Reset folder permissions
Right-click the folder containing your company file, select Properties, then the Security tab. The following accounts need Full Control at the folder level: the local Administrators group, SYSTEM, and every account starting with QBDataServiceUser. If those QBDataServiceUser accounts do not appear in the list, they were not recreated during the Database Server Manager install—uninstall and reinstall the database server component to regenerate them.
Apply the permissions to the folder and all subfolders and files. Share the folder with Share permissions set to Full Control for the same user set, or for Everyone if your network security model permits it.
Step 4: Verify from a workstation
On a workstation, open QuickBooks while holding the Ctrl key to bypass the automatic open, then open the company file using the UNC path (for example, \\ServerName\QBData\Company.qbw) rather than a mapped drive letter. Switch to multi-user mode. If it connects, the rebuild is complete. If you still see H202 or connection errors, run a ping and a Test-NetConnection to the server on port 8019 from the workstation to confirm the network path is open before investigating further.