Problem displaying custom error page in ASP.NET MVC 2

Question

This is customErrors section from my web.config file

<customErrors mode="On">
  <error statusCode="500" redirect="HTTP500.aspx" />
</customErrors>

HTTP500.aspx is the same as standard /Views/Shared/Error.aspx page.

When I get HTTP 500 error I see this page:

Server Error in '/' Application.

Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.

But when I change the above customErrors section like this:

<customErrors mode="On">
  <error statusCode="500" redirect="HTTP500.htm" />
</customErrors>

then HTTP500.htm page is displayed when HTTP 500 error occurs.

Why HTTP500.aspx page isn't displayed?

Peter Ruderman · Accepted Answer · 2010-05-07 21:12:39Z

1

I suspect its a problem with your routes. You may be mapping HTTP500.aspx to a non-existant controller method.

answered May 7, 2010 at 21:12

Peter Ruderman

12.6k1 gold badge41 silver badges59 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

robert_d Over a year ago

I have only default routes. I didn't add any routes.

Peter Ruderman Over a year ago

Then this is your problem. When you ask IIS for a .htm file, it just serves it up (assuming you have appropriate permissions). When you ask it for an .aspx file, it routes it to the .NET framework. MVC then tries to map the request to a controller and method in your application, at which point it blows up.

Mr47 · Accepted Answer · 2011-05-24 11:14:20Z

0

Have you tried the following?

routes.IgnoreRoute("HTTP500.aspx");

edited May 24, 2011 at 11:14

Mr47

2,6651 gold badge20 silver badges26 bronze badges

answered May 23, 2011 at 22:06

adamclerk

7691 gold badge6 silver badges16 bronze badges

Collectives™ on Stack Overflow

Problem displaying custom error page in ASP.NET MVC 2

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related