Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When running classic ASP application in IIS7, when would a 500 error happen rather than a 500.100 error? What I mean is that a 500 error occurs but not a 500.100 error. I am under the impression that classic ASP would only throw 500.100 errors when error occurs in it’s VBScript code.
Some explanation through an example would be very helpful.
Classic ASP has always returned a
500.100status if there is a script error. It’s been like for a very long time in previous versions of IIS and the behaviour hasn’t changed.If you want to catch Classic ASP script errors and be able to read the
Server.GetLastError()object in your custom error page (say for logging) you need to provide a handler specifically for500.100.If you don’t specify a custom
500.100error then IIS will fall back to your custom (or its own)500error page butServer.GetLastError()won’t provide any useful information about the error.