tentavarious
asked on
webconfig runtime error
It seems like i get this runtime error everytime time i create a new web page on the server. I set the mode to Off and i still get the same runtime error:
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 age.htm"/>
</system.web>
</configuration>
I dont understand because i have this set to Off <customErrors mode="RemoteOnly" and i cant get the real error to show up.
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>
I dont understand because i have this set to Off <customErrors mode="RemoteOnly" and i cant get the real error to show up.
You will have to give the user ASPNET access to the folder your web site is located in.
ASKER
That has to be done through the IIS correct?
You can do by right clicking at your folder that contains the solutions, select Properties -> Security -> Add. Then type in "ASPNET" in the box, -> OK.
Done.
Done.
ASKER
I dont have that security option on my server folders.
What OS are you running you web site on?
Do you have direct access to the web server? If you don't have access to it, this must be done by someone that has.
Tell me everything you know about your server configuration.
Hang in there :-)
Do you have direct access to the web server? If you don't have access to it, this must be done by someone that has.
Tell me everything you know about your server configuration.
Hang in there :-)
ASKER
Alls i basically know is it runs windows 2000 i dont touch or server too often. I seem to get the webconfig error when i try to add a new folder containing the new web page under the inetpub\wwwroot directory.
Did you modify the right web.config file? That would be my first guess from what you described.
Bob
Bob
ASKER
Yep, i am looking at it now and the web config custom errors is set to Off. But i still get the same runtime error when i try to load the web page. I cant get the real error to show up. I had a similar problem b4 when i started a new folder on the server, i cant remember how i fixed it.
still getting this error
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 age.htm"/>
</system.web>
</configuration>
still getting this error
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>
Is this the web.config file for the main site or a sub site?
Bob
Bob
ASKER
The main site
Whenever I create a web site in ASP.NET, it gets created under a folder in C:\InetPub\wwwroot, and changing the CUSTOM ERROR MESSAGES section has always worked, so I don't understand what you did when you "created a new folder" on the web site.
Bob
Bob
ASKER
Here is how my folder is set up c:\inetpub\wwwroot\mainten ance\maint prod\all my webpages are here. I set up the maintenance\maintprod folders to contain my newly created web pages. Runs fine on my machine then i copy all the files to the server to the same location, and i get that web config error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thank you Jeffrey for that explanation. It's exactly what is needed.
Bob
Bob
You're welcome, Bob. I am glad that I can help.