none
This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying. For more information about HTTP errors, see Help

    Question

  • When i m trying to open sharepoint site i m getting the error below..

    I was getting an Error-404 after deploying some webpart trying to resolve this i wen to iis and tried to change the error 404 options and ended up with the error below..How to resolve this...

    This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying.

    For more information about HTTP errors, see Help

    Wednesday, December 26, 2012 8:36 AM

Answers

  • Hi Reddy25

    When you deploy a web part , the web.config is automatically backed up in the web application directory . Check the latest back up what has changed .  Reset the IIS and see if that fixes the issue . Also , even though this is trivial, please validate whether the app pools are running and that the application web site is running in IIS .  Your last resort will be to check in IIS logs and Sharepoint ULS logs to see if you can find anything . 

     

    Wednesday, December 26, 2012 9:20 PM

All replies

  • Check if you have a backup of your web.config file and verify what has any change after your IIS update. Revert that line alone.

    Also look in the Windows event logs on the server for more information.

    P.S. Make a backup of your web.config before modifying anything. 


    --Cheers


    • Edited by Prasath C Wednesday, December 26, 2012 9:26 AM
    Wednesday, December 26, 2012 9:25 AM
  • Unable to identify wat exactly wnt wrong...I dont have any backup..Is ther any other way to solve this error...
    Wednesday, December 26, 2012 12:57 PM
  • Hi Reddy25

    When you deploy a web part , the web.config is automatically backed up in the web application directory . Check the latest back up what has changed .  Reset the IIS and see if that fixes the issue . Also , even though this is trivial, please validate whether the app pools are running and that the application web site is running in IIS .  Your last resort will be to check in IIS logs and Sharepoint ULS logs to see if you can find anything . 

     

    Wednesday, December 26, 2012 9:20 PM
  • Hi Reddy25,

    We can also create a new web application, get the web.config from this new web application. And then, please compare the corrupted web.config to this new web.config, and fix the error we may have did in the web.config.

    If this is still not helpful, please create a new web application to use the original database.

    Thanks,
    Jinchun Chen


    Jinchun Chen(JC)
    TechNet Community Support

    • Proposed as answer by FAISAL FAHD Monday, January 07, 2013 11:14 PM
    Thursday, January 03, 2013 7:50 AM