When Timer jobs go bad…
by liquidpooled on Nov.04, 2008, under Microsoft, Office, Sharepoint Server, TechNet, Windows SharePoint Services
Occasionally, for no good reason, administrative timer jobs can go bad, leaving them in a state of limbo. For instance, have you ever deployed a solution package and the status remains at “Deploying”? When behaviors like this begin to appear, the timer jobs in question can still be forced through by utilizing STSADM.
The execadmsvcjobs switch will force any pending jobs to execute immediately (such as a deployment gone bad). Execute the command on each server in your SharePoint farm, and the timer job should clear itself.
stsadm -o execadmsvcjobs