CODEWITHSUNDEEP
c#asp.netwindows-server-2008
Blankman
Blankman

Reputation: 267310

Seeing a generic 500 internal error, how to view detailed error?

On my production server, I just deployed a asp.net web application.

I am seeing a generic '500 internal server error'.

How can I view a detailed error temporarily until I fix the problem?

I already have:

<customErrors mode="Off" defaultRedirect="error.aspx"/>

Upvotes: 2

Views: 1705

Answers (3)

Jared Shaver
Jared Shaver

Reputation: 1339

If the error page is coming from IIS because of some configuration being incorrect, you can try using Failed Request Tracing.

Upvotes: 1

Tomek
Tomek

Reputation: 3279

Change IIS Error Pages feature settings to "Detailed errors" or try to run the app from the server where it's deployed.

Upvotes: 2

Darin Dimitrov
Darin Dimitrov

Reputation: 1039438

<customErrors mode="Off" /> is usually enough. But if you have messed up with some IIS configuration it won't even reach your web.config which might explain why you are seeing this generic 500 error message. Take a look at the Event Log (eventvwr.msc) of the server which might contain additional information about the error. There could really be lots of possible reasons (.NET framework misconfiguration, application pool or virtual directory misconfiguration, missing access rights to some folders, ...)

That's the reason why you should have a staging server which has the same configuration as your production server - it would allow you to test your configuration before shipping.

Upvotes: 3

Related Questions