QuickBooks Error -6130, 0 -- Database Connection Failure

QuickBooks error -6130, 0 blocks access to your company file after a dropped database connection; our engineers walk through restoring connectivity step by step.

QuickBooks Error -6130, 0 appears when the QuickBooks Database Server Manager loses its connection to the company file mid-session or cannot establish one at launch. The error blocks all access to the file until the underlying database connection is restored and the file's integrity is confirmed.

What the Error Message Says

The full message displayed by QuickBooks is:

Warning: QuickBooks is unable to open this company file. Error code: (-6130, 0).

In some cases the message is preceded by a brief hang or a "Working..." spinner. On multi-user setups, other workstations may already be disconnected when the dialog appears.

What the Code Means

The -6130, 0 code belongs to the 6000 series of company-file errors. The first component (-6130) signals that QuickBooks attempted to open the file through the database server service but the connection was severed or rejected. The second component (0) indicates that no secondary Windows-level error was captured. In practice, the database engine either crashed, was stopped by another process, or lost access to the .QBW or .ND file on disk.

What Triggers It

Our engineers see this error most often in these scenarios:

1. Database Server Manager stopped or crashed while the file was open, severing the live connection.
2. Network interruption between a workstation and the host machine in multi-user mode.
3. Windows update or antivirus scan locking or quarantining the company file or its supporting .ND/.TLG files.
4. Power loss or hard shutdown leaving the database service in an inconsistent state.
5. Damaged .ND (Network Descriptor) file pointing QuickBooks to a server path that no longer resolves.

How to Fix It

Scenario 1: Database Server Manager stopped or crashed (most common)

1. Close QuickBooks on all workstations and the host.
2. On the host machine, open the Windows Start menu and type Services.
3. Scroll to QuickBooksDBxx (where xx is the QuickBooks version number, e.g., 33 for 2023).
4. Right-click the service and select Restart. If it was stopped, select Start.
5. Confirm the Startup Type is set to Automatic.
6. Reopen QuickBooks and try the company file again.

Scenario 2: Network interruption in multi-user mode

1. Verify the host computer is powered on and logged into Windows.
2. On the workstation, open File Explorer and type \\<host-computer-name> in the address bar to confirm network share access.
3. If the share does not open, ping the host by name from a command prompt to verify connectivity.
4. Once the share is accessible, close and reopen QuickBooks, then switch to single-user mode temporarily to confirm the file opens.
5. Re-enable multi-user mode via File > Switch to Multi-user Mode.

Scenario 3: Windows update or antivirus interference

1. Check whether a recent Windows update rebooted the host machine; if so, restart the QuickBooksDB service as described above.
2. Temporarily disable real-time antivirus scanning on the folder containing the .QBW file.
3. Add the company file folder to your antivirus exclusion list.
4. Verify that no Windows Defender controlled-folder-access rule is blocking QuickBooks from writing to the file.

Scenario 4: Power loss or hard shutdown

1. Restart the host machine cleanly.
2. Restart the QuickBooksDB service in the Services console.
3. Open QuickBooks and allow it to run its built-in file verification. If prompted to rebuild, allow the process to complete.
4. If verification fails, restore from the most recent backup before the shutdown occurred.

Scenario 5: Damaged .ND file

1. Close QuickBooks on all machines.
2. Navigate to the folder containing the company file.
3. Locate the file ending in .ND that shares the name of your company file.
4. Rename it to CompanyFileName.ND.OLD.
5. Run the QuickBooks Database Server Manager on the host, then select Scan Folders and point it at the company file directory.
6. After the scan completes, open the company file again.

How to Prevent It Recurring

• Set the QuickBooksDB service Startup Type to Automatic on every host so it restarts after reboots without manual intervention.
• Configure your antivirus to exclude the company file folder from real-time scanning and scheduled full scans.
• Place the host machine on a UPS to prevent hard shutdowns during power events.
• Run Database Server Manager's folder scan after any server rename, IP change, or folder move so the .ND files stay current.
• Keep all workstations on the same QuickBooks release and update patch level to avoid database-engine version mismatches that can destabilize connections.