April 17, 2009 at 2:12 pm
I have a weird problem. I have a couple of SQL 2005 and 2008 servers that when I try to cycle the service, SQL or Agent, it comes back saying login failure. So I manually punch in the same credentials in the service property and start the service it works. But later if I decide to cycle the service again it comes back with login failure.
It runs using domain credentials and those credentials are in the Administrators group of the server.
Any ideas?
April 17, 2009 at 2:29 pm
Don't change the login properties using the services applet. Use SQL Server Configuration Manager which will make sure the changes are made to all of the appropriate locations.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
April 17, 2009 at 2:33 pm
Hmm...
I'll try that.
Thanks
April 20, 2009 at 10:10 am
This get's weirder and weirder. I did waht you suggested. I went to the SQL Server Configuration Manager and put in the correct credentials and I hit "Apply" and I get the error message "The service did not start due to logon failure. [0x8007042d]". But if I change the credentials in the services.mmc it restarts.
Any ideas?
Thanks
April 20, 2009 at 10:26 am
Verify the settings on the AD account - make sure the password is not getting reset or the account is not getting locked out.
The account could be getting locked if there are multiple attempts to connect with a bad password.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
April 20, 2009 at 10:28 am
One other thing is that I try to go to the Loacl Security Policy mmc and drill down to "Log on as a service" and the buttons to add or remove are greyed out.
Whats the deal Oatmeal?
Thanks
April 20, 2009 at 10:32 am
The AD account is not getting locked out. I can authenticate with the credentials fine on one server and I can manually retype in the credentails from the services mmc and start the service fine. But in a few days, if I have to cycle the service (this is all testing), it again retirns the login failure message and I have to do it all over again. Ditto if I have to reboot. It looks like for some strange reason that it is losong the "Logon as service" policy. Hell, I can't even change that policy. See previous reply.
April 20, 2009 at 10:39 am
Maybe a group policy for that server is causing the problem?
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
April 20, 2009 at 10:56 am
I'll check with the AD guys...
April 20, 2009 at 11:46 am
Yup, that was it. The servers machine account was in the wrong OU that refreshed the policy. I had the AD guys move it to the correct OU and it should work now. I'll repost if it keeps happening but I think this is the fix.
Thanks!!!
April 20, 2009 at 11:50 am
Thanks for the feedback - I hope that was the problem and that it is now fixed.
Jeffrey Williams
Problems are opportunities brilliantly disguised as insurmountable obstacles.
How to post questions to get better answers faster
Managing Transaction Logs
August 31, 2009 at 7:52 am
Warren,
Did you fix the problem you were having. I am having the same problem right now and i cant seem to fix it. The SQL server is in a different OU but with no policy applied to it. So i am not sure why it is doing that. Your same problems that you had with sql is what i am dealing with right now. Please let me know or if anyone else have any suggestions!!! Thanks
September 1, 2009 at 6:30 am
Try changing to a completely different account (through the configuration manager), apply, and then change it back to the original credentials.
Greg E
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply