Expiration Policy Job is not running
Hi, I have setup a expiration policy for a list and configured the expiration policy for the list to delete the items on the same day of its creation, (created + 0 days). Then 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 it says the timer job(Expiration Policy) only ran last night at 11:15 PM. So it means it runs everyday as scheduled but it does not run when I click on "Process Expired Items Now". So above case my items are not getting deleted .. Whats step I'm missing here Thanks in advance, San
October 6th, 2009 8:57pm

I am not 100% sure I am right on this but I believe that it is working correctly. I believe it will not delete the docs until they are at 1 day. When they reach 1 day they would violate the 0 days rule. Right now they are not violating that rule
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2009 10:44pm

Hi, Based on my research, when I click “Process Expired Items Now”, the items that was created on today was deleted. There may be a problem with some part of the 'Records Management' feature not being completely activated which is why you are facing this issue. You can try to run the following command, then check the effect. stsadm -o activatefeature -filename recordsmanagement\feature.xml –force For expiration policy start time, it just records the schedule time not the time you manually start expiration policy. Hope this helps. Rock Wang Rock Wang– MSFT
October 8th, 2009 10:12am

I have enabled the recordsmanagement but still I'm having the same issue, but the job runs every day as schedule
Free Windows Admin Tool Kit Click here and download it now
October 8th, 2009 9:20pm

Hi, Did you run the following command, if not, please run the following command and then check the effect. stsadm -o activatefeature -filename recordsmanagement\feature.xml –force Hope this helps. Rock WangRock Wang MSFT
October 14th, 2009 5:05am

Rock, I am having the same problem as the OP and ran your command. It did not fix the issue. I have a list of items and created a workflow that changes a text field from "No" to "Yes" if the expiration date on the item is today or earlier (Today + 0 days). I have verified that the workflow functions correctly by having it run on new items to test it out. When I click on "Process Expired Items Now", the Expiration timer job starts, but it does not kick off my workflow that I have setup in Information Management Policy Settings in my list. When I look at the timer job status page in Central Admin after kicking off the Expiration timer job, it starts up and then disappears and never shows as completed. Mine still shows that the last time the job was run was 11:15 PM last night.
Free Windows Admin Tool Kit Click here and download it now
October 20th, 2009 10:42pm

Just a little more info on this point. If you click the "Process Expires Items Now" button, another job is created and shown on the Timer Job Status page, along the lines of "Expiration Policy (Manual)". It appears only briefly then its gone. However, it didnt seem to do anything on my expired items. I wonder, is it possible to change the scheduled time of the main "Expiration Policy" timer job for testing purposes?
January 7th, 2010 4:18pm

I found that the manual process expired items button doesnt seem to do anything, but if you allow the timer job (which runs daily just after 11pm) to do its thing, expired documents do get removed to the recycle bin
Free Windows Admin Tool Kit Click here and download it now
January 8th, 2010 12:47pm

Hi, If you want to run the Expiration policy job frequently during the day, create a console application and run the below code. After running following code on server, the Expiration policy job will start running every 5 minutes. using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Diagnostics; using Microsoft.SharePoint.Administration; using Microsoft.SharePoint; namespace RunExpirationPolicy { class Program { static void Main(string[] args) { SPSite siteCollection = new SPSite("http://SiteCollectionURL"); SPWeb web = siteCollection.OpenWeb(); SPFarm farm = siteCollection.WebApplication.Farm; SPWebApplication webApp = siteCollection.WebApplication; SPTimerService timerService = farm.TimerService; foreach (SPService srv in SPFarm.Local.Services) { foreach (SPJobDefinition jobDef in srv.JobDefinitions) { if (jobDef.Title == "Expiration policy") { jobDef.Schedule = SPSchedule.FromString("every 5 minutes between 0 and 59"); jobDef.Update(); Console.ReadLine(); break; } } } Console.Read(); } } } After running the above code on server, your expiration policy job will start running every 5 minutes. Hope, this will help you. Thanks, Rinkal
January 11th, 2011 4:27pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics