locked
HTTP 500 internal server error RRS feed

  • Question

  • Hi,

    I installed 180 days "Office SharePoint Server Trial with Enterprise Client Access License" on my Virtual machine. Recently, the server was down. After the server was rescued, we still can access all sharepoint web applications including central administration site, SSP and Mysites. But strangely we can't open any newly web application created after rescue and HTTP 500 internal server error was thrown in the browser. Any idea for this problem. Please help me out and contribute your knowledge for this. Thanks a lot for your attention to this matter.

     

    Friday, May 14, 2010 6:41 AM

All replies

  • Hi there.

    Could you please take a look at the WSS log files and see if they contain any useful information when this error happens?

    Hope this helps.

    Regards,

    Magnus


    My blog: InsomniacGeek.com
    Friday, May 14, 2010 8:30 AM
  • Thanks for your reply. I've checked event viewer of Web Server and Application Server and then I didn't see any error messages. :(
    Friday, May 14, 2010 9:44 AM
  • Thanks for your reply. I've checked event viewer of Web Server and Application Server and then I didn't see any error messages. :(

    Ok, thanks. But if you look in the WSS log files, by default located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS   on 32bit Windows,  find out if they say something.

    Regards,

    Magnus


    My blog: InsomniacGeek.com
    Friday, May 14, 2010 9:53 AM
  • Thanks again for your quick reply. I've checked it also and I didn't see any error stated in there. I really lost the way. At first, I thought my trial version is expired, but I can still access to all existing web application including central administration site, SSP and Mysites. I cannot access to new web application created after rescue. By the way, how can I check when "Office SharePoint Server Trial with Enterprise Client Access License" will be expired?
    Friday, May 14, 2010 10:02 AM
  • Did you check with new web application...do onething, create one more new web application and create a site collection. Try this site is open or not?

    Did you check the IIS. Check web application pool is existing or not.

    Keep in touch


    Cheers, Hemendra-MCTS
    Friday, May 14, 2010 10:13 AM
    Moderator
  • Hi,

    Thanks for your reply. I've created other new web application. None of them is accessible. Their respective application pools are also existed in IIS. Actually, none of the settings used in creating new web application is wrong. But I don't know the strange symptom of this problem.

    Monday, May 17, 2010 1:16 AM
  • Hi,

     

    Could you explain how you back up and restore your SharePoint server? Which method did you use?

     

    Please refer to the following article to check whether your steps are correct, if not, please do it again, then check the effect.

     

    Back up and restore an entire farm (Office SharePoint Server 2007)

    http://technet.microsoft.com/en-us/library/cc262412(office.12).aspx

     

    Hope this is helpful to you.

     

    Rock Wang


    Rock Wang– MSFT
    Monday, May 17, 2010 3:40 AM
  • Hi,

    Thanks a lot for your reply. Honestly, I didn't do rescue process. The person who did it already forgets how the server was rescued and what settings are changed. Could you enlighten more ideas about this problem? And I also want to know what services will be stopped after trial period of Office SharePoint Server is over. Thanks again for your attention to my problem.

    Monday, May 17, 2010 3:58 AM