QuickBooks Error 6130: Resolving Database Server Connection Problems

QuickBooks Error 6130 occurs when QuickBooks Desktop cannot establish or maintain an active connection with the database engine hosted on your network server. The error dialog typically indicates that the database server is not running or network communication was severed. This issue arises when the QuickBooks Database Server Manager service (QuickBooksDB##) stops unexpectedly, Windows Firewall blocks incoming database ports, or network cards drop connection threads. You can resolve Error 6130 by restarting the host database service, scanning file directories, and configuring your firewall ports.

Fast-Fix: The 45-Second Solution

To fix QuickBooks Error 6130, restart the QuickBooks database service on the host server. Press Windows Key + R on the server, type services.msc, and press Enter. Locate the service matching your QuickBooks version (such as QuickBooksDB34 for 2024 or QuickBooksDB35 for 2025), right-click it, and select Restart. Next, restart QBCFMonitorService. Once restarted, reopen QuickBooks on your workstation.

---

Quick Status & Triage Snapshot

• Data Risk Tier: Low. The error reflects a stopped background service or dropped network connection; it does not indicate data table corruption.
• Multi-User Impact: Complete. When the database server service halts, every workstation on the network is blocked from opening company files on that host.
• Common Triggers: The QuickBooksDB## service stopping after a server reboot, Windows Firewall blocking port 8019, dynamic port changes, or network adapter power-saving dropouts.
• Estimated Fix Time: 5 to 15 minutes.

---

Technical Anatomy: How QuickBooks Communicates with the Database Server

In a multi-user environment, QuickBooks Desktop does not read the .QBW company file directly over standard Windows file sharing. Instead, it relies on client-server database architecture:

1. The Daemon Process: The database engine (qbdbmgrn.exe) runs as a Windows background service under the account name QuickBooksDB## (where ## corresponds to the software release year).
2. The Connection Monitor: The QBCFMonitorService continually monitors folder shares and checks that the database engine is ready for incoming requests.
3. The Communication Port: When a workstation initiates a query, it routes packets to the server via port 8019 and a dynamic database port assigned during setup.

If the QuickBooksDB## service stops unexpectedly, or if the firewall blocks packets directed to its assigned ports, the client software cannot communicate with the database engine, resulting in Error 6130.

---

Diagnostic Flowchart: Error 6130 Decision Path

Start: Error 6130 appears on client workstation
 │
 ├──> Check host server Windows Services (services.msc)
 │     ├── Is QuickBooksDB## stopped?
 │     │     └── YES ──> Start service and set Startup type to Automatic.
 │     └── Is QuickBooksDB## running?
 │
 ├──> Test QBCFMonitorService status
 │     └── If stopped or paused, restart the service.
 │
 ├──> Rescan company folder using QuickBooks Database Server Manager.
 │     ├── Are files detected with "OK" status?
 │     │     ├── NO  ──> Reconfigure folder sharing and Windows permissions.
 │     │     └── YES ──> Proceed to firewall port validation.
 │
 └──> Configure Windows Firewall to open TCP port 8019 and dynamic version ports.

---

Step-by-Step Repair Guide

Follow these steps directly on the computer or server hosting your company files.

Step 1: Restart QuickBooksDB and QBCFMonitorService

If the host services stop or enter a hung state, workstations cannot reach the database.

1. Log in to the host server as a Windows Administrator.
2. Press Windows Key + R, type services.msc, and press Enter.
3. Scroll down to find the service corresponding to your QuickBooks version:
   • QuickBooks 2026: QuickBooksDB36
   • QuickBooks 2025: QuickBooksDB35
   • QuickBooks 2024: QuickBooksDB34
   • QuickBooks 2023: QuickBooksDB33
4. Right-click the service, select Properties, ensure the Startup type is set to Automatic, then click the Start button (or Restart if already running).
5. Switch to the Recovery tab inside Properties. Set First failure, Second failure, and Subsequent failures to Restart the Service. Click Apply and OK.
6. In the Services list, locate QBCFMonitorService, right-click it, and select Restart.

If the service refuses to stay running, follow our troubleshooting steps in Service Fix: Troubleshooting “QuickBooks Database Server Manager Stopped”.

Step 2: Rescan Company Folders in Database Server Manager

Rescanning ensures the database manager has active file locks and has created valid network connection files.

1. On the host server, open the Start menu, search for QuickBooks Database Server Manager, and launch it.
2. Select the Scan Folders tab.
3. Click Add Folder and browse to the folder where your company files (.QBW) are stored.
4. Click Scan.
5. When the scan finishes, ensure your company files appear in the bottom pane with the status confirmed as “Scan complete” or “OK.”
6. Open Windows File Explorer, browse to your company file directory, and verify that a newly generated .ND file exists alongside your .QBW file.

Step 3: Open Port 8019 and Dynamic Database Ports in Windows Firewall

If the services are running but workstations still receive Error 6130, Windows Firewall is likely blocking incoming connection requests.

1. Press Windows Key + R, type wf.msc, and press Enter to open Windows Defender Firewall with Advanced Security.
2. In the left pane, right-click Inbound Rules and select New Rule…
3. Select Port and click Next.
4. Select TCP, and in the Specific local ports field, enter:
   • Port: 8019
   • In addition, add your year-specific dynamic port range (e.g., 55383-55387 for QuickBooks 2024/2025).
5. Click Next, choose Allow the connection, and click Next.
6. Check all network profiles (Domain, Private, and Public), click Next, name the rule QuickBooks Database Ports, and click Finish.

For explicit firewall configurations and automated port utility steps, consult QuickBooks 2026 Firewall Setup: Configuring Port 8019 for Connectivity.

Step 4: Disable Power-Saving Modes on Server Network Cards

If Error 6130 occurs intermittently or after the server has been idle for several hours, Windows may be putting the network adapter to sleep.

1. Press Windows Key + R, type devmgmt.msc, and press Enter to open Device Manager.
2. Expand the Network adapters section.
3. Right-click your active physical network card (Ethernet NIC) and select Properties.
4. Navigate to the Power Management tab.
5. Uncheck the box labeled Allow the computer to turn off this device to save power.
6. Click OK, then close Device Manager.

---

Differential Diagnosis: Error 6130 vs. Related Server Errors

• Error 6130 vs. QuickBooks Error 6175: Fix: QuickBooks Unable to Start Database Server: Error 6175 occurs when QuickBooks attempts to access a file hosted on a computer that is not configured for hosting, or when the database service fails to start during file launch. Error 6130 indicates that communication dropped while accessing an existing database session.
• Error 6130 vs. Setup Failures: If you are configuring a new dedicated Windows server, ensure hosting parameters match enterprise requirements. Review the Server Guide: How to Configure QuickBooks Hosting for Dedicated Servers to verify your network setup.

---

Hard Stop: Persistent Service Crashes

If the QuickBooksDB## service starts but terminates within seconds of a workstation attempting to connect, the service executable or database registry hive has experienced structural damage.

Do not edit database tables directly. Execute a service reset by following Manual Reset: How to Restart QuickBooks Database Services (dbmgr.exe). If the service continues to crash, perform a clean uninstall and reinstallation of the QuickBooks Database Server Manager component using the QuickBooks Tool Hub.