QuickBooks Error 6129-105: Company File Verification Fails on the Host
Error 6129-105 appears when QuickBooks cannot verify the company file on the host computer; our engineers trace the connection and reopen the file.
Error 6129-105 stops QuickBooks Desktop before the company file even opens. The program contacts the machine that hosts the file, runs its connection verification, and fails it. In the repair cases our engineers handle, the cause sits in the network path to the file rather than in the data itself. Most jobs end with a firewall or hosting setting corrected on the host computer.
The message QuickBooks shows
When the error appears, QuickBooks presents a dialog close to this:
QuickBooks was unable to open the company file [path] on the host computer. Error code: (-6129, -105)
The bracketed text is the full location of your company file on the network. Exact wording shifts a little between releases. The behaviour does not shift at all: the file stays closed, and QuickBooks refuses multi-user mode until the connection check passes.
What does the code mean?
The 6129 code belongs to the 6000 series, the family QuickBooks raises whenever it cannot reach, verify, or open a company file. The leading number reports a failed database connection verification: QuickBooks asked the host computer to confirm the file and did not get a clean answer back.
The suffix narrows the cause to the network side of that exchange rather than damage inside the data. We therefore treat this code as a connectivity problem first, and we test the file itself only once the connection checks out.
Common triggers
The same few situations produce almost every occurrence:
- A firewall on the host computer, whether Windows Defender Firewall or a third-party security suite, silently drops the traffic QuickBooks Database Server Manager needs.
- The host is not really hosting: the Database Server Manager service has stopped, or the folder holding the file was never scanned.
- More than one machine has multi-user hosting switched on, so workstations try to reach the wrong computer.
- The .ND configuration file beside the company file is stale after a server rename, an address change, or a move to a new folder.
- The folder lacks the share and read and write permissions QuickBooks requires on a Windows network.
How do you fix it?
Work through the scenarios below in order. The first covers most of the cases that reach us. Unless we say otherwise, every step happens on the host computer, the machine where the company file physically lives.
The firewall is blocking QuickBooks
- On the host computer, open Windows Security, choose Firewall & network protection, then select Allow an app through the firewall.
- Add an exception for QuickBooks and another for QuickBooks Database Server Manager, and tick the private network box for both.
- If a third-party security suite controls the firewall instead, add the same exceptions inside its own console. The Windows settings will not override it.
- If you prefer explicit port rules, open QuickBooks Database Server Manager, read the ports listed in its port monitor, and create an inbound rule for each one.
- Test the result by opening the company file from a workstation in multi-user mode.
If you would rather let a tool handle it, the File Doctor included in the QuickBooks Tool Hub can repair common firewall configuration problems automatically.
The host is not actually hosting
- On the machine that should hold the file, open QuickBooks Database Server Manager from the Start menu.
- Confirm the QuickBooksDB service is running. If it is stopped, start it and set it to launch automatically.
- Open the Scan Folders tab, add the folder that stores the company file, and run a scan. The file should appear in the results with its location.
- On every other computer, open QuickBooks, choose the File menu, then Utilities. If the menu offers Stop Hosting Multi-User Access, that machine is hosting too. Stop it, so exactly one host remains.
The .ND file has gone stale
- Close QuickBooks on every computer on the network.
- Open the folder that holds the company file and find the file with the same name and an .ND extension.
- Rename that file, adding .old to the end. It holds configuration details only, and QuickBooks rebuilds it from scratch.
- Rescan the folder on the host with Database Server Manager, then open the file in multi-user mode. A fresh .ND file appears on the spot.
Folder permissions are missing
- On the host, right-click the folder that holds the company file and choose Properties.
- On the Sharing tab, confirm the folder is actually shared, and note the share name.
- On the Security tab, give the Windows accounts that run QuickBooks read and write access.
- From each workstation, open the file by browsing to the shared location. Opening a copy stored on the local disk never reaches the host at all.
Keeping the error from coming back
Prevention is routine work on the host machine. Update Database Server Manager whenever QuickBooks receives a new release or a new year version, because an outdated host database engine quietly breaks the connection check. Refresh the firewall exceptions each time QuickBooks is installed or upgraded, since updates replace the programs those exceptions point to.
Leave hosting switched on for one computer only, and rescan the folder whenever the file moves or the server changes name or address. Our engineers run these checks as part of every hosting and connectivity repair we carry out.