“QBDBMgrN not running on this computer” means one specific thing. The Windows service that hosts your QuickBooks company file over the network is stopped, blocked, or unreachable from the machine that showed you the message. Nothing is wrong with your data. The file is fine. A background service is not answering.

That distinction matters because it decides where you spend the next twenty minutes. Most people start by reinstalling QuickBooks on the workstation that threw the error, which is almost always the wrong machine. The service in question — QBDBMgrN.exe, registered in Windows as QuickBooksDBXX — only runs on the computer that stores the .qbw file. If it is down there, every workstation in the office drops out of multi-user mode at once, and every one of them can display this message.

This guide works through the failure in the order the components actually depend on each other: service state, hosting mode, the network data file, the firewall, then permissions. Each step tells you how to confirm it worked before you move on. You are never left guessing whether the last change did anything.

Key Takeaways

1. QBDBMgrN.exe is the executable behind the Windows service QuickBooksDBXX, where XX is the release year minus 1990 — QuickBooks Desktop 2025 registers QuickBooksDB35.
2. The service only needs to run on the server (the machine holding the company file), not on every workstation.
3. Restarting the service fixes the symptom; it comes back unless you also fix the cause — usually a firewall rule, a reset startup type after a Windows update, or a broken .ND file.
4. Windows 10 reached end of support on October 14, 2025, and you can enroll a Windows 10 device in Microsoft’s consumer Extended Security Updates program any time until the program ends on October 12, 2027 (Microsoft, retrieved 2026-08-05). A server still on Windows 10 is worth checking whenever this error follows an update.
5. You can keep working in single-user mode on the server itself while you troubleshoot. Multi-user is what is broken, not the file.

What the QBDBMgrN Not Running on This Computer error actually means

QuickBooks Desktop in multi-user mode is a client–server application wearing a desktop application’s clothes. The company file is not opened directly over a network share by each workstation. Instead, a database service on the host machine opens the file and brokers every read and write. QBDBMgrN.exe is that service’s executable, and it must be running on the host even when nobody has QuickBooks open there

So the message is a connection report, not a diagnosis. The workstation tried to reach the database service for the company file it was told to open, and got nothing back. Six different root causes produce the identical sentence.

Is QBDBMgrN the same as QuickBooks Database Server Manager?

Effectively yes, at different layers of the same product. QuickBooks Database Server Manager is the name of the tool and its user interface. QBDBMgrN.exe is the executable that runs as a background Windows service. QuickBooksDBXX is the name that service is registered under in services.msc.

The XX suffix is the release year minus 1990. QuickBooks Desktop 2023 registers QuickBooksDB33, 2024 registers QuickBooksDB34, 2025 registers QuickBooksDB35. Each installed year version gets its own service and its own QBDataServiceUserXX account, which is why a server that has hosted three upgrades in a row shows three QuickBooks services in the list. That is normal. Only the one matching the version that created your company file needs to be running.

Why QuickBooks says QBDBMgrN is not running

Six causes cover the cases this guide addresses. They are ordered by how cheap each one is to rule out, not by how often it occurs.

Two of these — hosting configuration and a stale .ND file — also produce the H-series errors (H101, H202, H303, H505) that QuickBooks shows when it can find the file but cannot reach its host. If you are seeing both messages on different machines, treat them as one incident, not two. A 6000-series error is a different failure: that one means QuickBooks reached the file and could not open it.

Five-minute triage before you change anything

Do this before you touch a setting. It takes five minutes and it decides which of the seven fixes below you actually need.

1. Identify the server. The server is whichever machine stores the .qbw file — not necessarily a rack-mounted box, and frequently the office manager’s desktop. Open the company file on any working workstation and press F2. The File Information panel shows the full network path. The machine name in that path is your server.
2. Note the exact QuickBooks year. The same F2 panel shows the product year and release. You need the year to know which QuickBooksDBXX service to look for.
3. Check the service state on the server. Press Windows + R, type services.msc, press Enter, and scroll to the QuickBooks entries. Note the Status and Startup Type columns for the service matching your year.
4. Check whether it is one machine or all of them. If one workstation fails and the others are fine, the problem is on that workstation or in that one machine’s network path. If every workstation fails at once, the problem is on the server. This single observation eliminates about half the guide.

What “working” looks like: on a healthy server, QuickBooksDBXX shows Status “Running” and Startup Type “Automatic”, QBCFMonitorService shows “Running”, and QBDBMgrN.exe appears in Task Manager under Details even with QuickBooks closed.

What “working” looks like: on a healthy server, QuickBooksDBXX shows Status “Running” and Startup Type “Automatic”, QBCFMonitorService shows “Running”, and QBDBMgrN.exe appears in Task Manager under Details even with QuickBooks closed.

Fix 1: Restart the QuickBooksDBXX service

By the end of this step you will have the database service running and configured to start itself after a reboot. This resolves the immediate outage in most cases; the later fixes stop it from recurring.

Before you start: Fixes 1, 4, 5, and 7 all require local administrator rights on the server. If Windows returns “Access is denied”, or a menu option does nothing when you click it, you are not signed in as an administrator — sign in with an admin account or ask whoever set the machine up. Also ask anyone still working in the company file to close it first: restarting this service disconnects every open multi-user session, and unsaved work in an open transaction window can be lost.

On the server:

1. Press Windows + R, type services.msc, press Enter.
2. Scroll to QuickBooksDBXX — match XX to your year (2025 → QuickBooksDB35).
3. Right-click it and select Restart. If Restart is greyed out, the service is already stopped — select Start instead. If you get “Access is denied”, you do not have administrator rights on this machine; see the note above.
4. Right-click again, select Properties, and set Startup type to Automatic.
5. Switch to the Recovery tab and set First failure, Second failure, and Subsequent failures all to Restart the Service.
6. Click Apply, then OK.
7. Repeat steps 3 to 6 for QBCFMonitorService.

Verification: the Status column reads “Running”. Open Task Manager, go to the Details tab, and confirm QBDBMgrN.exe is listed. Then try multi-user login from a workstation.

That Recovery tab is the step most guides skip, and it is the difference between a fix and a patch. Windows will restart a crashed service on its own if you tell it to, which converts a Monday-morning outage into a five-second hiccup nobody notices.

If the service starts and then stops again within a few seconds, do not repeat this step Intuit documents that pattern separately, and it points at account permissions rather than service configuration. Jump to Fix 5.

Fix 2: Confirm hosting is on the server only

By the end of this step exactly one machine on the network will be hosting. More than one host is a frequent cause of an error that keeps coming back after a service restart.

On the server:

1. Open QuickBooks Desktop and go to File → Utilities.
2. If you see Host Multi-User Access, hosting is currently off. Click it to turn it on.
3. If you see Stop Hosting Multi-User Access, hosting is already on. Leave it alone.

On every workstation:

1. Open QuickBooks Desktop and go to File → Utilities.
2. If you see Stop Hosting Multi-User Access, click it. That machine is wrongly acting as a host.
3. If you see Host Multi-User Access, hosting is off there, which is correct. Do not click it.

Verification: exactly one machine offers “Stop Hosting Multi-User Access”. Every other machine offers “Host Multi-User Access”.

The wording is genuinely confusing — the menu shows the action available, not the current state. I have watched competent people turn hosting on across an entire office because the menu appeared to be telling them hosting was off everywhere. Read it as a button, not a status light.

Fix 3: Rescan the folder to rebuild the .ND file

By the end of this step the network descriptor file that points workstations at the host will be regenerated. Every company file has a companion .ND file MyCompany.qbw.ND — that stores which machine hosts it and how to reach it. It is a configuration file, not data; deleting it costs you nothing, because Database Server Manager rebuilds it.

On the server:

1. Open the Start menu, type Database, and open QuickBooks Database Server Manager.
2. Go to the Scan Folders tab.
3. Click Browse, select the folder holding your company files, and click OK.
4. Click Start Scan.
5. When the scan finishes, the folder appears under QuickBooks company files found.
6. Open the Monitored Drives tab and tick the drive that holds those folders.

Verification: the scan results list your .qbw file by name, and the folder now contains a fresh .qbw.ND file with today’s timestamp.

Ticking the drive in Monitored Drives is what stops this from becoming a recurring chore. Once a drive is monitored, moving or renaming company files inside it no longer requires a manual rescan.

If the scan reports the folder but no company files, the service account cannot read the folder — that is Fix 5, not a scanning problem.

Fix 4: Open the firewall ports and program exceptions

By the end of this step Windows Defender Firewall will allow both the QuickBooks ports and the QuickBooks executables through on the server. This is the fix when QuickBooks opens fine on the server itself but every workstation reports the error.

QuickBooks needs both port rules and program exceptions. Doing only one of the two is a common half-fix.

Ports by version

From 2019 onward Intuit moved to dynamic port assignment, so there is no fixed range to memorize. Older releases use a fixed range that differs per year. Either way, do not work from a number you found in a forum post — open QuickBooks Database Server Manager on the server, go to the Port Monitor tab, and read the port your installation is actually using. Intuit’s firewall article lists the per-year values if you want to cross-check.

To create the rules:

1. Open the Start menu, type Windows Firewall, and open Windows Defender Firewall with Advanced Security.
2. Right-click Inbound Rules → New Rule → Port → TCP.
3. Enter your ports in Specific local ports — 8019 plus the port from Port Monitor — then click Next.
4. Select Allow the connection, tick Domain, Private, and Public, and name the rule something you will recognize, such as QBPorts(year).
5. Repeat the whole sequence for Outbound Rules.

Program exceptions

Create a Program rule for each QuickBooks executable, most of which live in C:\Program Files\Intuit\QUICKBOOKS 20XX\:

1. QBDBMgrN.exe — the database service itself
2. QBCFMonitorService.exe — the connection monitor
3. QBW32.exe (QBW.exe on 64-bit releases) — the QuickBooks application
4. QBServerUtilityMgr.exe — the Database Server Manager window
5. DBManagerExe.exe, QBLaunch.exe, QBUpdate.exe, AutoBackupExe.exe, FileManagement.exe, FileMovementExe.exe

Verification: from a workstation command prompt, run ping <servername> and confirm replies, then attempt multi-user login.

Third-party antivirus and endpoint security suites enforce their own firewall independently of Windows. If Windows rules are correct and the error persists, temporarily disable the third-party product’s firewall module and retest. If that fixes it, add the same exceptions there and re-enable it — do not leave it off.

Fix 5: Repair QBDataServiceUserXX permissions

By the end of this step the Windows account that runs the database service will have full access to the company file folder. This is the fix for the specific pattern where the service starts and stops within seconds, and for scans that find the folder but not the files.

The service does not run as you. It runs as a dedicated local account, QBDataServiceUserXX, created during installation. When that account loses read/write access to the shared folder after a drive migration, a permissions cleanup, a domain change, or a restore from backup — the service starts, fails its first file operation, and exits.

On the server:

1. Open File Explorer, right-click the folder containing your company files, and select Properties.
2. Go to the Security tab and click Edit.
3. If QBDataServiceUserXX is not listed, click Add, type the account name, and click Check Names.
4. Select the account and tick Full control under Allow.
5. Click Apply, then OK.
6. Repeat for every folder in the path that contains company files, including any subfolders.
7. Restart the QuickBooksDBXX service.

Verification: the service stays in the “Running” state for more than a minute, and a fresh folder scan in Database Server Manager lists your company files.

Two details worth knowing here. First, if the folder is on a NAS or a non-Windows file server, this local-account approach does not apply. The share permissions on the NAS itself have to grant access instead, and some consumer NAS devices cannot host QuickBooks company files at all. Second, if you have upgraded across several years, grant the permission to the QBDataServiceUserXX account matching the version you are actually running. It is not always the highest number in the list.

Fix 6: Run QuickBooks Tool Hub

By the end of this step Intuit’s own diagnostics will have repaired the network configuration and the installation, if either is the cause. Tool Hub bundles the utilities that used to ship as separate downloads.

1. Download QuickBooks Tool Hub from Intuit’s support site and install it on the server. Version numbers change; always take the current build directly from Intuit rather than a mirror.
2. Open Tool Hub and select Company File Issues → Run QuickBooks File Doctor.
3. Choose your company file, select Check your file and network, and enter the QuickBooks admin password.
4. Let it finish without interrupting it. Run time scales with company file size, so a large file can take a while.
5. If the error persists, return to Tool Hub and run Installation Issues → QuickBooks Install Diagnostic Tool.
6. Restart the server after either tool completes.

Verification: File Doctor reports the network test passed, and multi-user login succeeds from a workstation.

Run Tool Hub after the manual checks above rather than before. File Doctor is good at repairing what it understands: hosting flags, .ND files, service registration. It cannot see a third-party firewall rule or a NAS permission. A clean File Doctor result on a still-broken network is what sends people down the reinstall path unnecessarily.

Fix 7: Repair or reinstall Database Server Manager

By the end of this step the Database Server Manager installation will be rebuilt from scratch. Reserve this for when QuickBooksDBXX does not appear in services.msc at all, or when everything above has been verified and the service still refuses to stay up.

1. On the server, open Control Panel → Programs and Features.
2. Select your QuickBooks version and click Uninstall/Change → Repair. Let it complete and reboot.
3. If the repair does not restore the service, reinstall: back up the company file first, uninstall QuickBooks, then reinstall using the Custom and Network Options installation type.
4. When the installer asks, choose I’ll be using QuickBooks Desktop on this computer, AND I’ll be storing our company file here if the server also runs QuickBooks, or the database-server-only option if it does not.
5. After installation, rescan folders as in Fix 3.

Verification: QuickBooksDBXX appears in services.msc with Startup Type “Automatic” and Status “Running”.

Choosing the wrong installation type is how servers end up without a database service in the first place. The default “Express” install does not configure the machine as a host, so an in-place upgrade done in a hurry can leave a server running QuickBooks perfectly for the person sitting at it while serving nothing to anyone else.

Why it broke right after a Windows update

Windows updates break this in three specific ways, and each one has a different fingerprint.

Service startup type reset. A feature update can leave QuickBooksDBXX set to Manual instead of Automatic. Everything works until the next reboot, then nothing does. Fingerprint: the service starts fine when you start it by hand.

Firewall profile flip. After an update — or after a router or NIC change — Windows can reclassify the network from Private to Public and apply a stricter rule set. Fingerprint: QuickBooks works on the server, fails from every workstation, and the firewall rules look present but are scoped to the wrong profile.

Permission and account changes. Updates that touch the security stack can disturb local account rights, which lands you in Fix 5. Fingerprint: the service starts, then stops within seconds.

Underneath all three is a version question worth answering honestly. Windows 10 reached end of support on October 14, 2025. Microsoft’s consumer Extended Security Updates program is open for enrollment until it ends on October 12, 2027 (Microsoft, retrieved 2026-08-05), and commercial and education customers can buy a maximum of three years of ESU coverage. Either way, ESU delivers security updates only: no new features, no non-security fixes, and no general technical support.

QuickBooks Desktop has a parallel clock. Intuit runs a rolling three-year support window, and QuickBooks Desktop 2023 — including Pro Plus, Premier Plus, Mac Plus, and Enterprise 23.0 — reached end of service on May 31, 2026. Discontinued versions keep opening your file; what stops is payroll, bank feeds, payments, live support, and security updates. If yours has passed that date, the practical choices are upgrading the Desktop version or migrating to QuickBooks Online.

QBDBMgrN vs QBCFMonitorService

Both must run on the server, and their error messages look interchangeable, but they do different jobs. Knowing which one is down tells you where to look.

If QBDBMgrN is running and multi-user still fails, QBCFMonitorService is the next thing to restart. The reverse is not true: starting the monitor service without the database service accomplishes nothing.

How to stop “QuickBooks Database Server Manager not running on this computer” coming back

A fix that survives the next reboot has five properties. Confirm each one before you close the ticket:

1. QuickBooksDBXX and QBCFMonitorService are both set to Automatic with Recovery → Restart the Service on all three failure entries.
2. Hosting is on at exactly one machine, and you have physically checked the File → Utilities menu on each workstation.
3. The drive holding company files is ticked in Monitored Drives, so file moves do not require a rescan.
4. Firewall rules exist inbound and outbound, for both ports and programs, scoped to Domain, Private, and Public.
5. QBDataServiceUserXX has Full control on every folder in the company file path.

Two settings are commonly missing on a network that keeps failing: the Recovery tab settings and the outbound firewall rules. Neither is dramatic. Both convert an intermittent, unexplained outage into a network that simply stays up.

Where to go next

If multi-user is running again, spend ten more minutes on the five durability checks above; that is what keeps the fix. If it is still down, the next place to look depends on what you saw: a service that starts and stops points at permissions, and a server that works locally while every workstation fails points at the firewall.

Frequently Asked Questions