ELMAH not logging errors in MVC 2 app?

Its short circut logic so it will stop at || RaiseErrorSignal(e) and not evaluate IsFiltered(context) The fact that context. ExceptionHandled is true indicates that you have explictly handled the exception yourself in your code with a try catch block. In this case you need to explicitly tell ELMAH to handle the error as well: catch (Exception ex) { // do something // etc // now tell ELMAH to handle it too ErrorSignal.

FromCurrentContext(). Raise(ex); }.

While it is true that the call to RaiseErrorSignal(e) will skip IsFiltered(e) (if true), this will not prevent the exception from being recorded. RaiseErrorSignal(e) will record the exception via ErrorSignal. FromCurrentContext().

RaiseError(e), if possible. – Nathan Taylor Feb 3 at 3:42.

The call to RaiseErrorSignal(e) will record the error within ELMAH, LogException(e) does not need to be called if RaiseErrorSignal(e) returns true. If ELMAH is properly configured both RaiseErrorSignal(e) and LogException(e) will result in an error being recorded. There are a few reasons for which RaiseErrorSignal(e) could return false, so LogException(e) exists merely as a backup should signaling fail.

If errors are still not showing up in ELMAH then chances are you have a problem with your configuration. Could you please post the relevant parts of your Web. Config so we can have a look?

Namely, please post the section and also your http modules in or (if you're using an IIS7 environment). Update As Erik King pointed out- your connection string 'AppDb' is for Entity Framework. It will not work as an ErrorLog connection string.

If you add a standard connection string to your Web. Config and point the ErrorLog at it, ELMAH should start logging correctly. In case you were unaware- the ErrorFilter HttpModule must be declared after any modules it should filter.In your current Web.

Config if you were to define a filter it would only be applied to the ErrorLog module and not the ErrorMail module.

I've added my web. Config to the original post. – Steven Feb 3 at 4:00.

It looks like your AppDb connection string is an Entity Framework connection string. I don't think ELMAH was written to recognize that format. Try giving ELMAH a standard SQL connection string and see if that works.

Its short circut logic so it will stop at || RaiseErrorSignal(e) and not evaluate IsFiltered(context).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.