locked
Timer Jobs are not running on SharePoint servers RRS feed

  • Question

  • All,

        I have a four server 2013 test farm that I've been upgrading and documenting SharePoint 2010 databases on. There are two WFEs and two APP servers. The APP servers are not running any timer jobs at all. In Central Admin, under timer job history for these servers, there is no history. Here is what I tried so far.

    The only thing I'm seeing in ULS logs is this: Performance Counter OS (pdh) call failed with error code PDH_INVALID_DATA.

    Any thoughts will be appreciated.

    Tuesday, December 15, 2015 8:01 PM

Answers

  • Hi PawnofGod,

    According to your description, the timer jobs are not running in your servers and there is no job history.

    Per my knowledge, it is related to the timer service. You should keep your timer service running.

    Here are solutions for the error in ULS logs, though they are all applied in SP 2010, I think you can have a try:

    https://blog.tallan.com/2012/07/06/resolving-performance-counter-os-pdh-call-failed-with-error-code-pdh_cstatus_bad_countername-on-sharepoint-2010/

    Best Regards,

    CY

    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, December 16, 2015 9:04 AM
  • I ended up calling Microsoft support and the issue was resolved on first call. Apparently There were lots of one-time timer jobs and pending upgrade job were causing the issue on these servers.

    Here are the steps that were taken.

    Checked the timer job instance status and found all the instances are online using these PowerShell commands.
    $farm=Get-spfarm
    $farm.timerservice.instances

    Checked the timer job history and confirmed that that are no timer job running on these servers and the last jobs show up are failed upgrade jobs.

    There are lots of onetime time jobs in the job definitions.  We used the PowerShell to clean up some of them and then cleanup the rest manually.
    Get-sptimerjob | where {$_.title -like "SharePoint Worker Process Group Update"} | %{$_.delete()}
    Get-sptimerjob | where {$_.name -like "FormsMaintenanceJobDefinition2015*"} |  %{$_.delete()}

    Ran psconfig -cmd upgrade -inplace b2b -wait -force but it failed with error below
    An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown.  Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20151221-142700-130 was updated by domain\Farm_Account, in the PSCONFIG (6676) process, on machine APPServer1.  View the tracing log for more information about the conflict.

    Checked the timer job definitions and found that one-time job "Upgrade job", deleted it again.

    Ran below to set the command line upgrade status in the farm
    stsadm -o setproperty -propertyname command-line-upgrade-running -propertyvalue Yes

    Ran the command again on the server AppServer1 and this time it ran successfully


    Wednesday, December 23, 2015 12:06 PM

All replies

  • Hi PawnofGod,

    According to your description, the timer jobs are not running in your servers and there is no job history.

    Per my knowledge, it is related to the timer service. You should keep your timer service running.

    Here are solutions for the error in ULS logs, though they are all applied in SP 2010, I think you can have a try:

    https://blog.tallan.com/2012/07/06/resolving-performance-counter-os-pdh-call-failed-with-error-code-pdh_cstatus_bad_countername-on-sharepoint-2010/

    Best Regards,

    CY

    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, December 16, 2015 9:04 AM
  • I ended up calling Microsoft support and the issue was resolved on first call. Apparently There were lots of one-time timer jobs and pending upgrade job were causing the issue on these servers.

    Here are the steps that were taken.

    Checked the timer job instance status and found all the instances are online using these PowerShell commands.
    $farm=Get-spfarm
    $farm.timerservice.instances

    Checked the timer job history and confirmed that that are no timer job running on these servers and the last jobs show up are failed upgrade jobs.

    There are lots of onetime time jobs in the job definitions.  We used the PowerShell to clean up some of them and then cleanup the rest manually.
    Get-sptimerjob | where {$_.title -like "SharePoint Worker Process Group Update"} | %{$_.delete()}
    Get-sptimerjob | where {$_.name -like "FormsMaintenanceJobDefinition2015*"} |  %{$_.delete()}

    Ran psconfig -cmd upgrade -inplace b2b -wait -force but it failed with error below
    An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown.  Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20151221-142700-130 was updated by domain\Farm_Account, in the PSCONFIG (6676) process, on machine APPServer1.  View the tracing log for more information about the conflict.

    Checked the timer job definitions and found that one-time job "Upgrade job", deleted it again.

    Ran below to set the command line upgrade status in the farm
    stsadm -o setproperty -propertyname command-line-upgrade-running -propertyvalue Yes

    Ran the command again on the server AppServer1 and this time it ran successfully


    Wednesday, December 23, 2015 12:06 PM
  • Hi PawnofGod,

    Thanks for your sharing.

    Please mark your reply as answer. It will help others who encounter the same problem.

    Best Regards,

    CY


    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, December 24, 2015 1:29 AM