SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a custom timer job that I create an instance of by activating a web application scoped feature in Central Admin. In the farm, the Central Admin box is an application server. What I'm finding is that the timer job is only scheduled to run on the application server, and not on the WFE. I used the "Job History" page in Central Admin to determine this.

Note that I am already setting the LockType to "SPJobLockType.None" in the constructor for my timer job.

var job = new CopyConfigJob(webApp);

The constructor for my custom timer job looks like:

public CopyConfigJob(SPWebApplication webApp) :
   base(JobNamePrefix + Guid.NewGuid().ToString(), webApp, null, SPJobLockType.None)
   Title = JobTitle;
share|improve this question
Please add the code you're using. – Anita Boerboom Aug 4 '11 at 16:41
up vote 3 down vote accepted

Make sure you haven't set DeploymentServerType="ApplicationServer" in your Solution Manifest file. You can also go to the WFE and see if the job-related assembly(s) have been GAC'd.

Can you provide the line of code you're using when you create an instance of the job...i.e:

MyTimerJob job = new MyTimerJob("jobname", webApp, null, SPJobLockType.None);
share|improve this answer
I was not deploying the solution to the WFE server. Your comment made me notice that the assembly containing the job code was not in the GAC on the WFE. Of course the job can't run there without the code! Thanks for your help. – jason.venema Aug 4 '11 at 21:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.