Help With Deployment!

[gderosa]

I am trying to deploy an application to a test server on my company's intranet. This application runs just fine locally, and I used the 'Copy Project' option in VS 2003. I set the destination project folder to http://ncgc-webdb/NEWGDLocator2/ and selected the File Share Web Access Method. When I access the application at http://ncgc-webdb/NEWGDLocator2/WebForm1.aspx I get this error:

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

<configuratio n>
<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 "defaultRedirec t" attribute of the application's <customErrors > configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuratio n>
<system.web>
<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
</system.web>
</configuration>

What am I doing wrong?? This is driving me crazy. I even tried to do the same process for an application that only had a label and I still received the same error.

[sashi]

I am trying to deploy an application to a test server on my company's intranet. This application runs just fine locally, and I used the 'Copy Project' option in VS 2003. I set the destination project folder to http://ncgc-webdb/NEWGDLocator2/ and selected the File Share Web Access Method. When I access the application at http://ncgc-webdb/NEWGDLocator2/WebForm1.aspx I get this error:

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

<configuratio n>
<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 "defaultRedirec t" attribute of the application's <customErrors > configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuratio n>
<system.web>
<customErrors mode="RemoteOnl y" defaultRedirect ="mycustompage. htm"/>
</system.web>
</configuration>

What am I doing wrong?? This is driving me crazy. I even tried to do the same process for an application that only had a label and I still received the same error.

Hi there,

Make sure the IIS_USR user account has been given permission on the destination folder. Good luck & Take care.

[gderosa]

Hi there,

Make sure the IIS_USR user account has been given permission on the destination folder. Good luck & Take care.

Thanks very much for your help but it turned out that I had to register IIS with ASP.NET 2.0.

[sashi]

Thanks very much for your help but it turned out that I had to register IIS with ASP.NET 2.0.

Hi there,

Registering IIS with ASP.NET 2.0 is something new to me, i was wondering how did you do that? Can you please provide some information on this process. Thanks in advance & Take care.