March 9, 2010 at 8:40 am
I set up a local instance of SQL2008 and went with the default setting of Windows Authentication mode. I used my NetworkDomain\Username combination for the windows account during setup.
Everything was working great for a month or so... then, yesterday, our network security policy forced me to change my windows password (as it does every 30 days or so)... Shortly after password change, I try to log into my local SQL (thru management studio) like usual, and I can't get in. I am locked out. It seems to me that SQL should not be storing my old password anywhere, but it must be. I have no other explaination for this sudden breakdown.
Can someone please tell me how I can fix this? Or how to do one or more of the following:
1. change my sql windows authentication password without being able to log in?
2. change to sql mixed mode (so I can use 'SA') without being able to log in?
3. delete this instance without being able to log in?
I'm stuck. Any help is appreciated.
March 9, 2010 at 9:07 am
I am assuming you have a local instance of SQL Server 2008 running on your workstation.
Open the SQL Server Configuration Manager. Click on the SQL Server 2008 Services. Right click on SQL Server and select properties from the pop-up menu. Change the password for your account there (as it sounds like the instance is running under your domain account) and restart SQL Server.
This should (no promises, my local instance is running under LocalSystem) fix your problem.
March 9, 2010 at 9:17 am
I agree with Lynn, I think you have used your own domain account as the account running the SQL Service.
As Lynn said chaning the password in Configuration Manager and restarting SQL Server should solve that issue...Until the next time you are forced to change you domain account password.
Gethyn Elliswww.gethynellis.com
March 9, 2010 at 9:18 am
You should never run the Service as a human account, create a non-human account for all Service accounts.
Are you stating that you cannot log into SQL? Or that SQL is not started? I am confused about this as well.
Andrew SQLDBA
March 9, 2010 at 9:19 am
It worked Lynn! Thank you. I guess I'm a little suprised that since I'm logged in to my computer with the same userid, that SQL Server Windows Authentication wouldn't just get a token or something from Windows...
But hey at least its fixed. Thanks again.
March 9, 2010 at 10:00 am
tom parks (3/9/2010)
It worked Lynn! Thank you. I guess I'm a little suprised that since I'm logged in to my computer with the same userid, that SQL Server Windows Authentication wouldn't just get a token or something from Windows...But hey at least its fixed. Thanks again.
Need to remember that SQL Server is running as a service. This means it needs to store the password so that it can log in even if you aren't.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply