When depolying an ASPX web site, an error msg popped up, indicating
the http://.. apsx can not be opened. Finally, I realized that the production server is a Windows 2003, while test server is a XP.

According to http://msdn2.microsoft.com/en-us/library/t6dbcb8d(vs.71).aspx , ASP.NET is installed as a role on the operating system for Win 2003 server, but with the .NET Framework on XP.
I have done ASP.NET and IIS Manager configuration on Win 2003 server, followed the article's instruction, however the aspx pages still can not be opened in the Win 2003 server.

The final error msg is: Failed to access IIS metabase.

Exactly how do I configure ASP.NET role on Win 2003 server? Any more information? BTW, do I have to re-start the Win 2003 production server to enable the ASP.NET and IIS configuration?

TIA,
Jeffrey

__________________
C. Jeffrey Wang

Can you clarify, is the problem with deployment or with running the application? What method are you using to deploy?

-Peter

The problem was running the web site applications after deployment. I have used both "Copy Web Site" and "Build>Publish" methods. In fact, I have two test servers, one unit test and one system test. I used "Copy Web Site" from unit test server with VWD 2005 Express to another system test server and the Production server; then used Build>Publish from the system test server with VS 2005 to unit test server and the production server.

There were no error msgs. during the deployment, and I had no problems to open the aspx web sites from both test server. The aspx web sites just can not be opened from the Production server.

One new question. Just relialized the Production server is a windows 2003 server, on which the .Net Frameowrk 2.0 was installed as a role of the windows operating system. I followed the Micocrosoft knowledge base articles to fix the .Net Framework 2.0 installation errors (I think)on Windows 2003 server. I still can not open the aspx web sites from the Production Wind 2003 server. Do I need to run the "Copy Web Site" and "Build>Publish" again? Do I need to re-start the Production server after installing the .Net Frameowrk 2.0 SDK? Do I need to re-intsall the .NetFramework 2.0/ASP.NET 2.0 on Production 2003 server? Are there specific problems for deploying XP to Windows 2003 server?

TIA,
Jeffrey

The machine you are deploying *from* should not have anything to do with this problem. The process of "deploying" a .NET web application is really nothing more than just copying files.

-Peter