Timer jobs have stopped running for a while in SharePoint 2016

SharePoint Guys 26 Reputation points


No timer jobs have been running on my SharePoint 2016 testing server for a while. I tried to start any timer jobs inside the Central Admin, but no timer job started to run.

I guess it may be caused by the wrong password of the SharePoint Timer Service account, as someone occasionally changed the password. I have updated the service account and restarted the SPTimer service. However, it doesn't help.

Since the "Delete Job History" timer job hasn't run for a while, the TimerJobHistory table has accumulated near 600,000 rows. I guess this may be the reason. But how to maintain this table in the SharePoint config database?

Would you please share your opinion, experience and knowledge? Thank you very much.

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,156 questions
SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,765 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Jinwei Li-MSFT 4,721 Reputation points Microsoft Vendor

    Hi @SharePoint Guys ,

    Please try to use this:

    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  

    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.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. SharePoint Guys 26 Reputation points

    Thank you for reply.

    I followed the steps that you listed above.

    I opened the content database settings of the Central Admin web application. However, there is no server to select; please refer to the screenshot. I think it is because this is a single-server farm.

    I restarted SharePoint Timer Service. However, the timer jobs still not running.....

    I am still thinking that I should maintain the TimerJobHistory table has accumulated near 600,000 rows since the "Delete Job History" timer job hasn't run for a while. I searched how to maintain the TimerJobHistory table in the SharePoint 2016 config database, but no useful information was found.

    In addition, is there any errors would be captured inside the ULS logs or the event log that can help me to do the troubleshooting?

    Thanks a lot!

    0 comments No comments