W
wardy
Hi All,
I've searched around this group and can't find anyone who has seen/
reported this problem before, so hopefully someone out there can help
me out....I'm using a .NET 2.0 web application with a custom errors
section set to "RemoteOnly" with a redirect to a custom error page -
the goal is to have any unhandled exception gracefully handled and
rendered to the user. However, when my application is hitting this
error, I am not getting the nice error page, but instead am getting a
blank screen, with only the basic html tags...(for any of you familiar
with how a page looks with the .NET ISAPI filters aren't registered,
this is the same output). I can load the error.aspx page
independently and it resolves, but I cannot get it to work through the
custom errors route.
The other perplexing thing is that this works on other servers, just
not this particular web server, so it is likely a configuration
setting somewhere, but I am at a loss as to what it is.
Thanks,
Wardy
I've searched around this group and can't find anyone who has seen/
reported this problem before, so hopefully someone out there can help
me out....I'm using a .NET 2.0 web application with a custom errors
section set to "RemoteOnly" with a redirect to a custom error page -
the goal is to have any unhandled exception gracefully handled and
rendered to the user. However, when my application is hitting this
error, I am not getting the nice error page, but instead am getting a
blank screen, with only the basic html tags...(for any of you familiar
with how a page looks with the .NET ISAPI filters aren't registered,
this is the same output). I can load the error.aspx page
independently and it resolves, but I cannot get it to work through the
custom errors route.
The other perplexing thing is that this works on other servers, just
not this particular web server, so it is likely a configuration
setting somewhere, but I am at a loss as to what it is.
Thanks,
Wardy