Error computing the expiration data for item

Question

EventID 7972 Task Category: Information Policy Management Source: Document Management Server

> 
> Error computing the expiration date for item
> http:///webapp/sites/sitecoll/documentlib/document.rtf
> 
> Error:  The file documentlib/document.rtf has been modified by
> SHAREPOINT\system on 08 Mar 2012 13:51:11 -0600.

It spammed at 1:51pm 5 times, and 3:00pm 5 times. I'm not sure why it happens. My information policy and expiration policy runs at 2am and 3am repectively. It happened this morning also at 7am 8 times, and last night at 9pm, and so on.

UPDATE:

These are the logs associated with the error:

0x81020015The file List/file.rtf has been modified by SHAREPOINT\system on 01 Feb 2013 08:36:37 -0600.

Possible mismatch between the reported error with code = 0x81070901 and message: "The file List/file.rtf has been modified by SHAREPOINT\system on 01 Feb 2013 08:36:37 -0600." and the returned error with code 0x81020037.

Error computing the expiration date for item http://sharepoint/sites/subsite/subsite/List/file.rtf. Error: The file List/file.rtf has been modified by SHAREPOINT\system on 01 Feb 2013 08:36:37 -0600.

Leaving Monitored Scope (UpdateExpireDate.OnEvent). Execution Time=63.1552334165376

Leaving Monitored Scope (Event Receiver (Microsoft.Office.Policy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Microsoft.Office.RecordsManagement.Internal.UpdateExpireDate)). Execution Time=64.022382733001

Answer 1

It MAY have something to do with having the same subject/filename, so SharePoint has to rename the file/post after it has uploaded, as well as (at the same time), execute the expiration date of the content. Maybe two different sessions doing two different things can cause this error...

1. Renaming the file (Session 1)
2. Calculating and updating the expiration date/time (Session 2)

These session may be fighting for the right to edit the post. I'm taking a stab in the dark that this may be it since for each library that has an error, it does have an expiration policy and they both have the SharePoint name change present, for example:

A) Post A posted at 10:00am named "Testing"

B) Post B posted at 10:05am named "Testing" then gets renamed to "Testing 1758"

Answer 2

There is one generic error in SharePoint that will throw

the file xxxx has been modified by SHAREPOINT\system

And that is when you don't have web.AllowUnsafeUpdates = true; But that error is old, really old IIRC.

But the likely reason is that you may be performing more than one update in the same request, so the second update will throw that error because it will think there is another user updating.