I dropped in a simple HTML file and IIS 7 is throwing a 500 error. The error details provide almost no information.
In general, what should be checked if a static HTML file is throwing that kind of error?
5 Answers
HTTP Handler Mappings
Recently, some person had dropped in a wildcard script mapper which was messing things up.
-
This happened to me once - someone added a .html Handler Mapping for the Server Side Include module, although it had not been installed on the server. Aug 18, 2010 at 23:31
500 type errors (internal server error) may happen for many reasons.
among others:
- misconfiguration of the server
- access rights problems
- ...
take a look at this site for a few examples.
Based on my last go-round with a similar problem:
1) Look in the HTTP logs. You will see a "500 mmm nnn" in for "sc-status sc-substatus sc-win32-status" in the HTTP logs. A "net helpmsg nnn" from the command line may give you results.
2) Add in Failed Request Tracing to your installation, then use an appropriate rule. The XML results may or may not be helpful.
3) If you think this is a security issue, turn on file object auditing in the policy for that server, then set the auditing for the directory and the files within it to have all failures for "Everyone." Check the Security section of the Event Viewer.
4) Try Process Monitor (not Process Explorer). Run Process Monitor for three or so seconds, just long enough to get your request in, and have it fail. Use Failed Request Tracing to get the process ID that failed. Use Process Monitor's filter to show only events where the process ID appears -- you can then see where it fails.
The Event Viewer should give you the reason why your getting the 500 error, it normally provides much more detail regarding the exception or configuration issue.
Another quick thing, depending on the browser you are using ensure that you have "Enable Friendly Error Messages" unchecked in the advanced options (for IE). This can mask errors from the server.
Just to add to this as a possible solution, had a client who was using an ISAPI filter, but there was no isapi filter anymore in the specified location. There was no Event Log, sc-winsubstatus had a value of 2(could not find file..) So check the ISAPI filter as well.