QuickBooks Error 6130: Resolving Database Server Connection Problems

QuickBooks Error 6130 (often accompanied by Error 6130, 0) occurs when QuickBooks Desktop on a client workstation cannot communicate with the database service hosted on the server or host computer. The error message indicates that the system is unable to access the company file (.QBW) because the background database manager process has halted, companion Network Data (.ND) files are damaged, or a Windows firewall rule is blocking communication over port 8019. Restarting the dedicated database service on the host computer and rebuilding the network configuration files resolves the connection blockage.

Fast-Fix: The 45-Second Solution

To resolve Error 6130 immediately, restart the QuickBooks database service on the host server and rename the .ND file. On the host server, press Windows Key + R, type services.msc, locate QuickBooksDBXX (where XX is your version year), and click Restart. Next, open the folder containing your company file, rename [FileName].qbw.nd to [FileName].qbw.nd.old, and rescan the folder using the QuickBooks Database Server Manager.

Quick Status & Triage Snapshot

• Data Risk Tier: Low (Error 6130 is a network transport and service-layer communication failure; the underlying accounting ledger is intact).
• Multi-User Impact: High (All workstations connecting to the hosted company file are blocked until the database service connection is restored).
• Common Trigger: Server reboots that fail to automatically restart the QuickBooksDBXX service, Windows firewall updates blocking dynamic database ports, or corrupted .ND files.
• Estimated Fix Time: 5 to 15 minutes.

Diagnostic Flowchart: Error 6130 Decision Path

Plaintext

[Start: "An error occurred when QuickBooks tried to access the company file" - Error 6130]
       │
       ▼
Is the company file located on a dedicated Server or Host PC?
       │
       ├─► NO (Local C: Drive)
       │     └─► Rename .ND and .TLG files > Run QuickBooks File Doctor via Tool Hub.
       │
       └─► YES (Network / Dedicated Server)
             │
             ▼
Check Windows Services on the Host Server (services.msc)
             │
             ├─► Is QuickBooksDBXX Running?
             │     │
             │     ├─► NO  ──► Set Startup Type to "Automatic" > Start Service.
             │     │
             │     └─► YES ──► Restart Service > Rename companion .ND file to .ND.old.
             │                   │
             │                   ▼
             │               Rescan Company Folder in Database Server Manager
             │                   │
             │                   ├─► File opens across network ──► Connection restored.
             │                   └─► Error persists ──► Check Windows Firewall Port 8019.

Is Your Data at Risk?

Error 6130 occurs at the network connection layer before any transaction commands are processed by the Sybase SQL engine.

• During Standard File Launch: Your balances, journals, customer lists, and transaction history are completely safe. The application fails before mounting the .QBW file into active memory.
• Safe Restart Procedure: You can safely restart the QuickBooksDBXX and QBCFMonitorService services in Windows without risking data loss, provided no other users are actively performing data writes.
• Precaution During Backups/Rebuilds: If Error 6130 appeared abruptly during a data rebuild or scheduled backup, check that the host server did not run out of storage space. Run a data verification pass once connectivity is re-established.

Technical Anatomy: What Error 6130 Means

When a workstation opens a multi-user company file, it must complete a handshake with the host machine’s Sybase database engine:

1. The Network Data Handshake: The client reads the .ND file located in the shared network directory. This file informs the workstation which IP address and dynamic port the host database manager is currently monitoring.
2. The Database Daemon (qbdbmgrn.exe): The host server runs the QuickBooksDBXX service. When the client attempts to establish a TCP socket connection, the server daemon must authenticate the request and issue a database session token.
3. The Connection Failure: Error 6130 is triggered when the workstation reaches the host machine, but the host database engine either fails to respond (because qbdbmgrn.exe stopped), rejects the network handshake due to a corrupted .ND file, or has its response packet dropped by an intermediate firewall rule.

Differential Diagnosis: Don’t Confuse This With…

• QuickBooks Error 6175: Occurs when QuickBooks on a host workstation is set to multi-user mode, but the database service itself was never installed or failed to initialize during Windows startup.
• QuickBooks Error 6129, 0: Occurs when the database connection verification handshake fails due to Windows domain authentication errors or security certificate mismatches.
• QuickBooks Error 6000, -82: Triggered when multiple client computers have hosting turned on simultaneously, creating conflicting database signals across the network.

Step-by-Step Repair Guide

Follow these steps in order, starting on the host server or main computer storing the company file.

Step 1: Verify and Restart the QuickBooks Database Service

If the Windows service associated with the database manager stops or hangs, network workstations cannot establish a socket connection.

1. On the host server, press Windows Key + R to open the Run dialog box.
2. Type services.msc and press Enter.
3. Scroll down the list of services and locate your version of the QuickBooks database service:
   • QuickBooksDB36 (QuickBooks Desktop 2026)
   • QuickBooksDB35 (QuickBooks Desktop 2025)
   • QuickBooksDB34 (QuickBooks Desktop 2024)
4. Check the Status column:
   • If it is Stopped, right-click the service and select Start.
   • If it is Running, right-click the service and select Restart.
5. Right-click the service again, select Properties, change the Startup type to Automatic, and click OK.
6. Locate QBCFMonitorService, ensure it is running, and set its startup type to Automatic as well. For troubleshooting stuck services.

Step 2: Recreate Damaged .ND and .TLG Support Files

Outdated or corrupted .ND configuration files prevent the client from locating the correct server port.

1. Ensure QuickBooks is closed on all client workstations.
2. On the server, open File Explorer and browse to the company file folder (e.g., C:\QuickBooksData).
3. Locate the files matching your company file name with the extensions .ND and .TLG:
   • [YourCompany].qbw.nd
   • [YourCompany].qbw.tlg
4. Right-click each file, select Rename, and append .old to the end:
   • [YourCompany].qbw.nd.old
   • [YourCompany].qbw.tlg.old

Step 3: Rescan the Directory with QuickBooks Database Server Manager

Rescanning forces the database manager to regenerate a fresh .ND file containing the server’s current IP address and port bindings.

1. On the host server, open the Windows Start menu and launch QuickBooks Database Server Manager.
2. Go to the Scan Folders tab.
3. Click Add Folder and select the folder where your .QBW file is stored.
4. Click Scan.
5. When the scan finishes, ensure your company file appears in the lower box with an active database status.
6. Open QuickBooks on a workstation and attempt to open the file across the network. If the scanner fails to recognize company files.

Step 4: Configure Windows Firewall and Port Exceptions

If the database service is running and the .ND file is regenerated, but workstations still cannot connect, the Windows Firewall is blocking inbound database traffic.

1. On the host server, open Control Panel > Windows Defender Firewall > Advanced Settings.
2. Click Inbound Rules on the left, then click New Rule on the right.
3. Select Port, click Next, choose TCP, and in the Specific local ports box, enter port 8019 and your version’s assigned dynamic port range.
4. Select Allow the connection, apply it to Domain, Private, and Public network profiles, name the rule QuickBooks Database Service, and click Finish.

Hard Stop: When to Call an Expert

If restarting services, recreating the .ND file, and opening firewall ports fail to clear Error 6130:

• Persistent Service Startup Crashes: The QuickBooksDBXX service immediately crashes after clicking Start, displaying error codes such as Windows Error 1067 or 1053. This indicates damaged .NET components or registry keys requiring a clean reinstall of the Database Server Manager.
• Corrupt Operating System Network Stack: The server cannot assign static IP bindings, or network diagnostic tools return physical socket transport errors across all client machines.

Closing the Books

QuickBooks Error 6130 is a communication bottleneck between your workstation and the host database manager, not an indicator of corrupted company records. By restarting the QuickBooksDBXX service, refreshing your network data files with the Database Server Manager, and confirming that port 8019 is open in Windows Firewall, you can safely restore multi-user access across your entire network.