His posts typically reflect real situations that required real solutions. Many of these solutions are compiled from several other blogs or just personal experience and put into a easy to follow process.
QuickBooks database server will not start - SQLANY 17.0 cannot be found
Issues with the QuickBooks database server used to be a fairly rare occurrence. But since 2019, many of the servers running QuickBooks have been updated to new versions of the Windows Server OS and the QuickBooksDB##. The end user will typically get the following error when attempting to connect to the server in a multiuser setting.
"Error Code: H202 This company file is on another computer, and QuickBooks needs some help connecting. Quickbooks server manager service on the Windows server is not running."
When you run the QuickBooks Database Server Manager, and click Start Scan, it scans the folders, then get an error:
"Quickbooks network diagnostics failed. Resolve errors and retry. This is because the QuickBooksDB## system service is unable to start."
If you try to start the QuickBooksDB26 system service, it starts and then immediately stops, giving the message,
"The QuickBooksDB## service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
In the Application log on the server you will likely find the error:
"The description for Event ID 1 from source SQLANY 17.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."
This error is inaccurate. The issue is with the QuickBooksDB## server service using the same port number as the DNS Server service. This is why you don't see this in smaller environments where the QuickBooks database server is a Windows workstation, it typically is not running the DNS Server service.
There are a couple of options to resolving this issue temporarily.
1. Rebooting the computer hosting the QuickBooks database is the easiest method for most endusers.
2. Stoping the DNS server service, then starting the QuickBooksDB## service and the QBMonitoring service, and then restarting the DNS Server service can be done if you don't want to reboot the server.
A more permanent solution to resolve the issue is to reserve the port.
a. Stop the DNS Server service, and the QuickBooksDB## service.
b. Reserve the port using netsh from the command prompt
c. netsh int ipv4 add excludedportrange protocol=udp startport=55368 numberofports=5
d. then start both services