I enabled tracing in IIS7. I set those properties to true in the ASP tab of the IIS management tool:
- appAllowClientDebug,
- appAllowDebugging,
- errorsToNTLog,
- scriptErrorSentToBrowser;
To test it, I wrote a small classic ASP test page in wich I voluntary include a bug (bad activeX name).
My asp test page is rendered until the bug line is reached. The rest of the page is not rendered. I was expecting a 500 error code, but code is always 200. There is no error file in the FailedReqLogFiles folder.
Any idea someone?
OK, i think the issue is actually with Enable Server Side Debugging. You may have it enabled, but you should disable it instead.
The server thinks it should start debugging and tries to fire up a debugger, and then doesn’t find one and just gives up! I’m sure this never happened prior to IIS7.