IIS 7 & IIS 8
Trying to show a web form using IIS for the first time
Last post Apr 18, 2012 12:52 PM by lextm
Apr 02, 2012 01:54 PM|LINK
I created a web site application on Visual Web Developer 2010 Express. I added a web page. I tried to start the web page, but I get an HTTP 500 error. I can't run as debug. There's nothing wrong with the code itself. It's basically a simple label showing
the current time. Did I not set up my IIS correctly? I have the following features turned on
IIS/Web Management Tools/IIS Metabase and IIS 6 configuration compatibility
IIS Management Console
IIS/World Wide Web Services/ASP.NET
IIS/World Wide Web Services/Common HTTP Features/Default Document
IIS/World Wide Web Services/Security/Request Filtering
Apr 03, 2012 02:53 AM|LINK
You need to paste all details provided in the 500 page. Or before doing that, learn about IIS/ASP.NET breaking changes if you are using .NET 2, in case you hit any of them,
Apr 03, 2012 02:09 PM|LINK
I don't think this answers my question. I wasn't migrating my project. I was simply creating a quick-and-dirty practice project.
Apr 04, 2012 12:20 AM|LINK
Apr 07, 2012 12:10 AM|LINK
Apr 07, 2012 01:00 AM|LINK
First, please disable friendly error page in IE,
Apr 11, 2012 01:56 PM|LINK
Apr 12, 2012 05:57 AM|LINK
Thanks. That usually means it may not be IIS who responded with this 500 error page.
Can you learn about Fiddler and use it to capture the conversation between IE and IIS? http://www.fiddler2.com/fiddler2/
Though it seems to be an empty page in browser, the HTTP response (contains headers and contents) should contain more information about who responded. Paste the raw response here, and we may see what is the cause.
Apr 18, 2012 01:39 AM|LINK
Is this what you're looking for?
Apr 18, 2012 12:52 PM|LINK
No, it isn't. When you see this list in Fiddler window and click on one of the row, you should see in the right hand side the panels for request and response message. Their Raw tabs can show you the raw bytes sent/received in HTTP packets.
Navigate in the list to the 500 error one in the left, and then see how the raw response message looks like (and paste it here). That might reveal the cause of it.
Well, if you can afford, open a support case via http://support.microsoft.com.