Error HTTP 500 - Internal Server Error - ASP Errors


Common elaboration error returned by the webserver.

Error Message

English Error Message

HTTP 500 - Internal Server Error

Error HTTP 500 - Internal Server Error

The message HTTP 500 - Server internal error is without a doubt one of the most hated errors by anyone who comes close to the world of server side languages, especially amongst developers.

Why? Simple, because in reality it says all and nothing and often it contributes to create panic amongst the users.
Let’s see how it is possible to change this message, definitely user unfriendly, in another, more understandable one.

The code http of this error, HTTP 500, is generated by the webserver when an elaboration error has prevented the correct completion of the request.
The error is very generic and so it is basically impossible to understand the problem from this message.
In addition, Internet Explorer in predefined mode hides the details of the error giving the user a melancholic note.

Here is an example on how the error HTTP 500 with the Internet Explorer browser shows.


How to Fix the Error

Luckily it is possible to obtain more detailed information on the nature of the error, which will be useful in order to be able to make the correction. To see them, all it needs to be done is use a different browser from Internet Explorer or, as an alternative, deactivate the short http error messages by following this procedure:

  • Open the IE configuration panel: Tools > Internet Options
  • Choose the Advance Form
  • At the Explore voice, deactivate the Show Short http Error Messages
  • Apply, close the browser and restart

When visiting the page again, you will now notice an error that, for the great majority of developers, will be definitely be more understandable.
In this way it is possible to read in an unmistakeable way, information concerning the line that generates the error and other contents which are useful to identify and correct the problem.

In our case, here is how the mistake appears:


Having clearer ideas, it is possible to verify the reason of the error, in our case an incorrectly specified route. Let's fix the error and check the running of the page.

It is good practice, even for the users who are not developers, deactivate the generic errors messages, in order to read the errors in a more specific way, and above all not confuse, for example, a not found page (HTTP 404) with an elaboration error.
To view complete messages is also useful for immediately notice the person responsible for a web site that you are visiting about the error, in the case that you come across an error, to allow him to apply the necessary corrections. and are property of Simone Carletti.
Discover my website or visit my Simone Carletti's profile on LinkedIn