locked
Problem with Sharepoint lists after backup restore. RRS feed

  • Question

  • Hi 

     I do not know if this is the correct place to post about Sharepoint restore problems. Last week we had server hardware crash, we tried to restore almost everything. Now I have problem with Sharepoint lists. We had a big sharepoint environment with WSS3.0 which has around 200 sharepoint sites and many custom lists and custom webparts. After restoring the sites and content DB from backup, we have the sites working but our custom lists forms are not working. When I create a new element in blog or any list, sharepoint fails with unexpected error occured and I don't see any information in the sharepoint logs and application logs. I read in internet that Feature definitions are saved in the configuration DB so I uninstalled all features and installed them, still I have the same problem. Any one please help.

    I thought its because of my custom webparts and removed from page, but still I have the same problem. Whats causing the problem and why sharepoint is not logging.

     

    We have the same server name as well.

     

    Any ideas would be appreciated. 

    Thanks in advance.

    Aruna

     

    Thursday, November 3, 2011 2:07 PM

Answers

  • Hello,

    Appearntly you have rebuilt the SharePoint Server and are missing applying some customization which was present earlier.

    To get more information out of "unexpected error" please do the following changes to the web.config file of the web application hosting the SharePoint site. Default location would be "C:\inetpub\wwwroot\wss\VirtualDirectories\<PortNo>\"

    Open the web.config and
    1) Search for "stack"; you'll find CallStack="false", change the value to "true".
    2) Search for "customerrors"; you'll find <customErrors mode="On" />, change the value to "Off"

    Please note the case is important in both above values.

    Now again try to create a new element in blog or any list, you'll see more descriptive error which will give you more clues on the cause of failure. You could post that error here if you are unable to zero down on a cause.


    Please remember to click 'Mark as Answer' on the post that helps you or click 'Unmark as Answer' if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Regards,
    Nishant Shah
    Microsoft Online Community Support
    Wednesday, November 9, 2011 10:20 AM
    Moderator