Wednesday, November 21, 2012

Expiration Policy or Information Policy Management: Aborted

Few days back I have noticed that in our environment the Expiration Policy started successfully, however aborted after few min. This was happening for few days. There were no Event logs, no service drop alert.
The depth was left to be searched, yes correct the USL logs. In ULS logs we found some of the references form Information Policy Management service failed due the access blocked on the site.
ULS logs entry: Error message
10/23/2012 23:03:18.48             OWSTIMER.EXE (0x2D7C)                       0x22B4  DLC Server                                Information Policy Management        5016     Critical  Expiration Service for site failed. Access to this Web site has been blocked.  Please contact the administrator to resolve this problem
Why this happen
While processing the information Policy Management configured on some of the lib., the expiration policy service don’t find reference of the site because its access is blocked. Hence aborted or terminates its execution.

Go to central admin -> Applications Mgt. tab -> Site collection quotas and locks -> Check if the site is locked and change status to not locked and see next time if expiration policy works or not.

If you have any questions/queries, do let me know, I would be try my level best to answer those.  

No comments:

Post a Comment