Monday, June 9, 2014

Timer service terminated with service-specific error or Timer service terminated unexpectedly in share point



Timer service terminated with service-specific error  or Timer service terminated unexpectedly in share point

This is an issue that face every SharePoint administrator many times in their experience. This could be of many reasons. In this article I am providing the reason that cause the issue as per my experience.

Due to the issue with the timer service we see the other parts like Alerts, Backups, Search and UPS also stops working

When I tried to retract a solution, but the status showing "Retracting" only for long time. After digging in events, I figure out that the issue is with the SharePoint Timer service on one of the servers crashed every couple of minutes. The event log showed the following errors.

Events:
Log Name: System
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Server name]
Description:
The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259.
and
Log Name: System
Source: Service Control Manager
Event ID: 7031
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [Server name]
Description:
The SharePoint 2010 Timer service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service.

Solution: Ensure to follow the below steps to resolve the issue

·         Open the Registry Editor
·         Browse to HKLM > SOFTWARE > Microsoft > Shared Tools > Web Server Extensions > 14.0 > Secure > ConfigDB(For SharePoint 2013,Its 15.0)
·         Copy the value in the property "Id" 

                     
·         Browse to folder C:\ProgramData\Microsoft\SharePoint\Config and create a folder with the name of the previously copied value 

                          

·         Restart the SharePoint Timer service
·         The folder should be populated with XML files after restart
 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

6 comments:

  1. Thanks !! Your resolution helped me to solve my wsp deployment issue

    ReplyDelete
  2. Great articles dude

    ReplyDelete
  3. This works for me like saver

    ReplyDelete
  4. It we need to restart serve after changes

    ReplyDelete
  5. It resolves the issue after registry changes

    ReplyDelete
  6. Hi! I have the same issue. But I followed the above steps and found out that the folder already exists. Inside it, I found many log files. Is there any other solution?

    ReplyDelete

Your feedback is Much Appreciated. I will try to reply to your queries as soon as possible!!Anil Avula

ShareThis

X