Quickbooks Pro 2017 database service on Domain Controller fails to start, no access to hosted Quickbooks data files
Posted by Rubin Bennett, Last modified by Rubin Bennett on 13 April 2017 10:26 AM
A weird one, because it had been working for a long time, then stopped after a (Microsoft Update) patch and reboot cycle.


Financial users unable to access Quickbooks.  QB data files hosted on the Domain Controller, using the Quickbooks database service


Database service wont' start, and network diagnostics from the Quickbooks Database server manager GUI fail.  The following event is recorded in the Application log:
The description for Event ID 1 from source SQLANY 16.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Could not start server


QBCFMonitorService running, but QuickBooksDB27 service is not, and won't start (or immediately stops after start).

Network Diagnostics and repair in the QB database manager GUI fail.


It turns out that the Microsoft DNS service and the QB database service both want to use port 55333. DNS always starts first on a DC, so then the QB service can't bind to the port it wants, and fails out. (Good job, Intuit...).The test case to see if this is the issue is to stop the DNS Server service on the DC, and start the QB database service. If it starts then you've found the issue. DONT FORGET to restart the DNS server service or you'll have very unhappy users! You can permanently fix this by changing the startup parameter in c:\ProgramData\Quicbooks\QBGLOBALAPPCONFIG.ini to a port that is below the DNS server, recommended to be 49147.To test, leave the DNS server service running, and restart teh QB database


Adjust the service parameters in c:\ProgramData\Quicbooks\QBGLOBALAPPCONFIG.ini from 55333 to 49152, to get the binding out of the range of the Microsoft DNS server service.

Sources/ Credits:

(0 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).