Quick answer

QuickBooks multi-user mode not working usually means the host is not sharing the company file correctly, the connection path is blocked, or the file sits where QuickBooks cannot lock it. Work in one order: confirm the server and hosting, rescan with Database Server Manager, check services, fix firewall and name resolution, then repair folder permissions. The H505 and H202 guides cover those codes.

What "multi-user mode not working" actually means

QuickBooks Desktop needs three things working together before it shares a company file:

  • Windows file permissions — every person who opens the file needs permission to read, open, and modify it.
  • Database server mode — the database server on the host computer must be able to open and serve the file.
  • A QuickBooks user login — each person needs a user name and password inside the company file.

When one requirement fails, the symptom changes. Sometimes File → Switch to Multi-user Mode fails outright. Sometimes the file opens in single-user mode and blocks everyone else. Sometimes users connect in the morning and drop out in the afternoon. The codes H505 and H202 explain which requirement broke; this page covers the general failure. QuickBooks Online has no multi-user mode, and Desktop for Mac uses the QuickBooks Server app, so both sit outside this guide.

Symptoms and what each one points at

  • Switching to multi-user mode fails on one workstation while others work. Look at that machine first: firewall rule, stale mapped drive, or name resolution. See the H202 connection guide when the code appears.
  • The file opens in single-user mode and locks everyone out. One person opened it without multi-user mode. QuickBooks cannot share a file that is already open in single-user mode.
  • Hosting toggles will not stick. The server shows Host Multi-User Access again after you select it, which points at the service account, folder permissions, or a second host.
  • Some workstations cannot see the server in the Open a Company window — name resolution or Network Discovery. If every workstation loses the host at once, the problem is on the server.
  • Connections drop after a reboot or overnight: services are not starting automatically, hosting was reset, or the server went to sleep.
  • Users disconnect randomly during the day: Wi-Fi power saving, a sync client locking the file, or a share that briefly drops.

Common causes, ranked by how often we see them

  1. Hosting set on the wrong computer. The classic H505 pattern: a workstation hosts instead of the server, or the server is not hosting. Only the computer that stores the file should host.
  2. QuickBooks services stopped. QuickBooksDBXX and QBCFMonitorService must run on the server even when QuickBooks is closed.
  3. Firewall rules missing or reset. QuickBooks Desktop 2019 and later need port 8019 plus a dynamic database port, and updates can remove the rules silently.
  4. A stale .ND network file. It stores the server name, IP address, and port, so any change makes it wrong; a fresh Database Server Manager scan rebuilds it.
  5. Name resolution broken. The workstation cannot turn the server name into an IP address after a router, DNS, or DHCP change.
  6. Folder or share permissions changed. QBDataServiceUserXX or network users lost Full control over the company-file folder.
  7. The file is on the wrong storage. Database Server Manager does not support NAS devices, and OneDrive, Dropbox, and Google Drive lock files intermittently.

Back up first. Copy the whole company-file folder — the .QBW and its support files — to another drive before changing services, permissions, or network files. Verify and Rebuild Data are data-affecting operations, so run them only on a copy.

Before you begin

  • Identify the server: the one computer that physically stores the company file. Most fixes below happen there.
  • Sign in with local administrator rights, and have the QuickBooks admin password ready for File Doctor.
  • Press F2 on each computer to confirm the exact QuickBooks version. The service uses your version plus 10 — 2022 uses QuickBooksDB32, 2023 uses QuickBooksDB33, 2024 uses QuickBooksDB34 — and the name is listed in services.msc.
  • Plan 15 minutes if hosting or a service is the cause, and 30–60 minutes for firewall, name resolution, and permission work.

How to fix QuickBooks multi-user mode

1

Open the file on the server first, in multi-user mode

On the server, select File → Open or Restore Company → Open a company file, choose the .QBW file, and select the Open file in multi-user mode box before you open it. If another computer holds the file open in single-user mode, QuickBooks tells you it is in use; close QuickBooks on that computer first. A file already open in single-user mode cannot be shared, whatever the hosting setting.

2

Confirm hosting on the server and turn it off everywhere else

On the server, open QuickBooks without a company file and go to File → Utilities. If Host Multi-User Access appears, select it. If Stop Hosting Multi-User Access appears, hosting is already on — leave it. On every workstation, do the opposite: select Stop Hosting Multi-User Access if it appears. This check alone resolves most failures that begin after a new install, and it is the fix behind most error H505 reports. The hosting mode guide covers the three modes.

3

Scan the company-file folder with Database Server Manager

On the server, open the current QuickBooks Tool Hub, select Network Issues, then QuickBooks Database Server Manager. If your folder is listed, select Start Scan; if not, select Browse, point the tool at the folder, then scan. The scan rebuilds the .ND file, re-registers the folder for sharing, and repairs firewall permissions automatically. It takes one to three minutes on a normal folder, and you should repeat it after the file or folder moves. The Database Server Manager guide explains the install options.

4

Check and restart the QuickBooks services

Press Windows + R, type services.msc, and press Enter. Double-click QuickBooksDBXX. Set Startup type to Automatic, confirm the service is Running, then open the Recovery tab and set Restart the Service for first, second, and subsequent failures. Select Apply and OK, then repeat for QBCFMonitorService. If hosting will not stay on, check the Log On tab of QuickBooksDBXX: a service account with an expired password fails silently.

5

Fix the firewall rules and the ports

Open Database Server Manager and select the Port Monitor tab to see the port your version uses: QuickBooks Desktop 2019 and later use port 8019 plus a dynamic database port assigned at installation. In Windows Defender Firewall → Advanced Settings, confirm inbound and outbound TCP rules allow those ports on the server and each workstation. Third-party suites keep their own rules even when Windows Firewall is off, so add the same exceptions there. Never leave a firewall disabled after testing. The firewall and ports guide covers the exact rules.

6

Test name resolution from every workstation

On the server, run ipconfig /all and note the Host Name. On a failing workstation, ping the server by name and by IP — for example, ping QB-SERVER then ping 192.168.1.20. Both should reply. If the IP replies but the name does not, the workstation cannot resolve the server name, which is a DNS or router task for an IT professional. If neither replies, check the physical network first. Map the file with its UNC path (\\Server\Share\CompanyFile.qbw), not a drive letter. If workstations still cannot see the host, follow the server connection guide.

7

Restore folder and share permissions

On the server, right-click the folder holding the company file and open Properties → Security → Edit. Give QBDataServiceUserXX — for example QBDataServiceUser33 for the 2023 version — Full control. Confirm the exact account name on the Log On tab of the service if it differs. On the Sharing tab, share the folder and give the same account Full control over the network. Both layers matter: a folder can be shared with full rights while NTFS permissions still deny the service account.

8

Move the file to supported storage and stop the host from sleeping

Check where the .QBW file actually lives. Database Server Manager does not support NAS devices, and consumer sync folders lock files intermittently. Move the file to a local drive or a properly shared server folder, then rescan. Keep the server awake and wired, and make sure every computer runs the same QuickBooks Desktop year as the server; a different year cannot open the file.

Verify multi-user mode is really fixed

  1. Open the company file on the server and confirm File → Switch to Multi-user Mode is available; if the menu shows Switch to Single-user Mode, you are already in multi-user mode.
  2. Open the file from two workstations at once and press F2 on each to confirm the file and version.
  3. Post a test invoice from one workstation, refresh the report on another, then delete the test entry.
  4. Restart the server and repeat the test, confirming both services start on their own.
  5. Leave one workstation connected for 15 minutes to confirm the session survives idle time.

If multi-user mode still fails

Work through failures in order of evidence. If every workstation fails including the server, suspect the server: hosting, services, the .ND file, and permissions. If one workstation fails, suspect that machine: its firewall, name resolution, or a stale mapped drive.

Run the network check in QuickBooks File Doctor when the direction is unclear. In Tool Hub, open Company File Issues → Run QuickBooks File Doctor, select the company file, choose Check your Network, and enter the admin password. The results name the failing layer: hosting off, folder not writable, no network connectivity, or a service not running.

Escalate to Intuit support or a network technician when pings show packet loss, when services refuse to start, or when the server name resolves to the wrong address. Do not reinstall QuickBooks to fix a network fault; reinstall rarely changes a firewall rule or DNS record.

Prevention

  • Document the server, keep hosting on that computer only, and check hosting after every new workstation install.
  • Set QuickBooksDBXX and QBCFMonitorService to Automatic with restart-on-failure recovery.
  • Rescan the company-file folder after any move, rename, or network change.
  • Give the server a reserved IP address, keep it wired, and disable sleep.
  • Keep every workstation on the same QuickBooks Desktop version family, and test multi-user mode from two machines after updates.

Frequently asked questions

Why can only one person open the company file?

Someone opened it in single-user mode, or hosting is off on the server. Close QuickBooks everywhere, reopen the file on the server with Open file in multi-user mode selected, and confirm only the server shows Stop Hosting Multi-User Access.

Why can some workstations see the server and others not?

That points at the failing machines, not the server. Ping the server by name and by IP from each one. If the IP replies but the name fails, it is a name resolution problem on that workstation or in DNS. If both fail, check its firewall profile and network connection.

Can I use a NAS or cloud folder for the company file?

No for NAS — Database Server Manager does not support Network Attached Storage. No for consumer sync folders either, because they lock files while uploading. Use a local drive on the server or a properly shared Windows folder, and rescan after moving the file.

Why does multi-user mode stop working after a server reboot?

The QuickBooks services are probably set to Manual, or hosting was reset. Set both services to Automatic with restart-on-failure, confirm hosting is on, and retest.

Sources & further reading