I\'ve spent a lot of time trying to figure out a workaround for this to no avail, so I thought I\'d see if anyone here has an idea.
I\'m using Elmah in my ASP.NET MVC3 a
I was having this same issue, but i wasn't executing base.OnException() anywhere. Another possible solution was to remove this from <system.web>
in my web.config:
<customErrors mode="On" />
If you use Elmah.MVC and want to use custom error pages, just change the below value to true in your Web.config:
<add key="elmah.mvc.disableHandleErrorFilter" value="true" />
This will keep Elmah logging enabled but stop it from trying to redirect to the default error page.
Somewhere your site is trying to navigate to ~/Error and it can't find it because it doesn't exist.
Trying removing or disabling customErrors in your Web.config. I'm willing to be its set to the default of on and redirect to ~/Error
If you want to post your Web.config (omitting any sensitive information) I can probably help. I've dealt with similar issues with Elmah recently.
Don't call the base.OnException(context);
method in your custom error handler that derives from HandleErrorAttribute
. You no longer need it because you have implemented a custom error handling in Application_Error
.
If you use Elmah.mvc, then it will help to change this settings to true:
<add key="elmah.mvc.disableHandler" value="true" />
<add key="elmah.mvc.disableHandleErrorFilter" value="true" />