=?Utf-8?B?R3JhaGFt?= <(E-Mail Removed)> wrote in
news:1ADC84D7-C8BF-4AF3-9631-(E-Mail Removed):
> Hi there,
>
> Trying to upload a web site to the server from Visual Studio 2005,
> using the temple when creating a new web site.
>
> It uploads ok with no errors. However when viewing through the web
> browser not in Visual Studio I get the following error: -
>
> 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 have switched the <customErrors mode="Off"/> to off and still get
> the same error.
>
> What am I doing wrong
>
Most probable causes:
1. The version of ASP.NET on the server is not the same version on your
local box. you can check this in IIS.
2. You are missing a required assembly.
NOTE: IF this is deployed to an ISP, they sometimes have things set so
you cannot get a lot of error detail. This is to avoid hacking on their
machines, but makes it a pain in the rear for us. Deploying recently to
webhost4life, I found that my connection string was wrong and throwing
an error that was not even properly caught by my try ... catch. So it
may be something as simple as ensuring your configuration is pointing to
the right server.
Peace and Grace,
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Twitter: @gbworld
Blog:
http://gregorybeamer.spaces.live.com
My vacation and childhood cancer awareness site:
http://www.crazycancertour.com
*******************************************
| Think outside the box! |
*******************************************
Similar Threads
