COMException
<nativehr>0x81020015</nativehr><nativestack></nativestack>The file FileName.xml has been modified by SHAREPOINT\system on 18 Aug 2014 12:41:01 -0400.
SPException
Save Conflict. Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes
We are facing above two exceptions in following scenarios-
1. While adding/updating the listitem property bag values for document library
2. While adding/updating list item columns for for document library
Please note we have more than one processes are accessing and updating the list items for document library. And we are disabling and enabling event firing before and after update.
Also, Currently We are using SPListItem.SystemUpdate(), to update the list item in document library but if we replace it with SPListItem.SystemUpdate(false), then we are not experiencing exceptions described above. We have understood that passing false parameter in SystemUpdate will not create versions of the list item. However, we want to know that will SystemUpdate with FALSE parameter assure fixing this issue? If not, are there other other alternatives to fix these exceptions?
Another thing, we are not facing the exceptions mentioned above with following SPFile.Update() or SPFolder.Update() as of now. However any one have faced the similar exceptions while updating SPFile and SPFolder?
<nativehr>0x81020015</nativehr><nativestack></nativestack>The file FileName.xml has been modified by SHAREPOINT\system on 18 Aug 2014 12:41:01 -0400.
SPException
Save Conflict. Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes
We are facing above two exceptions in following scenarios-
1. While adding/updating the listitem property bag values for document library
2. While adding/updating list item columns for for document library
Please note we have more than one processes are accessing and updating the list items for document library. And we are disabling and enabling event firing before and after update.
Also, Currently We are using SPListItem.SystemUpdate(), to update the list item in document library but if we replace it with SPListItem.SystemUpdate(false), then we are not experiencing exceptions described above. We have understood that passing false parameter in SystemUpdate will not create versions of the list item. However, we want to know that will SystemUpdate with FALSE parameter assure fixing this issue? If not, are there other other alternatives to fix these exceptions?
Another thing, we are not facing the exceptions mentioned above with following SPFile.Update() or SPFolder.Update() as of now. However any one have faced the similar exceptions while updating SPFile and SPFolder?