Sometimes some behaviors in SQL Server are unexpected and that’s the right time when an expert need to be engaged. In this blog post we will learn about how automatic startup sometimes does not work in SQL Server Services.
One of my client told that they had a business down situation for few hours. Based on their findings they realized that there was a restart of SQL Server machine due to power failure. They are OK with that, but their expectation was that SQL Service should have automatically started after machine reboot which didn’t happen. I asked to share the screenshot of SQL Server Configuration Manager.
By looking at the screenshot it’s clear that they have already configured “Start Mode” of SQL Service for Automatic. Which means their expectation was correct.
Next, we looked into Event Logs to see any interesting information. We found Event ID 5719 via source NETLOGON.
Log Name: System
Event ID: 5719
The MSSQLSERVER service was unable to log on as FORTUNE\SQLSvc with the currently configured password due to the following error: There are currently no logon servers available to service the logon request. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC)
It was not very difficult to search below knowledge base article from Microsoft which explained the cause of such message. https://support.microsoft.com/en-in/help/139410/err-msg-there-are-currently-no-logon-servers-available
Based on the error messages we can conclude that in this scenario the SQL Service didn’t start automatically because SQL Server was unable to communicate to domain controller (DC). When I checked with client about above and asked about network connectivity to DC, they replied – “Unfortunately, domain controller was also rebooted due to power failure”.
Reference: Pinal Dave (https://blog.sqlauthority.com)