Cannot Update One Site After Patches (delete, save, create).


  • Patched the SharePoint 2010 Foundations Server and the SQL Server yesterday and now one of my SharePoint sites has quit working.  It won't allow me to delete or create list items.  When viewing items it looks normal, but has some fields that say "unable to rendor item".

    I honestly don't even know where to start looking to determine where things are breaking down, but I want to be careful because I have other SharePoint sites that are working just fine.  The only difference I can think of is that this one was truly created in 2010.

    Any advice?

    Delete Error: The server has encountered the following error(s): Cannot complete this action. Please try again.

    Save Error: The server has encountered the following error(s): Cannot complete this action. Please try again.  Correlation ID:

    Saturday, March 17, 2012 4:04 PM

All replies

  • Hi,

    You can try and find out more about the error if you hunt down the lines in the log files that contain that correlation ID.

    One way is to use the SharePoint management shell (PowerShell) and to issue a command like this:

    Get-SPLogFile | ? { $_.CorrelationID -eq '52f25762-1590-4e17-adc7-00971e6fae5f' }

    If you want to speed things up, you can specify a start time and end time to search within:

    Get-SPLogFile -StartTime 09:00 -EndTime 10:00 | ? { $_.CorrelationID -eq '52f25762-1590-4e17-adc7-00971e6fae5f' }

    This might shed some light on why.

    Hope this helps!


    Joel's SharePoint Architect Blog
    Want SharePoint Training?

    Saturday, March 17, 2012 9:54 PM
  • Hi,

    Following Joel's suggestions you basically have to starg troubleshooting till you get more clues. Two most common places to troubleshoot SharePoint are Windows Event Logs (mostly the Application logs) and ULS Logs. A great tool to easily browse through ULS logs are ULS viewer which can be downloaded from here:

    Another hunch. By any chance if the site got changed to read only not letting you edit or delete but showing your content in read only mode. Please check if the database got converted to read only mode by going to SSMS.

    Also, please check if by chance the web application has gotten into a readonly state. For checking this, go to the SharePoint root folder (hope you know what this is, corresponds to 12 hove of the MOSS 2007 days) and run the stsadm tool.

    stsadm -o getsitelock -url "Your webappliacations url" will get you the current status of the webapplication. By any chance if it has become readonly, it will show you an outout suggesting that.

    For changing that to the normal default state, use:

    stsadm -o setsitelock  -url "Your webappliacations url" -Lock none

    Thanks, Soumya | MCITP, SharePoint 2010

    Saturday, March 17, 2012 11:35 PM
  • Unfortunately, the logs come back with nothing at all.  I even generated the error a couple more times and used the new Correlation ID, to no avail.
    Sunday, March 18, 2012 1:31 AM
  • Hi,

    How about the read only test? The one to be performed with stsadm?

    Thanks, Soumya | MCITP, SharePoint 2010

    Sunday, March 18, 2012 3:52 PM
  • The command said that there were no locks, but your theory matches everything that I'm seeing.  I was able to narrow it down to determine that it is a particilar list on the site that is read-only.  

    Is there a way that someone could have accidentally marked it as "checked out" and the command above not show it?

    Sunday, March 18, 2012 6:17 PM
  • Check your library settings and the 'Manage files which have no checked in version', perhaps you will find something there...?

    If all else fails, try to either export the entire site using Powershell and importing to a new location(test to see if it works when 'recreated') or, save the site as template and recreate it.


    Thomas Balkeståhl - Technical Specialist - SharePoint -
    Download the SharePoint Branding Project here

    Sunday, March 18, 2012 7:00 PM
  • That's the only thing I found that worked (recreate and copy data).  Now I'm working on verifying workflows and custom pages.  Sad day.

    Sunday, March 18, 2012 10:17 PM