April 15, 2008 at 8:15 am
Our production SQL Server 2000 Sp4(OS Windows 2003 SP2) was rebooted this weekend. None of the instances on the server restarted nor the sql agent eventhough all of them have the AutoStart SQL Server and Auto Start SQL Server Agent options checked.:w00t:
The event log showed errors for each instance service account used to start the services. The error is "The MSSQL$InstanceName service was unable to log on as ServiceAccountUsed with the currently configures password due to the following error: There as 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)."
Services were restarted manually without any changes to their password. There are being running fine since then.
Has anyone experience this behavior? Any suggestion to fix this problem Thanks !!
October 30, 2010 at 3:24 pm
Yes, I've recently had this, and its very annoying, I've put a powershell script that doesn't fix the issue but is a good work around.
Basically, it iterates through all the auto start services and starts them, it also had an "ignore" list.
http://01792.org/blog/post/2010/09/27/Autostarting-services-that-just-done28099t-start.aspx
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply