I can't figure this out, i've taken everything out of the web.config that could possibly cause a problem and still get this generic garbage...
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".
|
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.
|
Had this problem yesterday. I had an error on the server that I couldn't simulate on the dev environment. I changed my Web.Config from
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
to
<system.web>
<customErrors mode="Off" >
</system.web>
but in my haste, I didn't close the customErrors tag. See? Then it gave me that horrible message that you received above.
But wait, there's more! I then tried to copy my web.config again, this time WITH the closing tag, but I kept on getting an access denied error from the server. I had to contact the hosting company, one of their tecchies had to fix my web.config file for me, and only then could I continue working on the server again.
How embarrassing!
Hope this helps you in some way...
Is the folder with the offending web.config file configured as anapplication in IIS? Otherwise, it may be a web.config higher upin the directory structuner that's causing the issue.
Hi,
When u create a web application, by default the custom errors mode is remote only. Turn it off and try it again.
HTH.
This worked...thanks.
<system.web>
<customErrors mode="Off" >
</system.web>
0 comments:
Post a Comment