I found a post on the MSDN forums because I have the same problem and it recommended the SP1 upgrade to fix the Day Light Savings issue which we have here in Perth Australia. The Day Light Savings actually finished last week before we could get all our ducks in line to test the SP1 patch on our Test Servers and I really couldn't wait for our SharePoint SP1 rollout to happen and needed a solution out. Anyway, turns out the issue was still there after Day Light Savings ended.

I had blogged about this before here.

I noticed initially that the Windows SharePoint Services Timer was not running when I ran the add solution and deploy solution, so I started it. But it didn't seem to pick up the Jobs. I've tried execadmsvcjobs to force it and it doesn't pick it up. The Jobs are in the Job Definitions as "One-Time" and their is a Last Run time in there also which correlates with when I fired off the stsadm commands. It looks like it's just holding onto the Jobs for some reason.

I tried various things around Cancelling the deployment, which executes properly. But then when I try and retract the solution, it too gets a Job set up and gets stuck also, which means the Solution gets stuck at Retracting! Deleting the Job Timer Definition for some reasons resolves it from saying Deploying or Retracting.

I took a further look at this and basically it was because all the servers in the farms Windows SharePoint Services Timer had stopped! I remote connected to them all and started them and ran execadmsvcjobs and it all seemed to fix itself up.