QuickBooks Error -6129, -101 -- Network Company File Will Not Open

QuickBooks error -6129, -101 blocks database connection verification when a company file opens over a network. Here is what the code means and how to clear it.

Error -6129, -101 appears when QuickBooks Desktop cannot verify the database connection to a company file stored on another computer. The file may be perfectly healthy. The failure usually sits in the connection path between the workstation and the host. This page covers what the message means, what sets it off, and the steps our engineers take to clear it.

What the error message says

The message typically reads:

"Connection to the QuickBooks company file has been lost. Error code: -6129, -101. Database connection verification failure."

In multi-user mode you may also see a note that QuickBooks cannot reach the QuickBooks Database Manager on the host computer. The dialog usually appears immediately after you select the company file, before any data loads.

What the code means

The 6000 series covers company file access problems. The -6129 portion signals that the database server manager could not confirm the connection to the file. The -101 suffix narrows it to a verification failure during the initial handshake rather than a read or write error later in the session.

In plain terms, QuickBooks asked the hosting computer for permission to open the file, and the answer never arrived or arrived in a form QuickBooks could not use. The data itself is often untouched.

What triggers it

The most common triggers we see are:

1. The QuickBooks Database Manager service on the host is stopped or failed to start.
2. The company file was moved, renamed, or restored to a new location without re-scanning the folder.
3. Windows folder permissions block the QuickBooks service account from reading the file.
4. Firewall or antivirus software is filtering the ports QuickBooks uses for database traffic.
5. The workstation and host are running mismatched QuickBooks versions or database manager versions.
6. The file is being opened across a mapped drive letter that Windows has not fully restored after a reboot.

How to fix it

Work through these scenarios in order. The first resolves the largest share of cases.

Scenario 1: the database manager is not running on the host.

1. On the host computer, close QuickBooks on all machines.
2. Open the Windows Services list and look for QuickBooksDBXX, where XX matches your QuickBooks version year.
3. If it is stopped, start it and set the startup type to Automatic.
4. Open the QuickBooks Database Server Manager, choose Scan Folders, and add the folder holding the company file.
5. Run the scan, confirm the file appears in the results, then open the file from the workstation.

Scenario 2: the folder has not been scanned after a move or restore.

1. Open QuickBooks Database Server Manager on the host.
2. Remove the old folder from the scan list if it no longer holds the file.
3. Add the current folder and scan it.
4. Confirm the company file name appears with the correct version year before reopening it.

Scenario 3: Windows permissions are blocking access.

1. On the host, right-click the folder holding the company file and open its sharing and security settings.
2. Grant full control to the Windows user account used by the QuickBooks database service, and to QBDataServiceUser entries.
3. Apply the change to the folder, its subfolders, and files.
4. Reboot the host and try the file again.

Scenario 4: firewall or antivirus interference.

1. Add QuickBooks and the database manager executables to the firewall exceptions list on both the host and the workstation.
2. If your antivirus has its own network filter, add the same exceptions there.
3. Restart the database manager service and test the connection.

Scenario 5: version mismatch after an upgrade.

1. Press F2 in QuickBooks on each machine and compare the version and release numbers shown.
2. Update every installation to the same release.
3. Reinstall the database manager on the host if it lags behind, then rescan the folder.

Scenario 6: mapped drive problems.

1. Disconnect the mapped drive on the workstation.
2. Remap it, or browse to the file by network path instead of the drive letter.
3. Open the file directly from the File menu using that path.

How to prevent it recurring

Keep the database manager service set to Automatic on the host. After any file move, rename, or restore, run a folder scan before users connect. Apply QuickBooks updates to every machine at the same time so versions stay matched. Finally, set firewall exceptions once, centrally, rather than relying on per-workbook prompts that a future update may reset.