Timer service failed to recycle

Symptoms

 

On Central Admin, Health Analyzer shows "The timer service failed to recycle" warning:

 







































Cause


The Timer Service Recycle job was blocked by other running Timer jobs, such as:













The running jobs that block the Recycle job could be stuck in the running mode and need to be verified first.


Resolution


1.      Make a note of the Failing Servers in the report and run the Timer Service Recycle Job from Central Admin > Monitoring > Job Definitions > Timer Service Recycle. (Direct URL: https://<caDomainName>/_admin/JobEdit.aspx?JobId=<guid>) Click the "Run Now" button. This will kick off the Job across all servers in the farm. 

2.      Go to the Running Jobs page (https://<caDomainName>/_admin/ServiceRunningJobs.aspx) and wait until the Job finishes. It will take several minutes.

3.      Check the Job History page (https://<caDomainName>/_admin/TimerJobHistory.aspx) and ensure that the Job status shows “Succeeded” for all servers. If the server entries are not found, the job has not started or finished running yet. Check the status at https://caDomainName/_admin/Timer.aspx. If the status is “Failed”, go to the failing servers and restart the SharePoint Timer (SPTimerV4) service.

4.    Repeat Step 1 and 2.  

5.    Click “Reanalyze Now” at https://caDomainName/Lists/HealthReports/DispForm.aspx?ID=<number>  

6.      Wait for a few minutes and confirm the “Success” message: Graphical user interface, text, application, email Description automatically generated


Popular posts from this blog

October 2025 SharePoint CU Failed to Install After Applying September 2025 SharePoint CU

Image
[Tested on SharePoint 2016 only] Applying the September 2025 SharePoint Cumulative Updates to SharePoint On-Prem was a bit chaotic as it introduced a number of bugs. It would have been better if I had the option to skip it and go straight to the October CU. Stefan, the Sr. SharePoint Escalation Engineer at Microsoft, has summarized the issues very well on  his blog . While many of the issues have been fixed in the October CU release, the fix for the "installation of this package failed" error  was not included for those who had already applied the September CU before the fix was made. That is, the System and Local Service accounts have to be manually removed from the WSS_WPG and IIS_IUSRS groups before applying the October CU. Without this step, I encountered a new popup error that said: Error 2349. An internal error has occurred. ( ) Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see PSS10R.CHM. Remedy Remove...
Read more

September 2025 SharePoint 2016 CU - Configuration Wizard failed

Image
[Applies  to SharePoint 2016; not tested on other versions of SharePoint] While the farm account is in the local admins group (regardless of being present in the  WSS_WPG  group), running the psconfigui.exe (SharePoint Configuration Wizard) or psconfig.exe with the farm account gets stuck at the last step (step 10 of 10). Associated behaviors are: CopySideBySideFiles_*.log showing the endless repetition of: “\16\TEMPLATE\LAYOUTS\accessrequestcontrol.debug.js Access is denied. Waiting 30 seconds… Retrying…”. Unable to close the Config Wizard by hitting the Cancel or X button on the GUI; it has to be killed in Task Manager. The “Upgrade Status” page on Central Admin, however, shows the green status “Succeeded” even though it's not. Diagnosis Microsoft has deployed the security hardening with the 2025 September CU. The farm service account can no longer be used interactively from now on. Previously, this was not a requirement, despite the documentation at  https://lear...
Read more

Broken Site Collection

Image
[Tested on SharePoint 2016 only] Suppose the following error occurs while creating a new site collection with a farm admin user account: ## Assume all declared variables are correct ## PS C:\FarmAdminUserAccount> New-SPSite -Url $spSite -Name $scName -Description $scDesc -ContentDatabase $cdb -QuotaTemplate $scQuota -Template $scTemplate -Language 1033 -OwnerAlias $scPrimaryAdmin -OwnerEmail $scPrimaryEmail -SecondaryOwnerAlias $scSecondaryAdmin -SecondaryEmail $scSecondaryEmail ********************** PS>CommandInvocation(Out-String): "Out-String" >> ParameterBinding(Out-String): name="InputObject"; value="Calling extension methods on object Microsoft.SharePoint.Administration.SPContentDatabase+<>c__DisplayClass16 failed with exception(s): The UPDATE permission was denied on the object 'MSP_TVF_WEB_ADMIN', database 'WSS_Content_DbName', schema 'pjpub'." New-SPSite : Calling extension methods on object Microsoft.Sha...
Read more