Enable detailed error in ASP and ASP.Net

With ASP and ASP.Net script, IIS is configure to disable any error for security concern. If you are in development stage, you could enable them from your web.config file without access to the server/control panel.

By fault, if you hit any error from your ASP/ASP.Net script, you shall receive error 500 Internal Server Error.

First of all, you should enable detailed error from your web.config file. To do this, enter the following command,
<httpErrors errorMode=”Detailed” />

Now, detailed error is enabled but you will found out the ASP/ASP.Net is still showing Error 500, Internal Server Error.To fix it,

For ASP.Net,
Find the system.web section or create it with,
<customErrors defaultRedirect=”errors.aspx” mode=”Off” />

For ASP,
Find the system.web section or create it with,
<asp scriptErrorSentToBrowser=”true” />

Understand ASP.Net custom error

It is very normal when you design your script in ASP.Net and getting some runtime error as attached below when you are designing your script from your local PC and uploaded to the web server.

With the above error, some programmer not even know what to do :S .

Today, MGe will guide you on what is the custom Error type and how to make it work when you are hosted to the web server that do not have the administrator privilege.

Basically custom error used to hide the real error from the script from the visitor, where it might be the sensitive information from your website such as connection string.

The ASP.Net <customErrors /> do have 3 types, such as On, Off and RemoteOnly. In short, may refer to the table as below.

Off Show everyone the detailed error message.  This is rarely a good idea.
On Don’t show anyone the detailed error message.
RemoteOnly Only show the detailed error message if you are testing from the local server where the site resides.

To set it, just open your web.config file and set it from the <system.web>.


<customErrors mode="RemoteOnly" />