>I have been looking into expiration policies for a customer. So fired up my dev machine and applied the policy to a custom content type.

The policy is run once a day, however fortunately you can start it manually. Using Central Admin->Operations->Information Management Policy Configuration, I clicked on the Expiration policy link. Then within there clicked “Process Expired Items Now”. Looked at the Timer Job Status (Central Admin->Operations->Timer Job Status) and there was no reference of the Expiration Policy.

Looked within Timer Job Definitions (just under the Timer Job Status link) and a timer job had been created called “Expiration Policy (manually initiated)” but it had never been run. Actually neither had the daily “Expiration Policy”. I went back to the Information Management Policy Configuration and into the Expiration policy. The “Process Expired Items Now” button was greyed out, to clear this I ended up deleting the “Expiration Policy (manual initiated)” timer job. This enabled the “Process Expired Items Now” button… however nothing.

Other things that I tried included stsadm -o execadmsvcjobs – though nanda.

Then I thought about the fact that the job had never been run and I found this article
http://www.sharepointblogs.com/teameli/archive/2008/10/13/record-center-information-management-policy-jobs-not-running.aspx

Following the instructions sorted the problem…

>Over the past few days I have been addicted to listening to the SharePoint Podshow by Rob Foster, Nick Swan and Brett Lonsdale. They have had some great speakers including Rob Brogue, Andrew Connell and Bill English.

Just finishing the second Andrew Connell which has been really interesting. What I do find that helps is that these people are really on top of their game and a lot of their views I share. This helps when you are in a situation where you have a certain view but are not sure that its entirely correct.

Take a look and start downloading the podcasts at http://www.sharepointpodshow.com/