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 created a custom timer job (SharePoint 2010) which gets registered through a feature receiver. At the moment the custom timer job works fine but I need to make changes to the code. So, naturally I recompiled my project and repackaged it into a WSP.

However, when I run update-spsolution the timerjob continues to run the old code. I have verified the the assembly is deployed successfully. So other parts of the site have been updated as a result but the timerjob continues to behave as before.

I also tried restarting IIS but that did not help. I then deactivated/reactivated the feature, but still the timerjob executes old code.

How can I update this timer job properly?

share|improve this question
up vote 5 down vote accepted

The timer job is run by SharePoint Timer Service (OWSTimer.exe). So you need to restart the service (so that the new dll is referenced) from the Services control panel.

To open Services, Start>Control Panel>Administrative Tools>Services. Right-click the SharePoint Timer Service and click Restart.

share|improve this answer
A life saver... been struggling to resolve the mistery why my job doesnt execute the recompiled version. Also I noticed after receiving the list it start to throw error message to MS Event Viewer saying the list is no longer available when in fact it was never been use after recompilation. Thanks. – R2C3 May 7 '12 at 9:21
So glad I found this answer! Totally fixed weird null references I was seeing while debugging! – swolff1978 Jul 19 '13 at 17:02

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.