getting Runtime error instead of custom errors

  • Thread starter Thread starter Pat
  • Start date Start date
P

Pat

In my Web.config i have :-
<customErrors mode="On" defaultRedirect="genericerror.htm">
<error statusCode="404" redirect="pagenotfound.aspx"/>
</customErrors
to get page not found error but instead i keep getting a RUN TIME error
below:
Any ideas..


Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed.

Details: To enable the details of this specific error message to be viewable
on the local server machine, please create a <customErrors> tag within a
"web.config" configuration file located in the root directory of the current
web application. This <customErrors> tag should then have its "mode"
attribute set to "RemoteOnly". To enable the details to be viewable on
remote machines, please set "mode" to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
 
Pat,

are you getting the runtime error when you attempt
to view the page locally ( from the same machine
which is running the web server ) or remotely ?



Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================
 
On the same machine..
Patrick


Juan T. Llibre said:
Pat,

are you getting the runtime error when you attempt
to view the page locally ( from the same machine
which is running the web server ) or remotely ?



Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================
Click to expand...
 
Fixed it Juan..
found out that the pagenotfound.aspx had errors..
Guess i need a coffee..
Thx
 
Good news!

I was about to suggest that you check the redirection pages for errors,
since that's one of the steadiest-performing ASP.NET components.



Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================
 
Back
Top