All timer jobs don't start (paused in check job status)

Question

Hello,
Some bad things have happend to our SharePoint Server 2010. All timer jobs suddenly stopped running. The last time they ran successfully was 09/26/11. Since that time all jobs have been scheduled to run according to their schedule but don't actually run.
In the Check Job Status view there is a list of jobs scheduled to run 09/26/11 which are currently paused for some reasons, other jobs don't run at all. 
Is it possible to unpause these jobs and let other jobs to run? Any ideas would be very much apprecaited. Thank you in advance.

Answer 1

Hi,
Thanks for your post.
Pausable Timer Jobs
You can now create pausable timer jobs. This is done by inheriting from the
SPPausableJobDefinition and overriding Execute(SPJobState) instead of
Execute(Guid). You can then use the current job state (SPJobState) to store values which are retrieved when the job is resumed.
Running jobs on all content databases
Another new timer job derivative type is the SPContentDatabaseJobDefinition.This is a timer job specifically made to perform actions on content databases. The timer job is distributed on the WFE servers and each content database is only
processed by one job. Override the Execute(SPContentDatabase, SPJobState) to add your own processing. The job supports pausing.
Running jobs on all Site Collections
A really interesting new timer job type is the SPAllSitesJobDefinition. This one is derived from the SPContentDatabaseJobDefinition and has a method called
ProcessSite(SPSite, SPJobState) which you override to process the SPSite object. This could be very useful to build site inventories/directories.
Running job on a specific server
The SPServerJobDefinition is a pausable timer job that is designed to be targeted to a specific server (SPServer).
Running jobs for specific services
The SPServiceJobDefinition is another pausable timer job that runs a job on all servers where a specific
SPService has been provisioned. A very similar job is the
SPFirstAvailableServiceJobDefinition which runs the job on the first available server which has a specific SPService installed. If you would like to run a job an all servers you can easily use SPServiceJobDefinition. Then use the timer job service
(which is installed on all servers, except dedicated database servers) and pass
SPFarm.Local.TimerService as the SPService parameter in the constructor.
All of the new specific timer jobs are essentially smart derivatives of the SPJobDefinition but using these new abstract classes will certainly save you some time when you need to target your timer jobs.
I hope that helps.