Help! Issue with legacy site

Hi there,

I have only played with ASP.NET so I still consider myself a newbie. I have
taken over a website to maintain. I copied this down from an FTP client ( CUTIE
FTP) and set it up in my Visual Web Developer Express.   Then went to deploy the
site to the new host web server using visual web developer express and attempted
to view the site in IE. I am now getting an error.  I have changed nothing in
the site other than transferring to a new place.  The error is 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="mycustompage.htm"/>
    </system.web>
</configuration>


I dont know what I did wrong. Can anyone help?

Hi Cuz64081,

The first thing you need to do is modify the web.config file as it describes -
change customErrors mode="Off" this way the real error message will be
displayed.

If you can remote on to the server, the real error message will be displayed for
you there even without the setting. It's a security precaution.

Since this is a new server, some of the first couple things I would check - the
website has been set as an application in IIS and the proper .NET version has
been selected.

Let us know what the actual error message is and we can probably fix you right
up quickly.