Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, July 20, 2011 6:26 PM
Hello everyone,
SharePoint Timer Service on my SharePoint Web Server stops by itself every couple of days or so. Trying to restart it gives me the following error:
Windows could not start the SharePoint 2010 Timer service on Local Computer.
Error 1069: The service did not start due to a logon failure.
I am able to start it after retyping the SP Service Account password. SP Service Account has Administrative rights to the machine. There are other services with the same logon, Web Analytics Service being one of them, that don't display the same behaviour.
I am not sure if this is an Active Directory issue.
Has anyone experienced this condition?
Regards,
MichaelSaroyan
All replies (19)
Wednesday, July 20, 2011 7:39 PM âś…Answered | 2 votes
Could it be a group policy that is applied and maybe is restricting the accounts rights? Check security log for any failed login when the service stops.Regards
Henrik A. Halmstrand
http:/www.sharepointrevealed.com
http://getspconfig.codeplex.com
Wednesday, July 20, 2011 6:32 PM
Hi,
Verify that the service account you are using is not disabled and that password hasn't expired.
Regards
Henrik A. Halmstrand
http:/www.sharepointrevealed.com
http://getspconfig.codeplex.com
Wednesday, July 20, 2011 7:06 PM
Hi Henrik, the account and password are fine. After reentering the password, the service starts fine. It runs for a day or two and it stops again. The service account is used by other services which are fine.
MichaelSaroyan
Tuesday, January 3, 2012 4:53 AM
Hi,
Even I am having the same issue. but when I checked in the group policy the account has rights for "logon as a service" and this account is local administrator.. But still this issue is occuring again..
Is there any other things that I need to check..
Tuesday, January 3, 2012 8:37 AM
Hi Mike,
It seems that this account is not properly updated for Sharepoint environment. Run the below mentioned command and monitor further if you are still facing the same issue or not.
stsadm -o upgradefarmcredentials -userlogin <userid> -password <password>
followed by IISRESET
Hope this helps.
Wednesday, January 4, 2012 7:19 AM
Dear Sumit,
I tried this command stsadm -o upgradefarmcredentials -userlogin <userid> -password <password>
But no use if I restart the server the sharepoint timer service stops and when I try to start it, that service fails to start due to logon failure..
Thursday, January 5, 2012 6:04 AM | 1 vote
Hi,
My apologies as I mentioned wrong command. It is updatefarmcredentials but not upgrade. And even if it is not working, try to run Configuration wizard and see if the sites are running or not.
Thanks, Sumit Gupta SharePoint Consultant MCP, MCTS, CCNA
Sunday, January 8, 2012 11:14 AM
Sites are running fine, But I don't why the sharepoint timer service is stopping all of a sudden.. The account has administrator privileges and Logon as a service permission.. I also checked event log but there is nothing related to SharePoint timer.. I don't know how track and solve this issue..
Monday, July 16, 2012 2:59 PM | 1 vote
Hi
Please follow below steps
Verify that the user account that is performing this procedure is a member of the Administrators group on the local computer.
Click Start, click Administrative Tools, and then click Services.
In the Services snap-in, right-click the Windows SharePoint Services Timer V4 service, and then click Properties.
In the Service Properties dialog box, on the Log On tab, type the password for the account, confirm the password, and then click OK.
Right-click the service, and then click Start.
Follow below URL for more clarification.
http://technet.microsoft.com/en-us/library/ff182790
Regards,
Ajit Shinde
Monday, July 16, 2012 4:42 PM
Try to the password with updatefarmcredentials ( run this on each server using -local)
Last options:
try to update the password manually and check if any other services are using the account and with wrong password.
can you check if the account locked out in AD?
Try this,
Update the password manually and then check AD , if account is not locked out and still timer service not running, please paste the ULS logs here, if account is locked then please check the other services that this account is running under and change the password.
(Some times restarting netlogon service will solve this issue)
Saturday, March 2, 2013 5:45 PM
Hello Mike,
Do you use Managed Service Account in SharePoint? If yes this is the issue and I resolved it by doing the following:
Go to Central Administration, Security, Managed Accounts
Click the farm account (that is the same as your timer service is running on) then Edit, Check Change Password Now and use existing password to change it in the configuration.
Regards, Alex Zoutenbier
Wednesday, January 22, 2014 1:33 AM | 1 vote
The best way to resolve this is to
1. Go to "Services"
2. Go to service properties
3. Select "Logon" tab
4. In user account, RE-Browse the account and enter the password.
5. HIT Start the service.
This should resolve the issue.
SharePoint 2007 (Administration/Development) | Web developer and .NET DTS Programmer | .NET Framework 2.0/3.5 | SQL Server 2008/2005/2k
Monday, March 30, 2015 7:50 AM
All the possible scenarios and resolutions explained in this article. Hope it helps anyone looking for resolution
http://adicodes.com/sharepoint-timer-service-not-starting-up/
Regards,
Adi
Friday, September 4, 2015 1:48 PM
MichaelSaroyan,
Have you checked LogOn tab in Service Properties? If this account option is used you may want to check if the account that is running service is not disabled/locked out/deleted.
Friday, August 26, 2016 12:24 AM
This did the trick for me!
It was set to use a specific account, and I simply checked the 'use Local System Account' and the service starts now.
Thursday, January 25, 2018 9:02 AM
followed the step, then the logon issue has solved. thanks.
Thursday, May 9, 2019 7:07 PM
We tried all these Technics, but none worked. also worked with MSFT for 5 weeks and couldn't find any results.
Tried a new Technic and it worked magically. Documentation in the below link.
https://venugopalareddy.blogspot.com/2019/04/spt2010.html
Thursday, May 9, 2019 7:08 PM
We tried all these Technics, but none worked. also worked with MSFT for 5 weeks and couldn't find any results.
Tried a new Technic and it worked magically. Documentation in the below link.
https://venugopalareddy.blogspot.com/2019/04/spt2010.html
Thursday, May 9, 2019 7:08 PM
We tried all these Technics, but none worked. also worked with MSFT for 5 weeks and couldn't find any results.
Tried a new Technic and it worked magically. Documentation in the below link.