QuickBooks Error 6094-0: Firewall and Antivirus Blocking the Database Server
QuickBooks Desktop error 6094-0 blocks company file access in multi-user mode when security software interferes; here is how our engineers resolve it.
Error 6094-0 stops QuickBooks Desktop the moment you try to open a company file in multi-user mode. The program calls on the database server that hosts the file, the server fails to start, and the file stays closed. In most cases security software is the reason, and the sequence below clears it.
The exact error message
Before the company file opens, QuickBooks displays this text:
An error occurred when QuickBooks tried to start the database server that provides access to the company file. Error codes: 6094, 0.
Some installations show the first code with a minus sign, as -6094, 0. The wording and the failure point are the same either way. The database server process never starts, so the file never opens.
What does error 6094-0 mean?
QuickBooks Desktop relies on a separate component in multi-user mode. The Database Server Manager, built by Intuit, hosts the company file on one machine and lets other workstations connect to it. The host process runs as a Windows service and is launched from an executable named QBDBMgrN.exe.
The 6094 code means that launch failed. QuickBooks asked the service to start, something interrupted the request, and the open attempt failed. The trailing 0 is a status detail; the pair together identifies this particular startup failure.
What triggers error 6094-0?
Any of these conditions can produce the code, and our case history points clearly at the first:
- A firewall or antivirus policy blocks QBDBMgrN.exe, so the server process cannot run or cannot accept connections.
- The Windows service behind the server is stopped, or its startup type is set to manual or disabled.
- The .nd network descriptor beside the company file is stale or damaged, so it points to a server instance that no longer exists.
- Antivirus quarantined a QuickBooks component during a scan, leaving the server unable to start.
- The company file sits in a folder that cloud sync software controls, and the sync layer locks it while the server tries to host it.
Fixing error 6094-0
Work through the scenarios in order. The first one resolves the majority of cases we see.
Security software is blocking the database server
- On the machine that hosts the file, open your antivirus or firewall console.
- Add exclusions for the QuickBooks executables, starting with QBDBMgrN.exe, QBDBMgr.exe, and QBW32.exe, in the folder where QuickBooks is installed. If the software keeps an application rules list, set each one to allow.
- In the firewall, create inbound and outbound allow rules for the same executables. Allow the program itself rather than a fixed port, because the port assignment changes between version years.
- Restart the machine, or stop and restart the QuickBooksDB service in Windows Services, so the new rules take effect.
- Open the Database Server Manager, scan the folder that holds the company file, then open the file again.
The database service is not running
- On the hosting machine, open Windows Services.
- Locate the service whose name begins with QuickBooksDB and ends in a number matching your version year.
- Set the startup type to Automatic, then start the service.
- Try the company file again in multi-user mode.
The .nd file is stale or damaged
- Close QuickBooks on every workstation.
- In the folder that holds the company file, rename the matching .nd file by adding .old to the end of its name. Renaming is safe; QuickBooks rebuilds the file.
- Run a folder scan in the Database Server Manager.
- Open the company file again.
Antivirus quarantined QuickBooks components
- Open the quarantine area of your antivirus software and look for QuickBooks files.
- Restore anything that was flagged, then add exclusions so the same files are not removed again.
- If components were deleted rather than quarantined, run the QuickBooks installer again and choose the repair option so the Database Server Manager is reinstalled.
Keeping error 6094-0 from coming back
Most recurrences trace back to an upgrade. Each version year installs into a new folder and re-registers the server, so exclusions tied to the old folder stop matching. After any upgrade, refresh the exclusions and run a new folder scan.
Keep the company file out of folders that cloud sync tools watch. A file locked mid-upload cannot be hosted, and the server fails at startup. Leave the QuickBooksDB service set to Automatic as well, so hosting survives a server restart without manual steps.
If the code persists after all four scenarios, the hosting layer is likely healthy and the data file itself may be the problem. At that point a structural review of the file is the next sensible step.