September 23, 2021

QuickBooks Database Server Manager is not starting

QUICKBOOKS DATABASE MANAGER (QUICKBOOKSDBXX) SERVICE CONFLICTS WITH DNS SERVER SERVICE 

An issue can happen when QuickBooks Database Manager (QBDM) is installed on a Windows Server that is likewise going about as a DNS server. In short, the issue happens on the grounds that the QuickBooks Database Manager endeavors to utilize a port that is as of now being used by the DNS server administration. At the point when the QBDM administration begins it experiences a contention with the DNS server administration and quickly ends. 

Intuit gives a rundown of conceivable fixes to the issue, yet none of them address the issue of DNS server administration struggle. 

To take care of the port clash issue a framework head must avoid a port (or a scope of ports for past versions of QuickBooks). This model tells the best way to determine this difficult when utilizing QuickBooks Desktop 2020, anyway the standards appeared here can be applied to past versions of QuickBooks also.

PRE-TEST: 

  • Prior to continuing to the “Permanent Fix” step through a second to examine this fast answer to check whether it settles your concern. To pre-test this arrangement essentially: 
  • Stop the DNS server administration 
  • Endeavor to begin the QuickBooksDB30 installation 

In the event that the QuickbooksDB30 administration begins without tossing an error, at that point you will have affirmed that a contention exists between the DNS server administration and the QuickBooks Database Manager administration. Proceeding to the “Perpetual Fix” area underneath after you: 

  • Stop the QuickBooksDB30 administration 
  • Start the DNS Server administration 

In the event that QuickBooksDB30 administration starts and, at that point promptly stops, then extra investigating is required. Start the DNS server administration and afterward consider reaching Help-O-Matic for extra help. 

Significant Note: The means taken in the Pre-Test will be fixed on the following server reboot, so it’s imperative to proceed to the “Perpetual Fix” to guarantee the issue doesn’t repeat.

 

PERMANENT FIX QUICKBOOKS DESKTOP DATABASE MANAGER 2020: 

In the wake of discovering that there is a contention between the DNS server administration and the QuickBooksDB30 administration, find a way to tackle the issue permanently*: 

  1. Open the QuickBooks Database Manager program 
  2. Select the Port Monitor tab 
  3. Note the Port Number adjoining the QuickBooks Database Manager 2020 Version. Trade the prominent port number with the xxxxx in the order beneath. 
  4. Stop the DNS Server administration and the QuickBooks administration 
  5. Hold the prominent port by entering the following at an order brief: 
  6. netsh int ipv4 add excluded portrange protocol=udp startport=xxxxx numberofports=1 
  7. Start the two services 

The issue can be viewed as tackled if the two services start without error.

Answers FOR OTHER VERSIONS OF QUICKBOOKS: 

QUICKBOOKS 2019 

Utilize similar strides similarly as with the answer for QuickBooks 2020, just utilize the port related with the QuickBooks Database Manager 2019 as shows up under the Port Monitor tab. 

QUICKBOOKS 2018 

    • Stop the DNS Server administration and the QuickBooks administration 
    • Hold the prominent port by entering the following at an order brief: 
  • “netsh int ipv4 add excludedportrange protocol=udp startport=55378 numberofports=5”
  • Start the two services 

QUICKBOOKS 2017 

    • Stop the DNS Server administration and the QuickBooks administration 
    • Hold the prominent port by entering the following at an order brief: 
  • “netsh int ipv4 add excludedportrange protocol=udp startport=55373 numberofports=5”
  • Start the two services 

* It should be noticed that beginning with QuickBooks 2019 Intuit transformed it conspire for port necessities. Preceding QB2019 the QuickBooksDBxx administration utilized fixed arrangement of port numbers (for example QuickBooks Desktop 2018 utilizations fixed ports 8019, 56728, 55378-55382). Beginning with QB2019 Intuit decided to utilize “dynamic” ports all things being equal. The means above will function as long as the powerfully doled out port doesn’t change. Since this port is now recognized by Intuit as “Dynamic” it’s conceivable that it might arbitrarily appoint an alternate port number. A port change will make this issue repeat and a director should rehash the means above to determine the issue once more.

 

Leave a Reply

Your email address will not be published. Required fields are marked *