Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
We have an issue with Quickbooks Enterprise Solutions 2019 failing to start services on a Windows Server 2016 installation. Issue is most recognized by user trying to open company file and getting an error “This action requires Windows administrator permissions”. Also gave error code (-12, 0) in event viewer.
You would initially think this is related to any number of permission errors, but after debugging I discovered the error is simply caused because the QBCFMonitorService is not running. After reboot it does not start automatically! There are two temporary solutions to this:
1. Quickbooks Database Manager → Start Scan. This will launch the service.
2. Windows Services → Manually start service QBCFMonitorService
All is good … until next restart
My only permanent solution to this is to delay the startup of the DNS service from “Automatic” to “Automatic (Delayed Start)”. Huh, DNS? What does that have to do with it? Previous to this error I had this exact error in 2016 described here:
or
It notes there is a conflict between Windows DNS server ports and Quickbooks. This was written for 2016/2017, however in 2019 Intuit changed to Dynamic ports, so theoretically this should not be an issue. However changing the DNS service to delayed start clearly works: at least 15 times testing both ways.
I tried reserving the ports (both UDP & TCP just to be safe) but no change.
What is going on here? This is a fairly typical install, single server running typical services, DNS, Remote Desktop, Remote Access VNC. Quickbooks support told me change Logon user as “System” and to set the recovery options to restart (unlimited). They say it could be a firewall issue. None of this has helped. It is not a firewall issue – that would not cause the service to not start or crash. I’ve re-installed, clean installed, removed older versions running in parallel, everything.
Only my self discovered DNS server delay startup seems to work and I worry that may not someday if it is a weird race condition. I can’t find any logs pointing to anything useful, nothing in Event Viewer or log files in Intuit directories. No sign of why the service does not start up.
Please help!