July 15, 2010 at 8:03 am
Before two day’s I have changed Password of my windows domain account.
This same account we use to start SQL server Service with automatically start up option.
But today we restarted this windows server;
and found SQL server service did not started automatically.
I started service by reassigning the account name /password to the SQL server service
So my question is
Is changing password did not affects automatically to start SQL server service?
Regards,
Shivrudra W
July 15, 2010 at 8:28 am
May be a silly question, but did you update the password on the service account when you changed it in Windows? Check the event log to see if the SQL Server service failed to start because of a login failure. Otherwise, no, changing a password has no impact on startup state in the Services control panel.
July 15, 2010 at 9:20 am
yes seems silly question but......
1.did you update the password on the service account when you changed it in Windows?
No. I have changed password by Active directory.
And my question is it necessary to change Password of every server where that account use to start SQL server service
2.Check the event log to see if the SQL Server service failed to start because of a login failure
No I need not found any Login error in event viewer ..otherwise I found below error
At 22.10 I found information message
17147 :
SQL Server terminating because of system shutdown.
after restart (at 22:20)
I found below error
17143 :
SQLServiceControlHandler: Could not set Service Control Status. Operating system error = 6(The handle is invalid.).
3.Otherwise, no, changing a password has no impact on startup state in the Services control panel.
Seriously it is impacted I have manually changed password and restarted service.
Regards,
Shivrudra W
July 15, 2010 at 10:40 am
Ah, but the original question as phrased seemed to ask "Would changing a password change the service startup from automatic to manual?" The answer to that is "No, it won't". But if the REAL question is "Do I have to change the password for all instances of SQL that use that account?" then the answer is an emphatic "Yes". As a result, I recommend that each instance of SQL get its own service account, and maybe even finer grained (i.e. a service account for replication, one for log shipping, etc). That way you have fewer places to hit when you change passwords. But if you did not go into the Services control panel (or in the SS Configuration Manager) and update the password, then the behavior you saw is predictable and expected. I think if you go into the System Event Log in Computer Management you'll have a "Service Control Manager" fail event for MSSQLSERVER that says that there was a login failure.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply