QuickBooks Error -6010, -100 -- Database Service Missing or Stopped on Host

Last reviewed 2026-07-05 5 min read

QuickBooks error -6010, -100 blocks company file access when the database service on the host is uninstalled or stopped; our engineers walk through restoring it.

Error -6010, -100 is a 6000-series company file access error that occurs when QuickBooks Desktop cannot establish a proper connection to the database server manager on the host machine. Our engineers see this most often after the QuickBooks Database Server Manager has been uninstalled, stopped, or disrupted because hosting configuration was moved between computers. The error blocks all users from opening the company file until the database service is restored and the file is re-scanned.

What the Error Message Says

When this error fires, QuickBooks Desktop displays one of the following messages (wording varies slightly by QuickBooks version):

"-6010, -100: QuickBooks was unable to access the company file."

"Error (-6010,-100): This is not a QuickBooks data file or there is a problem with the file."

In multi-user setups the message may also reference the server or host machine by name.

What the Code Means

The -6010 component signals that QuickBooks detected a configuration mismatch between the workstation requesting the file and the machine designated as the host. The -100 sub-code narrows the cause to the QuickBooks Database Server Manager: either the service is not running, it was uninstalled, or the .ND (Network Descriptor) file on the workstation points to a host that no longer serves the file in that role.

What Triggers It

Our engineers have traced error -6010, -100 to a handful of recurring scenarios:

QuickBooks Database Server Manager was uninstalled or stopped on the host — the most common trigger. This can happen during a QuickBooks update, a Windows update, or manual cleanup.
Hosting was moved to a different computer — the old host still has hosting turned on, or the .ND files on workstations still reference the previous host.
QuickBooks was reinstalled or repaired on the host — the Database Server Manager component was not selected during reinstall.
A firewall or antivirus tool quarantined the database service executable (QBW32.exe or QBDBMgrN.exe), preventing it from starting.
The host machine was renamed — the .ND files still contain the old computer name.

How to Fix It

Scenario 1: Database Server Manager Is Stopped or Uninstalled (Most Common)

On the host machine, open Control Panel > Programs and Features (or Apps & Features in Windows 10/11).
Locate QuickBooks in the program list, select it, and click Uninstall/Change.
In the QuickBooks installation wizard, choose Change (not Remove).
Expand the QuickBooks Database Server Manager option and set it to Install on this computer or Will be installed on local hard drive.
Complete the wizard and restart the host machine.
After restart, open QuickBooks Database Server Manager from the Windows Start menu.
Click the Scan Folders tab, then Add Folder and browse to the folder containing your .QBW file.
Click Scan and wait for the scan to complete. The company file should appear in the results list.
On each workstation, open QuickBooks and switch to multi-user mode to confirm connectivity.

Scenario 2: Hosting Was Moved to a Different Computer

On the old host, open QuickBooks, go to File > Utilities. If you see Stop Hosting Multi-User Access, select it to turn hosting off on that machine.
On the new host, go to File > Utilities and select Host Multi-User Access.
Run QuickBooks Database Server Manager on the new host and scan the company file folder (steps 6-8 above).
On each workstation, delete the existing .ND file associated with the company file (e.g., CompanyFile.QBW.ND). QuickBooks will regenerate it on next open.
Open the company file on each workstation and select multi-user mode.

Scenario 3: Host Machine Was Renamed

On each workstation, navigate to the folder containing the company file.
Open the .ND file in Notepad (right-click > Open with > Notepad).
Look for the line containing SERVER_NAME= and verify it matches the current host machine name.
If it does not match, delete the .ND file entirely.
Run QuickBooks Database Server Manager on the host and scan the folder to regenerate the .ND file with the correct server name.
Open the company file on a workstation to confirm the connection.

Scenario 4: Firewall or Antivirus Is Blocking the Service

Open Services on the host (press Win + R, type services.msc, press Enter).
Locate QuickBooksDBXX (where XX is the QuickBooks version number, e.g., QuickBooksDB33 for 2023).
Confirm the status is Running and the startup type is Automatic. If it is stopped, right-click and select Start.
If the service will not start, check your firewall and antivirus software for blocked or quarantined items related to QuickBooks.
Add exceptions for QBW32.exe, QBDBMgrN.exe, and QBDBMgr.exe in your firewall and antivirus exclusions.
Restart the host and test file access from a workstation.

How to Prevent It Recurring

Our engineers recommend the following practices to keep error -6010, -100 from returning:

Verify hosting on only one machine. Only the designated server or host should have multi-user hosting enabled. Workstations must have hosting turned off.
Run Database Server Manager scans after any QuickBooks update or reinstall. Updates can reset service configurations; a quick scan re-registers the company file.
Avoid renaming the host machine without updating .ND files or re-scanning afterward.
Pin QuickBooks firewall exceptions in any new antivirus or firewall deployment so the database service is not inadvertently blocked.
Document the host machine name for reference so that if .ND files need manual editing, the correct server name is available.