Ken Schaefer

I just wondered if anyone else had encountered  the following  problem with service pack 2.

Any non existing webpages with an .asp extension are being processed by iis as 500 errors rather than 404 errors.

For most people this would not be an issue, but one of my sites it caused a bit of grief as we needed to deal with those 2 errors differently. Uninstalling service pack 2 resolved the issue.

Hi Nicholas,

Have you configured a custom error page for 404 errors? Perhaps your custom error page itself is having a problem, causing a 500 error to be generated?

Cheers

Ken

Nope no custom 404 page. Have you heard if anyone else has had this problem or is it just me. I have seen it on 2 different servers now.

Sorry Nicholas - I've seen no other reports of this behaviour.

Are you saying that when a non-existant ASP page is requested a 500 Internal Server Error actually occurs? Or just that your custom 500-100 error handler is invoked (but there is no real error)?

Hi I'm experiencing the same problem. After we applied the service pack all 404s stopped working. With classic asp, htm and html it just displays a 500 message. Asp.net works ok as long as you set it up in web.config as normal. Does anyone know of a workaround. BTW We use the Helm Hosting Control Panel I'm not sure if that makes a difference.

PingBack from http://www.rimonabantexcellence.com/t.php?aHR0cDovL3d3dy5hZG9wZW5zdGF0aWMuY29tL2NzL2Jsb2dzL2tlbi9hcmNoaXZlLzIwMDcvMDMvMTMvMjM4OC5hc3B4