Failed to call SharePoint timer jobs

I have a timer job that has been deployed to a server with multiple ends of the web interface.

  • This timer job reads its configuration from the Hierarchical Object Storage.
  • This timer job is scheduled to run daily on the server.

But the problem is that this timer job is not called daily. I have implemented event logging in the Execute () execution method, but I do not see any logs being generated.

  • Any ideas on what might cause the timer job to not be received for execution by the SharePoint Timer service? How to fix this problem?

  • Are there any "gotcha" for running timer jobs on servers with multiple interfaces? Will the timer job run at all ends of the web interface, or any of them in arbitration? How to find out which machine will have event logs?

  • This may be a stupid question, but does a few front ends for load balancing affect the behavior of hierarchical objects?

EDIT:

One of the commentators, Sean McDownow (thanks to Sean !!) made a very good point that:

"whether the execution of the timer job on all WFEs will be a function of the value of the SPJobLockType enumeration specified in the constructor. Using the value" No "means that the task will run on all WFEs."

Now my timer job is responsible for sending periodic emails to the list of users. It is currently tagged as SPJobLockType.Job "

  • If I change this to SPJobLockType.None, does this mean that my timer job will run separately in all WFEs? (This is undesirable, it will spam all users with several emails)

  • Or does this mean that the timer job will run in any of the WFEs, whatever?

+6
sharepoint moss wss sharepoint-2007 timer-jobs
source share
2 answers

Try restarting the SharePoint Timer service from the command line using NET STOP SPTIMERV3 and then NET START SPTIMERV3. I assume the timer service is working with an old version of your .NET assembly. The timer update service does not automatically restart assemblies when updating a WSP solution.

+9
source share

To do this, follow these steps:

  • Stop the timer service.
  • Click Start, select Administrative Tools and Services.
  • Right-click Windows SharePoint Services, and then click Stop or Restart the Service.

This url helped me.

+2
source share

All Articles