Setting a Major Version Limit on a Library With a Large Number of Items Causes System to Become Unresponsive When An Item Is Updated
Hi, Thank you for your question. I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience. Thank you for your understanding and support. Regards, Xue-Mei Change TechNet Subscriber Support in forum If you have any feedback on our support, please contacttnmff@microsoft.com.Xue-mei Chang TechNet Community Support
August 18th, 2012 5:16am

I had a document library with unlimited versioning enabled and frequent updates to a couple documents. In the interest of better space management I set the Major Version Limit to 25. There were 250 versions of one 13 mb document. When the first update to that document occurred this morning, the system became unresponsive for all users for a number of minutes until all current users recieved the ever helpful "An error has occurred" page. During the unresponsive period there was no significant resource usage on the front end server or database server. CPU below 10% and no paging on both servers. I "successfully' recreated the condition on my test server which has a recent copy of the production data. There are no relevaant Application or System Event Log entries on any production or test servers. Environment: 64 Bit Server 2003 R2 MOSS 2007 SP3 [Microsoft.SharePoint.DLL version 12.0.6608.1000] SQL 2008 19.0.5500 David McKenzie
Free Windows Admin Tool Kit Click here and download it now
August 18th, 2012 4:47pm

Hello, Any update?David McKenzie
September 1st, 2012 4:20pm

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

Other recent topics Other recent topics