Home/ Questions/Q 6391259
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T03:39:00+00:00

I know it’s possible in asp.net to create a custom error page in a

  • 0

I know it’s possible in asp.net to create a custom error page in a web app, by putting the following line in the web.config:

<customErrors mode="RemoteOnly" defaultRedirect="frmErrorPage.aspx" />

I have had to do this for my web app, since it is clearly much tidier than letting the program bomb out with it’s ugly default error page. My custom error page just has the customer’s logo and a brief message saying “Error has occurred. Please return to homepage”

The trouble now is that I have no way of knowing what caused the error, when a customer reports it.

Is there a way to make the actual error message appear on this custom error page too?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should be using logging to know when/where/what errors occured. The POINT of the custom error page is to not allow the end user to see why it messed up because obviously that could be a security risk. Look into using ELMAH. It automatically creates a nice web gui for any uncaught exceptions. And you can also create logs when you catch the errors yourself.
    If you do chose to use ELMAH, I would also strongly recommend installing it with the NuGet package manager

    • 0