>We have an ASP.NET application under source control with VSS that requires deployment to an Internet production server residing outside our firewall. There are two identical staging servers residing inside the firewall to which we upload the files. An administrator then copies the files from this location to the produciton server outside the firewall. When we upload to the staging servers we test to make sure the app is working properly. This has been successfully done.
>
>When the files are placed on the production server we get an ASP.NET unhandled exception when the first page is hit even though the server configuration is supposed to be identical to the staging servers.
>
>Has anyone seen behavior like this and if so what have the causes been?
>
>Possible causes we have been considering:
>
>1) Web.config setting(s) not correct. These have been double checked and the same Web.config file performs fine on the staging servers.
>2) Some sort of file corruption or unusual characters in one or more deployed files that is causing the production server to choke but is not affecting the staging servers. We have recreated the Web.config file from scratch manually and tested on the staging servers to eliminate this possibility in that file. We are waiting on this new file to be deployed to the produciton server for testing. If there is some sort of corruption in one or more of the aspx, ascx, etc. files, we have no way to pin down the file or files since we have not been able to reproduce the problem locally, or even on the staging servers.
>3) The production server configuration is not actually identical to the staging servers. We have been assured they are all configured identically but have no way of checking or verifying this since the servers are out of our control.
>
>Any information or experience on this issue would be appreciated.
>
>Bill

Bill;

Have you checked IIS and Security?

Tom