none
SharePoint 2010 Timer Service keep failing

    Question

  • Hi everybody,

     

    I am trying to set up SharePoint 2010 on small farm environment. 1 db server, 1 domain controller and 1 SharePoint server - where all services should run.

    It was installed and working, until I tried to configure user profile synchronization service. I used least privileged account model, following in particular this article http://www.harbar.net/articles/sp2010ups.aspx

    As you know, the configuration is quite complicated and require a lot of tuning on accounts rights.

     

    I apparently mess something up very, very badly because since then SharePoint Timer Service keep failling every 2 or so minutes.

    It all started at 6 am this morning when the service was recycled.

     

    System Event viewer is flooded a loop of 4 events regarding the timer service:

    • Timer service entered the running state.
    2.30 minutes latter:
    • Timer service entered the stopped state
    • Timer service terminated with service-specific error %%-2147467259
    • Timer service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 30000 milliseconds: Restart the service
    and starting again after 30 seconds

     

    for you information, here are the exact events:

    Log Name:   System
    Source:    Service Control Manager
    Date:     9/21/2010 4:42:04 PM
    Event ID:   7036
    Task Category: None
    Level:     Information
    Keywords:   Classic
    User:     N/A
    Computer:   server.Domain.company.com
    Description:
    The SharePoint 2010 Timer service entered the running 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="2010-09-21T14:42:04.337517900Z" />
      <EventRecordID>11334</EventRecordID>
      <Correlation />
      <Execution ProcessID="468" ThreadID="2916" />
      <Channel>System</Channel>
      <Computer>server.Domain.company.com</Computer>
      <Security />
     </System>
     <EventData>
      <Data Name="param1">SharePoint 2010 Timer</Data>
      <Data Name="param2">running</Data>
      <Binary>53005000540069006D0065007200560034002F0034000000</Binary>
     </EventData>
    </Event>
    
    ---------------------------------------------------------------------
    
    Log Name:   System
    Source:    Service Control Manager
    Date:     9/21/2010 4:44:38 PM
    Event ID:   7036
    Task Category: None
    Level:     Information
    Keywords:   Classic
    User:     N/A
    Computer:   server.Domain.company.com
    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="2010-09-21T14:44:38.237736300Z" />
      <EventRecordID>11335</EventRecordID>
      <Correlation />
      <Execution ProcessID="468" ThreadID="2648" />
      <Channel>System</Channel>
      <Computer>server.Domain.company.com</Computer>
      <Security />
     </System>
     <EventData>
      <Data Name="param1">SharePoint 2010 Timer</Data>
      <Data Name="param2">stopped</Data>
      <Binary>53005000540069006D0065007200560034002F0031000000</Binary>
     </EventData>
    </Event>
    
    ---------------------------------------------------------------------
    
    Log Name:   System
    Source:    Service Control Manager
    Date:     9/21/2010 4:44:38 PM
    Event ID:   7024
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     N/A
    Computer:   server.Domain.company.com
    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="2010-09-21T14:44:38.237736300Z" />
      <EventRecordID>11336</EventRecordID>
      <Correlation />
      <Execution ProcessID="468" ThreadID="2648" />
      <Channel>System</Channel>
      <Computer>server.Domain.company.com</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:     9/21/2010 4:44:38 PM
    Event ID:   7031
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     N/A
    Computer:   server.Domain.company.com
    Description:
    The SharePoint 2010 Timer service terminated unexpectedly. It has done this 2 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-09-21T14:44:38.238702400Z" />
      <EventRecordID>11337</EventRecordID>
      <Correlation />
      <Execution ProcessID="468" ThreadID="2528" />
      <Channel>System</Channel>
      <Computer>server.Domain.company.com</Computer>
      <Security />
     </System>
     <EventData>
      <Data Name="param1">SharePoint 2010 Timer</Data>
      <Data Name="param2">2</Data>
      <Data Name="param3">30000</Data>
      <Data Name="param4">1</Data>
      <Data Name="param5">Restart the service</Data>
     </EventData>
    </Event>

    Obviously, rebooting server didn't work.

    And I was not able to find anything about error "2147467259"

    If seen in some place suggested that it was a problem of memory overflow, but monitoring RAM usage show a nice maximum of 20%.

    I also have a handful of running jobs blocked at 0% in "paused" state. It's because they all started after the problem with timer service. I though of deleting them before trying to restart the service, but didn't find a way to flush the jobs queue.

    Finally, I absolutely don't know if it is related, but just before timer service started to fail, there is an error registered about permission for COM application

    Log Name:   System
    Source:    Microsoft-Windows-DistributedCOM
    Date:     9/21/2010 6:11:27 AM
    Event ID:   10016
    Task Category: None
    Level:     Error
    Keywords:   Classic
    User:     Domain\user1
    Computer:   server.Domain.company.com
    Description:
    The application-specific permission settings do not grant
    Local Activation permission for the COM Server application with CLSID 
    {B20E899D-B079-479D-A4DC-10F758D9CD9A}
    and APPID 
    {9209B1A6-964A-11D0-9372-00A0C9034910}
    to the user Domain\user1
    SID (S-1-5-21-2251373225-620573423-3193462131-1109)
    from address LocalHost (Using LRPC).
    This security permission can be modified
    using the Component Services administrative tool.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
     <System>
      <Provider Name="Microsoft-Windows-DistributedCOM"
    Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}"
    EventSourceName="DCOM" />
      <EventID Qualifiers="49152">10016</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime="2010-09-21T04:11:27.000000000Z" />
      <EventRecordID>10331</EventRecordID>
      <Correlation />
      <Execution ProcessID="0" ThreadID="0" />
      <Channel>System</Channel>
      <Computer>server.Domain.company.com</Computer>
      <Security UserID="S-1-5-21-2251373225-620573423-3193462131-1109" />
     </System>
     <EventData>
      <Data Name="param1">application-specific</Data>
      <Data Name="param2">Local</Data>
      <Data Name="param3">Activation</Data>
      <Data Name="param4">{B20E899D-B079-479D-A4DC-10F758D9CD9A}</Data>
      <Data Name="param5">{9209B1A6-964A-11D0-9372-00A0C9034910}</Data>
      <Data Name="param6">Domain</Data>
      <Data Name="param7">user1</Data>
      <Data Name="param8">S-1-5-21-2251373225-620573423-3193462131-1109</Data>
      <Data Name="param9">LocalHost (Using LRPC)</Data>
     </EventData>
    </Event>

    It is a bit surprising because user is my personal user to log into server and not sp_farm account that is used for SharePoint configuration.

    This error didn't repeat after reboot though, so I don't know what to make of it...

     

    I am now at an absolute lost about what to do, any help would be useful.

    • Edited by Aekko85 Tuesday, September 21, 2010 4:16 PM formatting pb
    Tuesday, September 21, 2010 4:03 PM

Answers

  • So, I am not exactly sure why did it work, but here what I did:

    1. Corrected DCOM error following article provided by Victor
    2. Cleanly stopped sptimerv4 service (not waiting for it to fail, but stopping it from service manager)
    3. Restarted timer service

     

    Since then the service do not crash anymore.

    I'll wait for planned recycling of service tomorrow morning to be sure that everything is ok.

    • Marked as answer by Aekko85 Thursday, September 23, 2010 3:15 PM
    Thursday, September 23, 2010 3:15 PM

All replies

  • What account does the sptimerv4 service run under? My guess is that the account does not have appropriate permissions to the databases

    The DCOM 10016 can be fixed using this: http://www.wictorwilen.se/Post/Fix-the-SharePoint-DCOM-10016-error-on-Windows-Server-2008-R2.aspx


    SharePoint MVP and Solutions Architect
    http://www.wictorwilen.se/
    Author of SharePoint 2010 Web Parts in Action
    Tuesday, September 21, 2010 4:45 PM
  • Hi Victor

     

    Sptimerv4 service run under the sp_farm account, that was used to install sharepoint. It does have databases access and it's working fine for other sharepoint services:

    • public
    • dbcreator
    • securityadmin
    • permission to connect: granted
    • login: enabled

    Unless timer service is depending on a specific database I am not aware of, login is map to user db_owner for all sharepoint databases on server.

    I think the problem is not coming for there.

     

    Plus , what is happening is not that the service cannot start, the problem is that it starts and then keep shutting down !

     

    I will look at the fix about DCOM 10016, but I really doubt it has anything to do with timer service.

     

    So... still looking for help

    Wednesday, September 22, 2010 8:54 AM
  • So, I am not exactly sure why did it work, but here what I did:

    1. Corrected DCOM error following article provided by Victor
    2. Cleanly stopped sptimerv4 service (not waiting for it to fail, but stopping it from service manager)
    3. Restarted timer service

     

    Since then the service do not crash anymore.

    I'll wait for planned recycling of service tomorrow morning to be sure that everything is ok.

    • Marked as answer by Aekko85 Thursday, September 23, 2010 3:15 PM
    Thursday, September 23, 2010 3:15 PM
  • Just for the record, we have a SQL server separate from our SP server and were getting this error. No matter which server we restarted, the problem was still there. No matter what we tried, we could not connect to the SQL server via a remote Management Studio interface- we could only connect to the SQL server databases via the local management interface! This was a clue that our problem was network related.

    One of our SQL gurus decided to restart the SQL Browser service on the SQL server and voila, our SP system was back up.

     

    Crazy, but true!


    Monday, April 4, 2011 12:25 AM
  • After lots of headaches, we finally fixed it by stopping and starting  User Profile Synchronization service.
    Wednesday, April 25, 2012 4:01 PM
  • For the DCOM error with AppID {9209B1A6-964A-11D0-9372-00A0C9034910} I've written an article: http://windoh.wordpress.com/2012/05/25/dcom-error-related-to-machine-debug-manager/. It's very difficult to find out what exactly is trying to do the local launch of the COM object with this AppID, but perhaps you can find out if you take a look at the other errors you have. My article deals with the error as a stand-alone error, but you can find out more because it's possibly related to the other errors. Greetings!

    Pedro

    Sunday, May 27, 2012 11:43 AM
  • It looks like this was already answered with another solution, but in my case the problem was that the one of the servers in the farm had the "SharePoint 2010 Timer" set to run with an account that needed to have the password updated.  We updated this service on each service with the new password and the error went away on all servers.
    Wednesday, February 27, 2013 9:47 PM