Today, I was contacted by a customer regarding the Intuit QuickBooks 2016 Database Server Manager running on their Windows Server 2012. Since May of 2016, they have been able to start or restart their QuickBooks Database Server Manager without issue. As of a day ago, QuickBooks Database Server Manager would not start. The error logged in the Event Viewer was SQLANY Event ID 1, SQLANY 16.0 cannot be found. This would lead one to believe the QuickBooks Database Server Manager needed to be reinstalled on the Server. This was not the resolution to the issue. A page on the QuickBooks Community website indicated the latest update for QuickBooks needed to be manually installed on the Server. This was also not the resolution to the issue. I was able to isolate the cause of the issue when I read on a third-party website that if you stop the Windows DNS Server Service and then try starting the QuickBooks Database Server Manager, you may find the QuickBooks Database Server Manager starts without issue. I did as instructed and it did start without issue. This would lead one to believe the problem is a port conflict between the port being assigned to the QuickBooks Database Server Manager Service (QuickBooksDB26) and the Windows DNS Server Service. This was not the cause of the issue.
The issue was resolved by Intuit QuickBooks Technical Support instructing me to change the QuickBooks Database Server Manager Service (QuickBooksDB26) from logging on as QuickBooksDB26 to Local Account and Allow Service to Interact with Desktop.
So in effect, I was told by Intuit to change the LogOn settings of the Windows Service designed by Intuit from the default Intuit setting to a custom setting. First, I am perplexed as to why this issue arose out of nowhere when there have been no changes to the Server. Second, I find it odd that if this is a known issue by Intuit wouldn't the installer have set the LogOn to Local Account upon installation. Third, what is the purpose of the installer creating QuickBooksDB26 if it is now not utilized by the Service?
The issue was resolved by Intuit QuickBooks Technical Support instructing me to change the QuickBooks Database Server Manager Service (QuickBooksDB26) from logging on as QuickBooksDB26 to Local Account and Allow Service to Interact with Desktop.
So in effect, I was told by Intuit to change the LogOn settings of the Windows Service designed by Intuit from the default Intuit setting to a custom setting. First, I am perplexed as to why this issue arose out of nowhere when there have been no changes to the Server. Second, I find it odd that if this is a known issue by Intuit wouldn't the installer have set the LogOn to Local Account upon installation. Third, what is the purpose of the installer creating QuickBooksDB26 if it is now not utilized by the Service?
Comments
Post a Comment