QuickBooks Desktop 2017 Multi-User Mode After Sunset

Keep QuickBooks Desktop 2017 running in multi-user mode without Intuit support. Set up Database Server Manager, fix firewall blocks, and resolve H-series e

If your office relies on QuickBooks Desktop 2017, you already know that Intuit officially sunset this version on May 31, 2020. While direct add-on services and live support have ended, the core desktop engine is built to last. With the right local configuration, you can continue running 2017 in multi-user mode across your team for years to come—entirely independent of Intuit's servers.

Here is how to establish and maintain a stable, local multi-user environment for QuickBooks Desktop 2017.

The Same-Version Rule

Before touching network settings, ensure every computer in your office is running the exact same release of QuickBooks Desktop 2017. Even a minor difference in patch levels (for example, one machine on R14 and another on R15) will prevent the company file from opening correctly in multi-user mode.

Because Intuit no longer hosts automatic updates for 2017, you must manually apply the final release patch to every workstation and the server. Check the current version under Help > Update QuickBooks, and ensure all machines match before proceeding.

Hosting Configuration

Multi-user mode requires exactly one computer to act as the host for the company file. This is usually your dedicated server, but it can be a primary workstation.

1. On your designated server, open QuickBooks Desktop 2017.
2. Navigate to File > Utilities.
3. If you see Stop Hosting Multi-User Access, do not click it—this means hosting is already turned on.
4. If you see Host Multi-User Access, select it to turn hosting on.
5. Ensure that every other workstation in the office has hosting turned off. Only the server should host the file.

Database Server Manager (QBDSM)

The QuickBooks Database Server Manager is the background service that manages traffic to your .qbw file. This step is identical across most QuickBooks versions, but it is critical for keeping 2017 stable.

1. On your server, open the Windows Start menu and find the QuickBooks Database Server Manager.
2. Go to the Folders tab and click Add Folder.
3. Browse to the exact folder where your 2017 company file is stored.
4. Click Scan.
5. Let the scan finish completely. It should confirm that your company file has access configured for multi-user mode. Run this scan any time you move the company file or create a new one.

Firewall Port Exceptions

If users can access the file locally but get stuck on the "Searching for network" screen, your firewall is likely blocking QuickBooks 2017. You must configure inbound and outbound rules to allow QuickBooks through.

For QuickBooks Desktop 2017, the specific TCP ports you need to open are 8019 (used for general database communication) and 56719 (the specific port assigned to the 2017 version's database service).

Create exceptions in your Windows Defender Firewall (or third-party security software) for these ports, and ensure the QBW32.exe and QDBMgr.exe programs are allowed through. If you manage to lock yourself out completely, temporarily turning the firewall off can confirm if it is the culprit.

Resolving H-Series Errors

When multi-user communication breaks down, QuickBooks 2017 typically throws an H-series error (such as H202, H505, or H303). These errors mean a workstation is trying to access the file but cannot communicate with the server's database service.

• H202: Indicates the workstation sees the server but cannot access the file. Verify that QBDSM is running on the server and that the server is in Hosting Mode.
• H505: Usually a firewall block or an incorrect network setup. Double-check your TCP port exceptions (8019 and 56719).
• H303: Suggests a configuration issue requiring you to move the company file to a local drive rather than a mapped network drive. QuickBooks operates best when the server stores the file directly on its internal C:\ drive, and workstations access it via a mapped network path.

Long-Term File Protection

Because you are intentionally running a sunsetted version offline, your company file is entirely in your hands. If the .qbw file ever throws a -6000 series error or refuses to open due to data corruption, do not attempt a forced upgrade. If the built-in Verify and Rebuild utilities fail to resolve the structural damage, our team at quickbooksfilerepair.com can manually repair the underlying database structure so you can keep your 2017 installation running smoothly.