All SQL services stopped with 'Logon Failure'
Posted on 2015-01-19
We have 3 SQL 2012 instances installed on a Hyper-V guest running Server 2012 Datacenter. This server has been in operation for about a month.
This morning when I came in, the 9 services relating to these 3 SQL instances had all stopped, and if I attempted to restart, I got a dialog saying that the service could not be started because of a logon failure.
I suspect that the logon accounts ('NT Service\MCAFEE' being one example) have expired passwords.
I have changed each of the services to logon with the Local System Account, and they have now all started.
That being said, HOW and/or WHERE do I check the password policy for NT Service accounts so that I can make sure that they do not expire (assuming that is indeed the problem)? These accounts were created by the application installers themselves.