QuickBooks Error -6175, 0 -- Database Server Cannot Start Hosting

Last reviewed 2026-07-10 5 min read

QuickBooks error -6175, 0 blocks multi-user access because the database server manager cannot reach the company file; our engineers walk through every trigger and resolution.

QuickBooks Error -6175, 0 occurs when QuickBooks Database Server Manager cannot start its hosting service or cannot obtain exclusive access to the company file in multi-user mode. The error prevents anyone on the network from opening the file until the underlying conflict is cleared. Our engineers have resolved this error across thousands of QuickBooks Desktop environments, and the fix is almost always one of a small number of identifiable causes.

What the Error Message Says

The full message displayed by QuickBooks is:

"QuickBooks is attempting to start this application. Please wait while we initialize the QuickBooks environment. (-6175, 0)"

In some configurations the message reads:

"QuickBooks cannot access the company file. The database server could not be started. (-6175, 0)"

What the Code Means

The -6175, 0 code is returned by the QuickBooks database engine when the server-side component responsible for hosting the company file fails to initialize or is blocked from opening the file in a controlled manner. QuickBooks Desktop relies on a Sybase-based database engine that must lock the company file briefly during startup. If another process already holds a handle on that file, or if the database service lacks the permissions or resources to start, the engine returns -6175, 0 and aborts the connection attempt.

What Triggers It

The most common triggers, in order of frequency our engineers see in the field, are:

Another process is locking the company file. A backup utility, antivirus real-time scanner, cloud-sync agent (such as OneDrive, Dropbox, or Google Drive), or even a second instance of QuickBooks on the same machine has the file open or is scanning it at the moment QuickBooks tries to start hosting.
QuickBooks Database Server Manager service is stopped or damaged. The Windows service that hosts the file may have crashed, been set to Manual startup, or lost its configuration after a Windows update.
Hosting mode is enabled on a workstation instead of the server. In a proper multi-user setup, only the machine storing the company file should have hosting turned on. When a workstation accidentally has hosting enabled, it competes with the server and produces -6175, 0.
Windows firewall or third-party security software is blocking database communication on the ports QuickBooks uses for multi-user access.
The company file is damaged at the database level, preventing the engine from opening it cleanly.

How to Fix It

Scenario 1: Another Process Is Locking the File (Most Common)

Sign in to the server or the machine hosting the company file. Close QuickBooks on every workstation and on the server itself.
Open Task Manager and end any running QuickBooks processes: look for QBW32.exe, QbwServerUtilityMgr.exe, QBDBMgrN.exe, and QBUpdate.exe.
Temporarily disable any real-time antivirus scanning on the folder that contains the company file. If a cloud-sync application monitors that folder, pause syncing or exclude the folder.
Disable any scheduled backup jobs that target the company file folder, then wait two minutes for any file handles to release.
Reopen QuickBooks on the server, switch to multi-user mode, and confirm that the file opens. Then test from a workstation.

Scenario 2: Database Server Manager Service Is Stopped or Misconfigured

On the server, open the Windows Services console (press Windows + R, type services.msc, and press Enter).
Locate QuickBooksDBXX (where XX corresponds to your QuickBooks version number, for example QuickBooksDB33 for QuickBooks 2023).
Check the Status column. If the service is not listed as Running, right-click it and select Start.
Right-click the service again, select Properties, and set Startup type to Automatic.
On the same Properties dialog, verify that the service is logging on as Local System account. If it is configured for a specific user and that user's password changed, reset it here.
Open QuickBooks Database Server Manager from the Start menu, go to the Folder tab, and rescan the folder holding the company file. Wait for the scan to report that the file is configured for multi-user access.

Scenario 3: Hosting Mode Is Enabled on the Wrong Machine

On each workstation, open QuickBooks, go to File, then Utilities.
If you see Stop Hosting Multi-User Access listed, hosting is currently on for that workstation. Click it to disable hosting.
On the server machine that physically stores the company file, confirm that Host Multi-User Access appears under the same menu (meaning hosting is already enabled). If it does not, enable it.
Restart the server, then reopen the company file in multi-user mode.

Scenario 4: Firewall or Security Software Blocking Communication

On the server, open Windows Defender Firewall (or the equivalent third-party firewall console).
Verify that inbound rules exist for the QuickBooks executables and for the ports used by your version: 8019 (dynamic port assignment) plus the version-specific database port assigned during installation.
If rules are missing, add them or use the QuickBooks File Doctor tool to reconfigure firewall ports automatically.
Restart the Database Server Manager service after applying firewall changes.

Scenario 5: Company File Damage

If none of the preceding steps clear the error, the file itself may be damaged at the database level. Run QuickBooks File Doctor from the QuickBooks Tool Hub. If File Doctor reports that it cannot repair the file, the file requires professional-level data recovery to rebuild the database structure.

How to Prevent It Recurring

Store company files on the server, never in a cloud-synced folder or a location monitored by real-time backup agents.
Configure antivirus exclusions for the company file directory and for the QuickBooks installation folder.
Ensure only the server has hosting mode enabled; verify this after every QuickBooks update, since updates occasionally reset the setting.
Set the QuickBooks Database Server Manager service to start automatically and document the correct service account credentials.
Apply QuickBooks maintenance releases promptly on the server first, then on workstations, so all machines remain on matching releases.