Classic ASP always returns 200 in IIS7

Question

I have enabled tracking in IIS7. I set these properties to true on the ASP tab of the IIS management tool:

• appAllowClientDebug,
• appAllowDebugging,
• errorsToNTLog,
• scriptErrorSentToBrowser;

To test this, I wrote a small classic ASP test page in which I voluntarily include an error (bad activeX name).

My asp test page is displayed until an error is reached. The rest of the page is not displayed. I expected a 500 error code, but the code is always 200. There is no error file in the FailedReqLogFiles folder.

Any idea of ​​someone?

Answer 1

OK, I think the problem is that using "Allow server-side debugging". You may have turned it on, but turned it off instead.

The server thinks it should start debugging and is trying to start the debugger, and then it will not find it and just give up! I am sure this did not happen before IIS7.

Answer 2

The morning sun

This problem significantly slowed down our development, because sql server errors did not appear in the browser. Our application service provider tried some settings, but could not get it to work. They sent me the settings, and I accidentally did just two times, and our problem was fixed. They told me that asp instead of an error code returned 200 code instead.

Here's what worked for us:

The combination "Send to browser = True" and "Enable debugging on the server side" = False is used.

I hope this helps others.

Tom Armstrong

Answer 3

Take a look at this and see if you can get a 500 error. Also, if the error is handled by an exception handler in ActiveX, you may not see the error in the asp response.

http://classicasp.aspfaq.com/general/why-do-i-get-a-500-internal-server-error-for-all-asp-errors.html

200 OK is the standard response for successful HTTP requests. A status code indicates that the client request has been successfully accepted, understood, and accepted.

Answer 4

We had the same IIS7 error. He did not return any errors. The error message did not appear on the screen and there was not 500. The page just stopped rendering.

Is that what you see? I cannot remember that it was, unfortunately, I think it was like something was handling the error. (If this is what you see, I will continue to try to remember!)

I don’t think this is so, but it could be: go to the error pages> Change the parameter settings (hidden in the right panel) and select "Detailed error"? This parameter is also required, and you did not mention it.