Site deploy issues

Anyone have any idea what this is?
Server Error in '/admin1' 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>
David Fetrow
Helixpoint LLC.
http://www.helixpoint.com
davef@dotnet.itags.org.helixpoint.comDaveF wrote:
> Anyone have any idea what this is?
>
Did you read the message? It says that some error has occured, but it can't
let
you see the details for security reasons. It even shows how to prevent this
block so you can see the real error.
Hans Kesting

> Server Error in '/admin1' 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>