Category: Timer Jobs

SharePoint 2016 / 2019 – Timer jobs with Job lock type do not run

This is going to be very similar to another recent post: In that case, timer jobs with lock type “ContentDatabase” would not run because no server in the farm has its AllowContentDatabaseJobs property set to “true”. In this case, Timer jobs with LockType = “Job” and IsServiceJob = “True” will not run because no

SharePoint 2016 / 2019 – Timer jobs with ContentDatabase lock type do not run

In SharePoint 2016 and 2019, you may find that some timer jobs are not doing what they should. In timer job history, you may see that the timer jobs are running successfully, but they aren’t doing anything. Depending on the timer job, this can be a little difficult to detect. Of the timer jobs affected

SharePoint: All about one-time timer jobs

Update 9/15/19: Added some clarifying info, and some PowerShell that can be used to delete any “stuck” one-time timer jobs. One-time timer jobs are created on the fly, should run immediately, and then disappear when they are done doing whatever they were supposed to do.  If you have one-time timer jobs hanging around, you have

SharePoint 2016: Active Directory Import timer job does not run – AllowServiceJobs

This is an interesting “gotcha” that came up recently: Problem: The Active Directory Import (UserProfileADImportJob) timer job does not run.  It’s enabled and scheduled to run (default every 5 minutes), but never runs.The result is that the user profiles never get imported. Cause: All the servers in the farm that are running the User Profile