2

I am working on an ASP.NET MVC 4 in C# project which works very well on my local development server. However, when I push it to my production server, a particular page gives a 500 internal server error. However, the error I get is no more helpful than "An error occurred while processing your request".

How can I force ASP.NET to display a more helpful error, even if it is the yellow screen of death?

Thank you for your time.

Improve this question
3
  • possible duplicate of Custom ASP.NET MVC 404 Error Page Commented Apr 25, 2014 at 15:39
  • 1
    Look at the Event Viewer and see if you can find anything in there... Commented Apr 25, 2014 at 15:41
  • Try to add a global error handler with logging capabilities Commented Mar 25, 2015 at 17:29

1 Answer 1

Reset to default
2

Yes, there's a Yellow Screen of Death. You can force it to display the error by going to the Web.Config file and making sure that you have this line:

<system.web> <customErrors defaultRedirect="GenericError.htm" mode="Off"></customErrors> </system.web>

BUT be very careful NOT to leave it like this after you figure out the issue. It is BIG a security risk to display full stack traces of errors on a Production box.

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

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.