ASP error messages nested on with IIS 6.0

When an HTTP 500.100 occure in IIS 5.0, I was getting redirected to a
HTTP 500.100 - 'page cannot be displayed' error page when there was an
error, but now in IIS 6.0, I get 'Microsoft VBScript runtime error
'800a01c2' ' nested within the page.


I'm trying to create my own error messages so it will re-direct to my
own error page and send me an email. I used to be able to do this in
IIS 5.0 but I can't seem to get it going in IIS 6.0 as it doesn't
re-direct to a default error message.

Anyone know how to get IIS 6.0 to work like IIS 5.0, or is there
another way of doing it, or is this not even an IIS problem!

Any help would be great!

Ken
Wed Jun 28 23:46:36 CDT 2006

IIS 6.0 works the same way as IIS 5.0 in regards to custom 500.100 error
handling. Just ensure that the custom error page you have defined is in the
same web app pool as the page where the error is being raised from. If you
custom error page is an ASP page, ensure the type is set to "URL"

And lastly, ensure that you have buffering turned on for your pages (which
is the default), so that you don't have part of the original file sent to
the client, and then the 500.100 page kicks in.

Cheers
Ken


"Lambuz" <lambu76@gmail.com> wrote in message
news:1151506745.711841.227620@y41g2000cwy.googlegroups.com...
> When an HTTP 500.100 occure in IIS 5.0, I was getting redirected to a
> HTTP 500.100 - 'page cannot be displayed' error page when there was an
> error, but now in IIS 6.0, I get 'Microsoft VBScript runtime error
> '800a01c2' ' nested within the page.
>
>
> I'm trying to create my own error messages so it will re-direct to my
> own error page and send me an email. I used to be able to do this in
> IIS 5.0 but I can't seem to get it going in IIS 6.0 as it doesn't
> re-direct to a default error message.
>
> Anyone know how to get IIS 6.0 to work like IIS 5.0, or is there
> another way of doing it, or is this not even an IIS problem!
>
> Any help would be great!
>