Quickbooky

Accounting News

Multi-User & Networking

QuickBooks Database Server Manager: the scan, the hosting switch, and the restart

Multi-user setup on QuickBooks Desktop stalls until folders are scanned, hosting is enabled, and the QuickBooksDB service is restarted in the right order.

COMMUNITY ISSUESQUICKBOOKY

Multi-user QuickBooks Desktop setups tend to fail at the same three points. The program is installed on every computer, the company file sits on the server, and the workstations still cannot open it. The accepted fix comes down to three moves: a folder scan in Database Server Manager, the hosting switch under the File menu, and a restart of the QuickBooksDB service. We have laid out the full sequence below, along with the spots where setups usually go wrong.

The tool that does the sharing

QuickBooks Database Server Manager is the Windows component of QuickBooks Desktop that publishes company files to a network. It runs on the server, meaning the machine that stores the company files, not the computers staff type on. The tool never opens a file itself. It scans folders, registers every company file it finds, and lets other QuickBooks installs attach to those files over the network. Without it, a workstation can only reach a company file stored on its own drive.

Scan the folders once

Setup starts on the server. Open the Windows Start menu, search for Database, and open QuickBooks Database Server Manager. On the Scan Folders tab, select Browse, choose every folder that holds company files, and confirm with OK. Then run Start Scan. One pass is enough. When the scan finishes, everything it found appears in a results list, and other computers on the network can reach those files from that point on. Revisit the tab only when the business starts keeping company files in a new folder.

Watch the right drives

The Monitored Drives tab tells the tool which hard drives to keep under observation. Check only the drives that store company files and leave the rest alone. Watching empty or unrelated drives adds nothing except slower, noisier scans. Two other tabs are worth a look. System shows where Database Server Manager sits on the machine, and Database Server gives a live view of the service plus a list of who is connected to it at any moment.

Hosting has its own switch

Scanning alone does not turn on hosting, and this is where many setups stall. On the server, open the File menu and look under Utilities. If it offers Host Multi-User Access, select it. If it offers Stop Hosting Multi-User Access instead, hosting is already active. This check matters because a workstation cannot attach to a company file that no computer is hosting. When hosting is missing, the symptoms are familiar to anyone who reads these threads: H-series errors such as H202, appearing the moment a workstation tries to switch into multi-user mode.

Open the file once, then close it

The accepted procedure then calls for a step that looks redundant. On the server, open QuickBooks Desktop, go to File, then Open or Restore Company, and choose Open a company file. Find the file, select Next, tick Open file in multi-user mode, and open it. Sign in as usual, then return to File and choose Close Company/Log off. That round trip proves the file can be served in multi-user mode, and closing it hands the file over to the database service rather than leaving it held open by a program on the server.

Why does the restart matter?

One more step closes the loop, and it is the one most often skipped. Open Control Panel, then Administrative Tools, then Services. Find the entry named QuickBooksDBXX, right-click it, and choose Restart. The XX stands for the product year, so a 2021 install runs as QuickBooksDB31. The service is the component that actually serves company files across the network, and it reads its folder list and hosting settings only when it starts. A restart forces it to reload that configuration, which is why this single step clears so many reports of files that stay invisible from other computers.

If workstations still cannot connect

Two follow-ups cover the remaining cases. First, the firewall. When QuickBooks Desktop is installed, Windows asks whether the program may communicate on the network, and dismissing that prompt leaves the database service blocked on the server. Adding an exception for QuickBooks in Windows Firewall restores the path. The network connectivity fix in the QuickBooks File Doctor, part of the QuickBooks Tool Hub, applies those permissions automatically, which suits anyone who would rather not dig through firewall settings.

Second, the install source. Database Server Manager ships with QuickBooks Desktop, so a server that stores files but does not run QuickBooks day to day still needs it. Run the QuickBooks Desktop installer on that machine and pick the option for a computer that will host and share the company file. That installs the server component without turning the machine into a full workstation.

The sequence in full

The full fix, in order: scan the company file folders, confirm hosting under File and Utilities, open the file once in multi-user mode and close it, then restart the QuickBooksDB service. Workstations that follow that sequence reach the company file. We keep seeing the same pattern in these reports. The scan sets the stage, hosting puts the file within reach, and the restart is what makes both stick.

← Back to Community Issues