none
Sharepoint site frozen RRS feed

  • Question

  • Hi, I need some urgent help. I was customizing our Sharepoint 2010 site, and I suddenly realized that no changes can be made to the site. Including, -Adding a library -Editing the name of a library -Deleting content -Uploading a file Which means, it cannot be updated. I am in a little bit of a situation as this is the live site I am updating. Please help me. This is the error I get Error Exception from HRESULT: 0x80131904 Correlation ID: {569ec6a177-4718a229-6bf8f586f248} Please help.
    Ashanjen
    Wednesday, November 30, 2011 6:57 AM

Answers

  • Hi guys,

    After looking at the ULS logs, we realized its something to do with the db space. We were running on SQL Express and it has a limitation (in my case 8 GB) and we upgraded to MS SQL Server 2008 R2 and now everything's back to normal. Thanks for taking your time to reply to my question.

    Best.

     

    AJ


    Ashanjen
    Friday, December 2, 2011 8:45 AM

All replies

  • Hi,

    I need some urgent help. I was customizing our Sharepoint 2010 site, and I suddenly realized that no changes can be made to the site. \

    Including,

    -Adding a library

    -Editing the name of a library

    -Deleting content

    -Uploading a file

    Which means, it cannot be updated. I am in a little bit of a situation as this is the live site I am updating.

    Please help me. This is the error I get,

    Error Exception from HRESULT: 0x80131904 Correlation ID: {569ec6a177-4718a229-6bf8f586f248} Please help.

     

    thanks.

     

    AJ


    Ashanjen
    Wednesday, November 30, 2011 6:58 AM
  • It might help us if you can tell us what you customisation you were doing.  I'm guessing it's not possible to "undo" those customizations?
    PT_UK http://redmanta.co.uk/blog Twitter: @RedMantaUK MCTS:WSS,MOSS,2010 MCITP:2010.
    Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.
    Wednesday, November 30, 2011 7:58 AM
  • Hi,

    Thanks for the reply.

    I was only creating some extra sites and migrating documents in a proper structure. Yesterday I copied a library using the explorer view (A simple copy paste) from and existing library to a new one in a new site in the collection (thats when it got this issue).

    I gathered that this could be a problem occurred due to exceeding the database limit, but I am not quite sure if an issue like that would cause the site to throw an exception even when I try to rename a document or a library.

     

    This is the common error to all the blocked operations.

    Exception from HRESULT: 0x80131904

    Please do suggest a solution.

    Thanks.


    Ashanjen
    Wednesday, November 30, 2011 8:10 AM
  • Wednesday, November 30, 2011 1:35 PM
  • Hi Ashanjen,

    When I have seen the error:  HRESULT:  0x80131904, it was related to permissions on the Admin Content database.  The clue I found was in the Event Viewer on the SharePoint application server.  There were critical errors with the following message:  

    The EXECUTE permission was denied on the object 'proc_EnumLists' database 'Sharepoint_AdminContent_<guid>', schema 'dbo'.  .  

    You're situation could be different, but I would check the event viewer and let us know if you get a hint there.  

    Also verify you're C:\ drives on App and SQL servers are not full.  This ended up being the problem after hours of searching once or twice....

    -Phil

    Wednesday, November 30, 2011 2:41 PM
  • Hi guys,

    After looking at the ULS logs, we realized its something to do with the db space. We were running on SQL Express and it has a limitation (in my case 8 GB) and we upgraded to MS SQL Server 2008 R2 and now everything's back to normal. Thanks for taking your time to reply to my question.

    Best.

     

    AJ


    Ashanjen
    Friday, December 2, 2011 8:45 AM
  • And thanks for taking the time to come back and let us know the resolution AJ.
    PT_UK http://redmanta.co.uk/blog Twitter: @RedMantaUK MCTS:WSS,MOSS,2010 MCITP:2010.
    Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful.
    Friday, December 2, 2011 8:48 AM
  • This must be coz, you wont be having any space available in your SQL DB. Free up some space, it should work fine.
    SharePoint Specialist, Ashish Ranjan
    Friday, December 2, 2011 9:06 AM