SharePoint components - business processes without development, InfoPath, SharePoint Designer or workflows. SharePoint Services, SharePoint Foundation & SharePoint Server 2010-2016.

Service Jobs in SharePoint 2016

By: Genady Vaisman | Comments [0] | Category: Administration | 7/10/2017

The latest SharePoint version introduces a new setting that can be applied to each of the timer server instances: AllowServiceJobs

When this attribute is set to false, basically this server will not be able to execute timer jobs with SPJobLockType: Job ("Service Jobs").

This type of lock is needed to ensure that this timer job is executed only on one of servers, basically to prevent multiple executions of the same logic.

Several of our products are affected by this setting: Smart Import ProSmart Action ProNewsletter. These Products will not be able to function properly in regards of their background / timed functionality. Another impact may be on the installation process, in terms of failure in deploying required recourse files.

Mind that this behavior can be caused only on SharePoint 2016 farms, as previous versions did not allow this setting to be controlled.

 

You can use the following PowerShell script to determine the value of this property in your farm:

$farm = Get-SPFarm

$FarmTimers = $farm.TimerService.Instances

foreach ($ft in $FarmTimers)

{

       write-host “Server: ” $ft.Server.Name.ToString();

       write-host “Status: ” $ft.status;

       write-host “Allow Service Jobs: ” $ft.AllowServiceJobs;

}

 

And the following script to enable it:

$farm = Get-SPFarm

$FarmTimers = $farm.TimerService.Instances

foreach ($ft in $FarmTimers)

{

      if ($ft.AllowServiceJobs -eq $false)

      {

             write-host “Service jobs are NOT enabled on ” $ft.Server.Name.ToString();

             write-host “Enabling service jobs”;

             $ft.AllowServiceJobs = $true;

             $ft.Update();

      }

      else

      {

             write-host “Service jobs are enabled on ” $ft.Server.Name.ToString()

      }

}

 

source: https://www.chrisgolden.de/blog/2017/06/20/sharepoint-2016-active-directory-import-timer-job-does-not-run

0 comments

Leave a Comment:

Comments are moderated and will appear after approval
Comments are not designed to replace support calls. If you have a specific issue with one of our products, please send an email to support@infowisesolutions.com to open a support ticket.