Knowledgebase:
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 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.

Problem:

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

Setup:

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

Symptoms:

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:

QuickBooksDB27
Could not start server

Diagnostics:

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.

Discussion:

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

Resolution:

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:

[1] https://community.intuit.com/questions/1299745-how-do-i-force-quickbooks-database-server-manager-quickbooksdb26-to-use-a-particular-network-configuration
(3 vote(s))
Helpful
Not helpful

Comments (1)
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!
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).