Home/ Questions/Q 7559233
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-30T12:35:13+00:00

Okay, I think I’ve ready every post on StackOverflow regarding this and still no

  • 0

Okay, I think I’ve ready every post on StackOverflow regarding this and still no luck.

I’ve confirmed in my global.asax that the HandleErrorAttribute filter is being registered.
I’ve set customErrors mode="On" in my web.config.
I’ve changed Layout=null to Layout="~/Views/Shared/_Layout.cshtml" in my Error.cshtml file.

I then added a throw Exception() in my Account controller’s Index action and browse to localhost:5050/Account/Index but I wind up with the standard YSOD error stack stuff.

I’ve even tried the following (although from my understanding it shouldn’t matter):

  1. Add [HandleError] and [HandleError(View="Error")] to my controller.
  2. Add defaultRedirect="Error" to my customErrors in web.config

What else can I do? Is there a way to tell what’s going on in the HandleError filter or to tell if the Error View is being generated at all?

Thanks for your help.

P.S. Incidentally, I’m using VS2010, IE9 & Chrome

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Okay, ignorance is not always bliss … sometimes being ignorant is just plain frustrating!

    It turns out I was editing the web.config located in my Views folder instead of the web.config for my site like I thought I was.

    Once I added customErrors mode="On" to my real web.config, things worked great.

    Thanks to everyone that tried to help.

    • 0