Thursday, November 22, 2012

Custom SharePoint timer job code doesn't seem to be updating

If you're running into a situation in which your making code updates to a custom SharePoint timer job and the code doesn't seem to be updating, you may want to try restarting the OWS Timer service to see if that helps resolve your issue.  To restart the OWS Timer service on SharePoint 2010, you can perform the following steps:
  1. Open the SharePoint 2010 Management Shell as an administrator 
  2. Enter “net stop SPTimerV4” and press enter. (The service will be stopped)
  3. Enter “net start SPTimerV4” and press enter. (The service will be started again)
In my particular example, I had just deployed a code update to one of the custom timer jobs on my SharePoint farm and, upon attaching the debugger to the OWSTimer, noticed that the debugger was simply skipping over the new lines of code that I had just added.  Anyway, refreshing the OWS Timer service made certain that the latest code I had just deployed was refreshed.  As a result, the debugger immediately started picking up the new lines associated with the code that I had previously deployed.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.