dba123
asked on
This <customErrors> tag should then have its "mode" attribute set to "Off".
I am not sure how to get past this error I'm getting after copying a website from my windows XP machine to our new dev server and then trying to run it's default.aspx page:
Server Error in '/' Application.
__________________________
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 remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, 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 "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</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="RemoteOnly" defaultRedirect="mycustomp
</system.web>
</configuration>
For the CustomErrors section in this app, we currently have:
--------------------------
<customErrors mode="RemoteOnly">
<error statusCode="404" redirect="~/temp/readme.tx
</customErrors>
we were all running this locally on XP Pro before we got this dev server now. We need to be able to keep the CustomErrors section as is I would assume so that it redirects them to our readme.txt once we go to production with this.
Server Error in '/' Application.
__________________________
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 remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, 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 "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</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="RemoteOnly" defaultRedirect="mycustomp
</system.web>
</configuration>
For the CustomErrors section in this app, we currently have:
--------------------------
<customErrors mode="RemoteOnly">
<error statusCode="404" redirect="~/temp/readme.tx
</customErrors>
we were all running this locally on XP Pro before we got this dev server now. We need to be able to keep the CustomErrors section as is I would assume so that it redirects them to our readme.txt once we go to production with this.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
My guess is that you don't have the folder set as an application, double check that.
The only other way, is to be logged into the dev server and run it from there using Localhost, and it will show you the error, but outside users will not see the error.
Ben.