So what happens if an error occurs?

The most likely scenario is that you have an error in the error handler in which case you get a standard ASP.Net error behavior that's virtually undistinguishable from the original error. THe easiest thing to do is set a break poin t the first line and see if it gets there.

Also make sure you haven't implemented a Page_Error on the page in question, which will override Application_Error.

If Application Error is not firing it's most likely because you've changed the name of the class or somehow don't have the event handlers hooked up.
Make sure you haven't renamed the class because this is autowired by the ASP.Net runtime.

Hope this helps,

+++ Rick ---


>Hi Rick.
>
>>AS you've already found out the place to do this is APPLICATION_ERROR in your global.asax file. This method gets routed each error and you can then look at each type.
>
>As far as I can tell, for some reason, none of the code I've placed in my Application_Error method is getting called, even after specifying it as my HttpApplication.Error event handler. Don't know why.
>
>>It's quite useful actually as you can selectively decide what to do with errors - you can ignore them, clear them and display another page (most common scenario) and of course it's also your hook to log and email error information.
>
>Which is exactly why I'm trying to get this hooked up. We're doing this app that the client intends on maintaining going forward, and they're really going to need some kind of logging mechanism so they can do a post-mortem on an error.
>> does it regardless of the RemoteOnly setting in web.config - so I can see what's wrong remotely without editing web.config.
>
>Hey, that's pretty slick.
>
>>If this sounds interesting you can take a look at the intefaces of these classes in the West Wind Web Store Documentation:
>
>I'm on my way now...
>
>Let me know if you can think of any reason that my Application_Error code isn't being triggered by an unhandled exception.