none
SharePoint timer jobs not running, appearing as not applicable in log

    Question

  • We have a SharePoint 2016 farm with 2 app, 2 wfe and 2 distributed cache servers. We are facing issue that most of the timer jobs are not running and their last run time is appearing as NA.  There is no custom job. In order to resolve the issue, tried the below solutions but no success:

    * Clear the cache on all servers, restart timer job, reset iis.

    * ReEnter the logon credentials for timer job user account.

    * Change the user account of timer service.

    While checking the log files got error that "Job definition {Job Name}, id {Job ID} not applicable, ignoring". The log file is available at this link Log File.

    Appreciate any suggestion to resolve the issue.

    Tuesday, April 18, 2017 7:41 AM

All replies

  • Hi,

    Please make sure that SharePoint Timer Service is running in your SP servers.

    If you enumerate the timer job via PowerShell:

    Get-SPTimerJob | where {$_.DisplayName -like “<timer job name>”}

    does it show a proper last execution time?

    Thanks,

    Dean Wang


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

    Wednesday, April 19, 2017 2:49 AM
    Moderator
  • Hi Dean,

    Thanks for your reply.

    I tried your suggested command, it's showing Last Run Time "01/01/0001" for all instances of Immediate Alerts timer job .

    Wednesday, April 19, 2017 9:43 AM
  • Hi,

    It seems that your SharePoint product hasn’t been set up correctly, please to re-run the Configuration Wizard on each SharePoint server. Then check whether the issue occurs.

    Thanks,

    Dean Wang


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

    Tuesday, April 25, 2017 12:29 AM
    Moderator
  • I also meet this problem!

    Did you get the solution now?

    Wednesday, October 18, 2017 2:22 AM
  • Hi,

    This solution helps me to solve a same problem.

    1. Open SharePoint Management Shell and execute code below:

    # Get WFE server on which you want to restore the timer service
    Get-SPServer -Identity "<name of WFE server>" 
    $ts = $server.ServiceInstances | ? { $_.GetType().Name -like "*sptimerservice*" } | Select -First 1
    $ts.AllowContentDatabaseJobs = $true
    $ts.AllowServiceJobs = $true
    $ts.Update()

    2. Open Central Administration and go to Manage content databases then select content database and select the server specified in the previous step as the Preferred Server for Timer Jobs.

    3. Restart SharePoint Timer Service.

    • Proposed as answer by StéphanC Thursday, March 29, 2018 3:47 PM
    Friday, January 26, 2018 6:03 AM
  • Thanks Roman, I already passed AllowServiceJobs to $true to allow AD import on WFE but let ContentDB to $false.

    following your procedure did the trick for me!

    Thursday, March 29, 2018 3:49 PM