An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation ...
mercoledì 10 ottobre 2007 08:53
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it's password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it's original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We're using SQL2k with SP3a. Thanks!
An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
Tutte le risposte
mercoledì 10 ottobre 2007 09:53Postatore
Assuming there are no external factors like event log messages indicating problems connecting to the domain controller then it sounds like there's an issue with that domain account.
I can only suggest that you try deleting and recreating that account in AD, if you have not tried this already.
I'd also recommend you apply SP4, but that does not have anything to do with this issue.
venerdì 11 gennaio 2008 21:03
I was getting the same error since I had changed the password. I found a work around for it to connect to SQL server.
Go to Run-->services.msc--> MSSQLSERVER . On the "log on as" tab right click and check your login information. i suggest delete the password and retype it again. It works !!
martedì 22 gennaio 2008 12:35
martedì 29 gennaio 2008 20:50
We are having the same type of problem.
For some reason, when rebooting a SQL server, the service will not start. When trying to start by hand, we will get the service did not start due to logon failure message.
Resetting it to the same password, gives the "logon as a service has been granted" message. Then the service will start up correctly. The account is a domain user account and it only used for the SQL service (on this machine and a few others). The problem seems to happen on at least 2 different SQL machines. The password has not been changed lately. This almost seems like when setting the password on the service, it is not being saved properly and when it is rebooted, it is using some other password that may have been cached.
Not sure what is going on, but it is very strange.
martedì 12 febbraio 2008 13:55
Hmmm, just a thought. SQL Server 2000 will be stopping it's support this year. Does that mean if theres a problem with this, we will not be able to resolve this issue anymore?
mercoledì 8 ottobre 2008 13:58
Ran into this error, and the password was correct. What the System Event Log said:
Code SnippetEvent Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7041
Time: 9:33:09 AM
The SQLSERVERAGENT service was unable to log on as DomainName\SQLAgent with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Domain and account: DomainName\SQLAgent
This service account does not have the necessary user right "Log on as a service."
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, a Group Policy object associated with this node might be removing the right. Check with your domain administrator to find out if this is happening.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
...sure enough it had been removed from the "Logon as a service" list. Hope this helps.
- Proposto come risposta Rashid Amin lunedì 16 luglio 2012 18:23
sabato 26 marzo 2011 15:22
I have the same error but its related to a brand new installed sql server 2000 SP4 but instead of SQLSERVERAGENT is SQLSERVER.
Any ideas ?
Sorry about my poor English.
giovedì 7 aprile 2011 07:13Thanks Anidutta..your post helped me..:)
giovedì 28 aprile 2011 20:04Thanks Anidutta..your post helped me too!!!!!
giovedì 14 luglio 2011 17:58Solved it for me. Thanks.
mercoledì 31 agosto 2011 17:19Thanks very much!! this resolved my problem. I too had changed my password. and the error with connecting to SQL occured a few days later. I was unable to connect to it. thanks again!
giovedì 8 settembre 2011 08:27
Thanks anidutta, it help me a lot and now work perfectly.
lunedì 17 ottobre 2011 11:00IT Works :)
giovedì 1 dicembre 2011 11:26
I think Rock explains this well here.
This fixed my issue.
mercoledì 1 febbraio 2012 20:03Thanks anidutta, it works in sql 2008 too.
domenica 4 marzo 2012 19:07think you !!
- Modificato cana01 domenica 4 marzo 2012 19:07
sabato 28 aprile 2012 11:33
my probelm get solved this suggestion realy help who face the same problem.
lunedì 16 luglio 2012 18:24This fixed my issue. There was an explicit "Logon as service" GPO assigned to a certain group. I added Domain Admins to that group.