(DNN 4.9.5 on IIS 6.0 & ASP.NET 3.5)

This might not be a DNN configuration issue, but if anyone can give me some pointers I would be grateful.

I have set up web.config to send errors to ErrorPage.aspx, as follows:

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

For some errors (e.g. SQL Server not available) the request is being redirected to ErrorPage.aspx. However there are certain errors where this is not happening:

• The URL is not redirected (remains on requested page)
• A plain text error appears, like this:

500 Server Error
An error occured during processing : if possible, check the event log of the server
Administrators : Obtain more information by changing to debug mode and switching custom errors off in the configuration.

This is not the ASP.NET "yellow screen" - it is just a few lines of unformatted text. Below the above lines the actual error is exposed, which is not good from a security point of view. In my case it is a "The process cannot access the file ..... because it is in use by another process" error. This is due to a mistake I made in coding an HTTP module, which I have fixed, but I am concerned that the error is not being handled in a secure and user friendly way.

Does anyone have an explanation and/or workaround?