R
Rick Strahl [MVP]
Cezar,
This is the default behavior so you need to figure out how to capture thte
error info to get the standard error information that will tell you more. As
per that message the easiest way for first time debugging is to simply
change web.config and set the Customerrors tag to off so you can see the
error. Get thngs going then change it back.
Ultimately though you'll want to trap errors display a cleaner error message
and log the error information.
+++ Rick ---
--
Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web
application error from being viewed remotely (for security reasons). It
could, however, be viewed by browsers running on the local server machine.
"web.config" configuration file located in the root directory of the current
This is the default behavior so you need to figure out how to capture thte
error info to get the standard error information that will tell you more. As
per that message the easiest way for first time debugging is to simply
change web.config and set the Customerrors tag to off so you can see the
error. Get thngs going then change it back.
Ultimately though you'll want to trap errors display a cleaner error message
and log the error information.
+++ Rick ---
--
Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web
..Net framework as it wasn't there before.Cezar said:Hi,
I try to deploy an application on a IIS5 web server. I just installed the
custom error settings for this application prevent the details of theI try to display a simple aspx page with just one label. The error I get is:
-------
Server Error in '/WebApp1' Application.
-------------------------------------------------------------------------- ------
Runtime Error
Description: An application error occurred on the server. The current
application error from being viewed remotely (for security reasons). It
could, however, be viewed by browsers running on the local server machine.
viewable on remote machines, please create a <customErrors> tag within aDetails: To enable the details of this specific error message to be
"web.config" configuration file located in the root directory of the current