Server Error in '/' Application.

[dpdoug]

I've just uploaded all the files to a new site. I have tested it locally and there is no problem. I've set the customErrors mode="Off" as it suggests and it gives me the same error when I test it online.

No matter what the setting, I get the same error page with no indication of what might be going on.

I've done a search here but I haven't found any answers. Please help -- I have to have this working by Monday.

Thanks for all your cooperation.


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="mycustompage.htm"/>
</system.web>
</configuration>

 

[lupidus]

On the webserver, ensure IIS has an application name set for the directory and the ASPNET account has read (and list?) permissions to the same folder.

 

[dpdoug]

The hosting company that I am using looked into it and discovered that there was insufficient permissions on the aspnet folder. I would guess that they are supposed to set that when they open your account -- but I would never have guessed that this was the problem. That error page gives you absolutely no indication of what the problem is.