Elmah is not triggering when custom errors is enabled

Question

When I have my custom errors disabled, Elmah is taking all exceptions that occur and logging them into my database and emailing me.

However, the second I change my web.config to:

<customErrors mode="RemoteOnly" defaultRedirect="~/Home/Error">
</customErrors>

Elmah stops functioning. It no longer logs exceptions to the database or anything, all I see is my custom error action being executed.

How can I have custom error messages and still have elmah log exceptions? I am currently not doing any other exception intercepting besides Elmah.

score 19 · Accepted Answer · edited May 23 '17 at 11:52

19

Figured it out!

The reason this was occurring was because I had filters.Add(new HandleErrorAttribute()); in Global.asax. I don't know why this is there, but that was what was causing this to fail when custom errors was enabled. Removing this line caused Elmah to work properly with custom errors.

Also, telling elmah to log "handled" errors also works, as described by this answer.

I don't truely know the full ramifications of either option though.

edited May 23 '17 at 11:52

Community

1
1

answered Oct 12 '11 at 03:38

KallDrexx

27,229
33
143
254

If you have just one "generic" error page for all errors, you don't need a HandleErrorAttribute added, and so can remove it as you have. – Matt Roberts Nov 20 '12 at 15:15
2

Removing the standard filter seems to stop the web.config custom error redirect. Telling Elmah to log "handled" errors is definitely the better solution. – Owen Mar 01 '13 at 12:45
@owen how do you tell ELMAH to log handled exceptions? – Tim Murphy Mar 17 '15 at 02:44
Read KallDrexx's answer – Owen May 22 '15 at 10:21

Elmah is not triggering when custom errors is enabled

1 Answers1