Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

enter image description hereEventID 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

share|improve this question
    
Couple ideas: Do you have anything else that could be running at the same time and changing the document? Is it possible a workflow ran on the document at those two times? I believe the expiration policy calculator is run whenever a document is updated. Also, are you editing the document within the Date Calculator besides just returning a date? –  xdhmoore Mar 10 '12 at 0:52
    
There are no workflows on any of these document libraries. –  Mike Mar 13 '12 at 15:59
    
Ironically, some if not most of them are when they get posted. So if the document is posted at 3:15, there is an error in the event viewer of the above that matches it. –  Mike Mar 13 '12 at 15:59
    
Is the DateCalculator function changing the document? Is it possible that the user is editing the document in office or another application immediately after posting it? –  xdhmoore Mar 13 '12 at 16:13
3  
We have a workflow that runs when a document is updated, and we occasionally see an error like this when a user checks out the document shortly after uploading it. (we should have broken into an event handler so that part of it could be synchronous.) I don't know if this could happen with a date calculator or not, but it definitely could if you are directly changing the document in the date-calculator, which would not be recommended. –  xdhmoore Mar 13 '12 at 16:40
show 15 more comments

2 Answers 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.

share|improve this answer
    
but that many times? I don't have any custom code for these lists, so I'm not performing the web.AllowUnsafeUpdates = true –  Mike Jan 30 '13 at 18:37
    
That was just for reference, what I mean is that somehow your job is running twice or more, custom code or not. –  F.Aquino Jan 30 '13 at 19:20
    
Mike do you have any way of checking to see if there are 2 updates happening at the same time? Do you have access to sql logs or monitor? –  ghangas Feb 1 '13 at 16:14
    
I updated my question to include the logs on the time of the incident –  Mike Feb 1 '13 at 20:09
    
Whether you agree with F.Aquino or not it is very likely that you have one of a couple problems that present the same: stackoverflow.com/questions/7094424/… 1. You are updating a cached item when the original has been changed 2. You are updating a read only field 3. You have a race condition and something quicker is updating simultaneously Perhaps a short delay and then retrieve a fresh object before trying to update it will be sufficient. –  ghangas Feb 4 '13 at 16:32
show 1 more comment
up vote 0 down vote accepted

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"

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.