As you might have noticed I’ve been blogging a lot about Application Pages and TimerJob related stuff in the last few months and this post is about those two same things! So apologies for that.. But you might get a smile on your face when you see the following screenshot:
What have I done and what do you see?
Well, I’ve created yet another application page (YAAP, cool acronym ;) that displays all the current timer job definitions and furthermore it showes for each timer job it’s status. So basically I’ve combined the Timer Job Status page and the Timer Job definitions page. But that wasn’t my main concern to build these pages.. the main concern was to have some more insight in the current defined jobs. Things like, when are they scheduled exactly (when is ‘hourly’ or ‘daily’) and give the administrators the choice to disable and/or delete timerjobs or change the schedule of each one.
Why did I add the option of mass deletion of timerjobs? I’ve seen some farms that when they are using Content Deployment, this service creates a lot of OneTime scheduled timerjobs. When these fail, they are not being deleted properly so it could be that the Timer Job definitions list can be flooded with those OneTime scheduled jobs. So you might want to remove these timerjobs to clean up the definitions list eh? Especially if the Timer service get’s restarted (after a WSP installation for example) then all those one timed jobs are being executed again and will fail again and will stay in the list again..
Why did I add the option of changing the schedule of timerjobs? I’ve seen some farms that had custom timerjobs installed on them but no interface for administrators to change the schedule or to disable the timerjob at all (other then deactivating the feature which came with the solution).
I also wanted to incorporate a feature that would let you create a new OneTime schedule to kick off a timerjob. Since you cannot change the schedule of a existing timerjob to OneTime schedule (you receive a nice error that tells you, you can’t change the schedule:), I have to create a new instance of that particular timerjob and give that one the OneTime schedule to run. And that ‘creating a new instance of that particular job’ is still a work in progress :)
It’s going to be on Codeplex.. but currently I’m getting this message on Codeplex : “Unable to save the release. The TFS server is not available”.. so .. sorry ;)
Meanwhile I’ve uploaded the installer here for you to download and play around with ;)
Get it from CodePlex right here !
Technorati Tags: SharePoint