none
Timer service keeps terminating unexpectedly

    Question

  • I got excetion while trying to configure project server 2010 over sharepoint server 2010 +TFS 2010 installed system.

    Here is the event logs;

    "The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259 . "

    "The SharePoint 2010 Timer service terminated unexpectedly.  It has done this 257 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service. "

    Timer service keeps restarting, how can I diagnose the problem?
    Monday, June 07, 2010 9:18 PM

Answers

  • I've solve this after including account into local admin group. But! this problem happen when i'm change Network service account to local one created espesially for this service.
    Wednesday, July 14, 2010 9:46 AM
  • For anyone else having this issue. The solution is to give access for the user the timer service is running under to the following SP directory. The Admin group has the rights required which is why the issue is resolved for those people who put the account in the machine's admin group which is a bad practice. Ensure the user has the correct permissions on the following SP directory, and see the error go away.

    C:\ProgramData\Microsoft\SharePoint\Config

    • Proposed as answer by jrush Tuesday, February 14, 2012 7:37 PM
    • Marked as answer by Margriet BruggemanMVP Friday, April 20, 2012 9:23 AM
    Tuesday, February 14, 2012 7:36 PM

All replies

  • I got excetion while trying to configure project server 2010 over sharepoint server 2010 +TFS 2010 installed system.

    Here is the event logs;

    "The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259 . "

    "The SharePoint 2010 Timer service terminated unexpectedly.  It has done this 257 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service. "

    Timer service keeps restarting, how can I diagnose the problem?


    I too am having this issue.. did you ever find a resolution.

     

     

    Friday, June 25, 2010 3:30 PM
  • You may want to look into the ULS log to see if there's anything related. Event log cannot provide enough valuable information for troubleshooting.

    Saturday, June 26, 2010 2:37 AM
  • We are having the similar issue in our SharePoint 2010 installation. The Timer service crashes and restarts every minute. All timer jobs are in the succeeded state. There is nothing related in the ULS logs. Any ideas where to dig further?

    In the system log we have:

    Log Name:      System

     

    Source:        Service Control Manager

    Date:          2.7.2010 12:14:09

    Event ID:      7031

    Task Category: None

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      XXXXX

    Description:

    The SharePoint 2010 Timer service terminated unexpectedly.  It has done this 2997 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

        <EventID Qualifiers="49152">7031</EventID>

        <Version>0</Version>

        <Level>2</Level>

        <Task>0</Task>

        <Opcode>0</Opcode>

        <Keywords>0x8080000000000000</Keywords>

        <TimeCreated SystemTime="2010-07-02T09:14:09.588916700Z" />

        <EventRecordID>80371</EventRecordID>

        <Correlation />

        <Execution ProcessID="528" ThreadID="8344" />

        <Channel>System</Channel>

        <Computer>XXXX</Computer>

        <Security />

      </System>

      <EventData>

        <Data Name="param1">SharePoint 2010 Timer</Data>

        <Data Name="param2">2997</Data>

        <Data Name="param3">30000</Data>

        <Data Name="param4">1</Data>

        <Data Name="param5">Restart the service</Data>

      </EventData>

    </Event>

     

     

    In the Application log we get this:

     

     

    Log Name:      Application

    Source:        Windows Error Reporting

    Date:          2.7.2010 12:14:09

    Event ID:      1001

    Task Category: None

    Level:         Information

    Keywords:      Classic

    User:          N/A

    Computer:      XXXXX

    Description:

    Fault bucket , type 0

    Event Name: CLR20r3

    Response: Not available

    Cab Id: 0


    Problem signature:

    P1: owstimer.exe

    P2: 14.0.4762.1000

    P3: 4bad920c

    P4: mscorlib

    P5: 2.0.0.0

    P6: 4a27471d

    P7: 420f

    P8: 51

    P9: DI4EQZGVCWKDLTHKQTZWPXE3YRFKN1I2

    P10: 


    Attached files:


    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_owstimer.exe_fda9bf6949e3e6d45ca9c0fddc792b95461d3e8_162a8895


    Analysis symbol: 

    Rechecking for solution: 0

    Report Id: 2b6dfba4-85ba-11df-b03f-00155d002008

    Report Status: 4

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Windows Error Reporting" />

        <EventID Qualifiers="0">1001</EventID>

        <Level>4</Level>

        <Task>0</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2010-07-02T09:14:09.000000000Z" />

        <EventRecordID>52437</EventRecordID>

        <Channel>Application</Channel>

        <Computer>XXXXX</Computer>

        <Security />

      </System>

      <EventData>

        <Data>

        </Data>

        <Data>0</Data>

        <Data>CLR20r3</Data>

        <Data>Not available</Data>

        <Data>0</Data>

        <Data>owstimer.exe</Data>

        <Data>14.0.4762.1000</Data>

        <Data>4bad920c</Data>

        <Data>mscorlib</Data>

        <Data>2.0.0.0</Data>

        <Data>4a27471d</Data>

        <Data>420f</Data>

        <Data>51</Data>

        <Data>DI4EQZGVCWKDLTHKQTZWPXE3YRFKN1I2</Data>

        <Data>

        </Data>

        <Data>

        </Data>

        <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_owstimer.exe_fda9bf6949e3e6d45ca9c0fddc792b95461d3e8_162a8895</Data>

        <Data>

        </Data>

        <Data>0</Data>

        <Data>2b6dfba4-85ba-11df-b03f-00155d002008</Data>

        <Data>4</Data>

      </EventData>

    </Event>

     

    Friday, July 02, 2010 9:42 AM
  • Any one find the problem with this?  I'm running into the same thing.
    Monday, July 12, 2010 7:42 PM
  • I've solve this after including account into local admin group. But! this problem happen when i'm change Network service account to local one created espesially for this service.
    Wednesday, July 14, 2010 9:46 AM
  • Making the server account a local admin works for me but is that recommended?

    Wednesday, August 04, 2010 9:00 AM
  • I ended up making the SharePoint Timer Service Account a member of Local Admins.
    Wednesday, August 18, 2010 7:41 PM
  • I have the same problem and Sharepoint Timer Service account is member of the Local Admin group.

    Another strange thing is when I want to restart this service; it says that the password isn't correct anymore.  I have to re-enter the password again and then I can restart the service again.

    Wednesday, October 06, 2010 3:09 PM
  • Making the service account a local admin worked for me too, but is it prudent?
    North to the Future
    Thursday, October 07, 2010 11:30 PM
  • This occurred for me because I had renamed one of the accounts sharepoint was using.  I renamed the account back and restarted SP Services and all was ok.

    This was the log entry that tipped me off:

    BCWCK62-20101103-1008.log:11/03/2010 10:24:13.81  w3wp.exe (0x1224)                        0x10F0 SharePoint Foundation          Configuration                  a16e High     SPAce PrincipalName found domain\oldname account renamed to domain\newname. Using new name. 72af02d0-8296-4ece-b6af-18965dc4ce19

    I was NOT using the account but it WAS setup as a managed account.  This might be a gotcha.

    -Mark

    Wednesday, November 03, 2010 5:33 PM
  • I have this problem, without solutions.

    My Timer Services Stop and at restart it says the password is incorrect. 

    My account is local admin, domain admin, farm admin, ____ admin, but dont work.

    if set a network service account or local account works, but this users dont have a permissions in my domain for exemple create a backup.

     

    Any help is good! :-)

     

    tks


    =================================== Marcelo Fernandes Pimenta Sharepoint´s Severino Belo Horizonte - MG
    Thursday, November 04, 2010 1:11 PM
  • Hi, I'm facing the same problem. My service account is already local admin, I have also launched the configuration wizard ... but it's been 4 days that I have the problem. It happens the first time by night at 4am... So it's not a manual action that create the behavior. still looking...
    AJ
    Wednesday, February 16, 2011 8:54 AM
  • I also get the error message that ArttuA described above. Even after installing the february 2011 cumulative update the errors remained in the event log. Because of this error we have big troubles with several workflows in our portal, because workflow status is dismissed.

    Anyone else solved this error?

    Thanks!

    Monday, March 14, 2011 8:21 AM
  • What is in the ULS log of that server?

    You can find it here: \Program Files\Common Files\Microsoft Shared\web server extensions\14\LOGS

    I recommend using this: http://ulsviewer.codeplex.com/ to make it a little easier to find the issue.

     


    Wednesday, June 29, 2011 3:26 AM
  • I was having the same issue, along with problems accessing the User Profile Service and the Manage Service Applications pages from Central Administration.  Our problem was a deleted user from Active Directory.  The user ID was listed in the ULS logs next to the OWSTIMER.EXE failure messages.  Adding the user back to AD solved the problem (we thought this wouldn't work, as the new user would have a new SID, but apparently it is tied to the login name, not SID).

    The ULS error log started with: SPAce PrincipalName domain\user cannot be resolved.

    The other SharePoint error messages we received were in Central Admin, and were mostly "The specified user or domain group was not found."
    For these messages, this post contains a lot of information:
    http://architectevangelist.wordpress.com/2010/12/07/sharepoint-2010-the-specified-user-or-domain-group-was-not-found/

     

    Friday, July 15, 2011 8:00 PM
  • For anyone else having this issue. The solution is to give access for the user the timer service is running under to the following SP directory. The Admin group has the rights required which is why the issue is resolved for those people who put the account in the machine's admin group which is a bad practice. Ensure the user has the correct permissions on the following SP directory, and see the error go away.

    C:\ProgramData\Microsoft\SharePoint\Config

    • Proposed as answer by jrush Tuesday, February 14, 2012 7:37 PM
    • Marked as answer by Margriet BruggemanMVP Friday, April 20, 2012 9:23 AM
    Tuesday, February 14, 2012 7:36 PM
  • We are having the same issue. The account that the Timer Service is running under is already an admin (despite it not being the best practice) and the error is still happening every minute. The AD user account is active and unlocked. I have logged in using the service account and was able to navigate to the C:\ProgramData\Microsoft\SharePoint\Config folder and open files. What else could be causing this error? 


    Friday, March 09, 2012 7:41 PM
  • If you are using an OS with UAC, turn that off. Check your OS event logs and SP logs for any errors. An admin user would probably not be able to create files in that directory if the user was not is the required groups with UAC active. You need to make sure that the user can create folders & files in that location, and even having the user as an admin may not solve the security requirements.
    Friday, March 09, 2012 9:03 PM
  • Hi all,

    We had encountered similar problem as reported above  however the timer service used to restart every 30 seconds, load and run all the scheduled jobs and crash again with error as below,

    Faulting application name: OWSTIMER.EXE, version: 14.0.6106.5001, time stamp: 0x4df9b75e
    Faulting module name: KERNELBASE.dll, version: 6.1.7601.17625, time stamp: 0x4de88429
    Exception code: 0xe0434f4d
    Fault offset: 0x000000000000cacd
    Faulting process id: 0xeec
    Faulting application start time: 0x01cd4ea759b70a11
    Faulting application path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\OWSTIMER.EXE
    Faulting module path: C:\Windows\system32\KERNELBASE.dll

    In our case none of the solutions suggested above really helped us since

    1. There were no failed Backup/restore jobs
    2. No issue with the permission to the timer service account to C:\ProgramData\Microsoft\SharePoint\Config
    3. DCOM error was also not applicable
    4. No expired password issue
    5. No meaningful information logged anywhere (neither ULS - even after enabling verbose for timer - nor Event viewer except above)

    On careful analysis of the timer job history we found that, there was one job that did not run since we started seeing this problem which was 'job-timer-recycle' and after running this job the issue got resolved for us.

    Do check more about this job here

    -V

    Friday, June 22, 2012 6:28 AM
  • Hi,

    Most likely you have more then one error. Making a service account als a local Administrator isn't that good.

    You can validate if the Service Accounts have Local Activation permissions on the IIS WamReg Service in your DCOM config. If you can't validate it, go to regedit and find the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{61738644-F196-11D0-9953-00C04FD919C1}

    Alter the permissions and check your DCOM config again. Add the following User Group: WSS_WPG with Local Activation permissions. Restart IIS, and SharePoint Services. Voila.

    Friday, August 24, 2012 10:14 AM
  • Hi All,

    I'm having the same problem. My Timerservice stops every 2 minutes.

    I've been searching the log, but can't find anything related to the 'crashing'. I've even changed schedules of timerjobs, to be sure that it isn't that job that is crashing the service.

    I've already tried to make the account under which the service runs a local admin (just to see if it works. I know it's not good), but it doesn't work.

    We're running some Nintex workflows too. Can that be related??

    Any help is appreciated.


    Rinze Smit Application Specialist Revalidatie Friesland (Netherlands)

    Monday, November 19, 2012 9:38 PM
  • Having the same issue. Timer service stops unexpectedly every few minutes. It restarts automatically.


    I've tried adding the service account to local administrators and have confirmed that the service account has full access to the folder specified in one of the posts above.


    Log Name:      System
    Source:        Service Control Manager
    Date:          11/28/2012 9:12:04 AM
    Event ID:      7031
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sp.spa.local
    Description:
    The SharePoint 2010 Timer service terminated unexpectedly.  It has done this 5969 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7031</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2012-11-28T14:12:04.978144500Z" />
        <EventRecordID>639034</EventRecordID>
        <Correlation />
        <Execution ProcessID="564" ThreadID="5316" />
        <Channel>System</Channel>
        <Computer>sp.spa.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">SharePoint 2010 Timer</Data>
        <Data Name="param2">5969</Data>
        <Data Name="param3">30000</Data>
        <Data Name="param4">1</Data>
        <Data Name="param5">Restart the service</Data>
      </EventData>
    </Event>

    Log Name:      System
    Source:        Service Control Manager
    Date:          11/28/2012 9:12:04 AM
    Event ID:      7024
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      sp.spa.local
    Description:
    The SharePoint 2010 Timer service terminated with service-specific error %%-2147467259.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7024</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2012-11-28T14:12:04.977168000Z" />
        <EventRecordID>639033</EventRecordID>
        <Correlation />
        <Execution ProcessID="564" ThreadID="1984" />
        <Channel>System</Channel>
        <Computer>sp.spa.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">SharePoint 2010 Timer</Data>
        <Data Name="param2">%%-2147467259</Data>
      </EventData>
    </Event>

    Log Name:      System
    Source:        Service Control Manager
    Date:          11/28/2012 9:12:04 AM
    Event ID:      7036
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      sp.spa.local
    Description:
    The SharePoint 2010 Timer service entered the stopped state.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="16384">7036</EventID>
        <Version>0</Version>
        <Level>4</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2012-11-28T14:12:04.977168000Z" />
        <EventRecordID>639032</EventRecordID>
        <Correlation />
        <Execution ProcessID="564" ThreadID="1984" />
        <Channel>System</Channel>
        <Computer>sp.spa.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">SharePoint 2010 Timer</Data>
        <Data Name="param2">stopped</Data>
        <Binary>53005000540069006D0065007200560034002F0031000000</Binary>
      </EventData>
    </Event>

    Wednesday, November 28, 2012 2:15 PM
  • Same problem, SharePoint 2010 Timer would run for about 30 seconds then crash.  The account that runs the service was already in local admins (bad practice I know, but I was not the person who set this up).  Turns out it was one particular SharePoint task that was causing our SPTimer service to crash.  Try looking in the SharePoint admin site at your tasks.  Check if you have any tasks sitting at 0%.  Try disabling it and starting the SPTimer service.  If that didn't fix it, look at the five or so tasks that start before it crashes and notice how some succeeded.  Look for a task that is in those five each time and try disabling that one.

    Monday, January 28, 2013 12:52 AM