QuickBooks Error 6129-102: Database Server Refused the Connection

We explain what error 6129, 102 means and how our engineers restore multi-user access when QuickBooks cannot reach the company file's database server.

Error 6129, 102 stops a workstation from opening a shared company file in multi-user mode. QuickBooks itself is rarely at fault. The database service on the host computer is not answering, or something between the two machines, most often a firewall, is blocking the conversation. Our engineers see this code after server restarts, Windows updates, and changes to security software. The company file is normally intact; the problem sits in the connection, not the data.

The exact message

The dialog usually reads:

QuickBooks has attempted to open this company file in multi-user mode and the database server has refused the connection.

The code below it appears as (-6129, 102). A few releases word the message differently, but the number stays the same, and so does the meaning.

What does the code mean?

The 6129 family covers failed database sessions in multi-user mode. The -102 part means the server refused the connection: the workstation asked the database service for a session and never received a usable answer.

That makes this a communication failure, not data damage. QuickBooks Database Server Manager, the service that shares the file with the network, is stopped, or a firewall is dropping the traffic between the two machines. Fix the connection and the file opens as before.

What triggers it?

The causes we find most often:

  • The QuickBooks database service on the host stopped after a reboot, an update, or a crash.
  • Windows Firewall or a third-party security suite blocks the ports the service uses.
  • The network data (.ND) file went stale after the server's name or address changed.
  • The workstation opened a local copy of the file, or two machines both claim hosting.
  • The host and the workstation run different QuickBooks releases.

The code also shows up while creating a new company file, because setup tries a multi-user open before any connection exists.

How do you fix error 6129, 102?

Work through these in order. Most cases clear in the first two sections.

Restart the database service on the host

  1. Go to the computer that stores the company file, not the workstation showing the error.
  2. Press the Windows key and R together, type services.msc, and press Enter.
  3. Find the service whose name starts with QuickBooksDB and ends with a two-digit number tied to your release.
  4. If the Status column says Stopped, right-click the service and choose Start. If it says Running, choose Restart so the session starts clean.
  5. Double-click the service, set Startup type to Automatic, and save.
  6. Return to the workstation and open the company file.

Let the firewall pass QuickBooks traffic

  1. On the host, open Windows Security, then Firewall & network protection, then Allow an app through the firewall.
  2. Find QuickBooks Database Server Manager in the list and tick the Private box. Tick the Public box as well if your network is set to Public.
  3. If the entry is missing, add QBDBMgrN.exe and QBW32.exe from your QuickBooks installation folder.
  4. A third-party antivirus suite keeps its own rules. Add the same programs to its exclusions, or turn it off briefly to see whether the error clears.
  5. On a business domain, ask your network administrator to open the ports listed on the Port Monitor tab of Database Server Manager.

Rebuild the network data file

  1. On the host, open the folder that holds the company file.
  2. Find the file with the same name but an .ND extension.
  3. Rename it by adding .old at the end.
  4. Open QuickBooks Database Server Manager, choose Scan Folders, add the folder, and run the scan. A fresh .ND file is written.
  5. Try the workstation again.

Run the built-in diagnostic

QuickBooks ships a repair tool inside the Tool Hub. Install the Tool Hub on the workstation, open the Company File Issues tab, and run QuickBooks File Doctor against the shared file. The tool tests hosting, repairs connectivity, and rebuilds firewall rules on its own. A scan of a large file takes several minutes, so let it finish before you retry.

Creating a new company file

If the error appeared during new company setup, finish the setup on the host computer itself. Then apply the service and firewall fixes above and open the new file from the workstation.

Keep the connection working

  • Leave the database service on Automatic startup and glance at it after every planned server restart.
  • Keep the same QuickBooks release on the host and every workstation, and update them together.
  • Re-scan the company file folder in Database Server Manager whenever the file moves or the server's name or address changes.
  • Revisit the firewall rules whenever you update or replace security software, because a new version can restore its default blocks.
  • Store the file on the host's own drive and let the database service share it, rather than opening it across a plain Windows share.

If the code returns after all of these steps, the cause runs deeper than the network. At that point it is worth having both the host setup and the file itself examined, because a damaged installation can produce the same refusal.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.