So I'm currently trying to get my custom errors to work but when doing so I get the following error:
Server Error in '/' Application.
Runtime Error
Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.
In the event viewer, the only exception happening is the standard database connection error exception but I need to show a custom error page when this happens (even if it's a static html page without using a controller).
This is the custom errors tag in web.config under < system.web >
I had used the httpErrors object under system.webServer previously, the responseMode="File" was the only difference which has successfully redirected it to my HTML file, however, that then gives me the following message "The page cannot be displayed because an internal server error has occurred.".
I am just using a default HTML template as the page, so nothing that could be causing a further error, so I believe the database not connecting is preventing the static error page from displaying:
Render custom errors when database cannot connect
So I'm currently trying to get my custom errors to work but when doing so I get the following error:
In the event viewer, the only exception happening is the standard database connection error exception but I need to show a custom error page when this happens (even if it's a static html page without using a controller).
This is the custom errors tag in web.config under < system.web >
Error controller:
I have this under
<system.webServer>
where the key part I believe isexistingResponse="Replace"
Regards, Magnus
I had used the httpErrors object under system.webServer previously, the responseMode="File" was the only difference which has successfully redirected it to my HTML file, however, that then gives me the following message "The page cannot be displayed because an internal server error has occurred.".
I am just using a default HTML template as the page, so nothing that could be causing a further error, so I believe the database not connecting is preventing the static error page from displaying:
is working on a reply...