Quickbooks Pro 2017 database service on Domain Controller fails to start, no access to hosted Quickbooks data files
Posted by rbTech Staff, Last modified by rbTech Staff on 10 May 2017 09:33 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


Windows 2012r2 Domain Controller, Quickbooks 2017 database manager running on DC


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 below 49147 (we use 49140).To test, leave the DNS server service running, and restart the QB database


Adjust the service parameters in c:\ProgramData\Quicbooks\QBGLOBALAPPCONFIG.ini from 55333 to 49140, to get the binding out of the range of the Microsoft dynamically assigned high port range of 49152-65535 (The lowest of which are often assigned to the DNS server service because it starts first).

Sources/ Credits:

(21 vote(s))
Not helpful

Comments (9)
Dee Payton
20 July 2017 06:08 PM
Adjust the service parameters in c:\ProgramData\Quicbooks\QBGLOBALAPPCONFIG.ini from 55333 to 49140, to get the binding out of the range of the Microsoft dynamically assigned high port range of 49152-65535 (The lowest of which are often assigned to the DNS server service because it starts first).

Worked for me.....Thank you!
Jeff Breeze
13 February 2018 09:17 AM
Thank you so much for this write up... I installed the database server on a domain controller that was indeed a DNS server. None of the previous versions of database server had issue (QB 2009 & QB2013), but Quickbooks 2018 definitely did exactly this. I reset the port in the INI file & rebooted (my INI file was in \ProgramData\Intuit\Quickbooks\QBGLOBALAPPCONFIG.ini) and it came back to life. Thank you, thank you, thank you!!!!
14 February 2018 10:35 AM
Thank you so much for your answer, this prevent a long day of stress and blaming AV solutions and Windows Updates!

10 April 2018 11:48 AM
Thank you! I have been banging my head against the wall with this problem for awhile. I did the same procedure as Dee Payton above and now Quickbooks works! I did go through and manually add inbound and outbound rules for the port I opened up (49140 in this case).
04 October 2018 10:00 AM
Thank you for the write up. I verified 55333 was in use by opening a command prompt and typing 'netstat -an' (without the quotes). This allowed me to see that the port was in use without having to stop the DNS Server service.

My server is 2008R2. Note that the path is different that indicated in the article for me. On my server, the path is C:\ProgramData\Intuit\Quicbooks\QBGLOBALAPPCONFIG.ini

I used 'netstat -an' to verify port 49140 was not already in use. It wasn't; therefore, I made the recommended change. This resolved our issue.
Thank you
17 October 2018 11:46 AM
Amazing! Quickbooks and their quest for world domination. Forget about other established best practices, lets just choose a port. Any port.
Thank you so much for this discovery. Would never have found the solution otherwise - would never have thought that any reputable company would deliberately configure their software that way.
Victor Stellan
04 January 2019 02:28 PM
Amazing! After 3 days of dealing with Quickbooks support and getting nowhere (and having the service agent nearly hose my server in the process), this article got us going in 15 minutes. Makes me wonder why I pay the annual maintenance contract. The funny (not ha-ha funny, but rather tragic funny) part about it is we've had this coexisting condition since we started with Quickbooks 2008 and never had a problem with it until the latest version. Thank you so much for sharing your knowledge. We can finally get back to work!
Antonio Calvino
16 January 2019 01:54 PM
I have looked for an answer for quite a while Thank you! This worked fine with my 2018 QB version.
Chris D
04 February 2019 10:57 PM
This also clearly worked in QB 2016 for me, but I don't completely understand why. DNS uses UDP and QuickBooks uses TCP. TCP and UDP ports are completely independent (even on the same port number). Can anyone explain?

Quickbooks 2019 went to "Dynamic Ports" aka static ports that's configured on installation. For whatever reason this does not appear to work anymore for me in QB2019. It may be I have a second issue, but it is still clearly related to an incompatibility with DNS server. More info on my QB support ticket:

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).