Deployed Timer Job not taking new code when deployed

Question

I've realized recently that, when re-deploying (either manually or through vs2010) my timer job feature package, the updated execute code is not being deployed. Strange yea. Essentially, I'll deactivate all features,retract my package, change the exec code in vs2010, re-deploy, and the code won't be updated. The old timer code will run.

I found a fix though. If I change the assembly and file versions with each deployment, the changes get picked up. Anyone know why this is necessary?

score 26 · Accepted Answer · answered Apr 08 '12 at 02:42

26

You need to restart the SharePoint timer service (Start > Run > Services.msc). The timer jobs code get cached in the timer.

answered Apr 08 '12 at 02:42

John Chapman

11,941
6
36
62

2
Right on! Thanks. I added the commands to the lab/production deployment scripts. Also, in VS2010, I added
```
net stop sptimerv4
net start sptimerv4
```
to the "Post Deployment Command Line Field" in Project -> Properties -> SharePoint.
– 1c1cle Apr 08 '12 at 14:48
2

Good idea on adding it to the deploy process in VS. – John Chapman Apr 08 '12 at 18:07
The same applies to WSS/MOSS 2007. Forgot about restarting the timer service, thanks StackExchange! – CigarDoug Feb 27 '13 at 15:35

score 11 · Answer 2 · answered Apr 08 '12 at 06:04

11

Just try to run this from the run dialogue

net stop sptimerv4
net start sptimerv4

this should do the trick.

answered Apr 08 '12 at 06:04

Oyshik Moitra

171
1
5

2

Or from PowerShell Restart-Service SPTimerV4 – Per Jakobsen Apr 08 '12 at 07:32
@PerJakobsen You should add this as an answer! – George Norberg Sep 17 '14 at 12:50

score 0 · Answer 3 · answered Mar 06 '14 at 09:08

0

The solution is to change your assembly and file version numbers: Project Properties -> Application -> Assembly Information...

answered Mar 06 '14 at 09:08

asilioni

11

Whoo, no, that should not be necessary to make it pick up your new code. – Cameron Verhelst Mar 06 '14 at 09:17
1

a solution, not 'the solution'. – 1c1cle Mar 10 '14 at 16:44

Deployed Timer Job not taking new code when deployed

3 Answers3