Last post Mar 17, 2014 11:49 PM by Starain chen - MSFT
Mar 16, 2014 05:41 PM|Ringo Englewood|LINK
Our web developer is no where to be found and I've been tasked with moving our organization's two website to a new server before our contract expires. Our old server is as follows:
We are moving two websites, one in DNN, the other in ASP.NET with SQL 2005 to the following new server.
Here's what I've done so far.
At this point, what else am I supposed to do make sure everything else is setup correctly on the new server? I am aware the WEB.CONFIG file contains SQL connection info that needs to be edited, but just dont know exactly how to get that done. Also, I noticed
in IIS, under Sites/Website1 or Website 2, when I click Default Documents, I get an error message stating, "There was an error while performing this operation" about a line error in the web.config file. The funny thing is, the websites seem to load fine for
now, but I just know I am missing some very important steps.
Any help would be greatly appreciated as I am a beginner at this, more of an general hardware IT Admin than I am a web developer.
Mar 16, 2014 06:54 PM|oned_gk|LINK
Mar 16, 2014 07:11 PM|Ringo Englewood|LINK
Thank you for your response.
On the OLD SERVER, in IIS 6, both websites are set to use ASP.NET Version:2.0.50727.
Any point in the right direction on how to get this setup correctly would be greatly appreciated. Thanks.
Mar 16, 2014 10:51 PM|oned_gk|LINK
You need to configure application pool to run under net 2.0
To enable net 3.5 (it's also using net 2.0 CLR), see this instruction
Mar 17, 2014 12:50 AM|Ben_HFL|LINK
When you migrate your site from one server to other server, you need to check the connection string again. Could you please check that you have given correct connection string?
Mar 17, 2014 11:49 PM|Starain chen - MSFT|LINK
If you are using the new server’s database, you should modify the web.config file
connectionStrings section. (E.g. Data Source User ID, Password)
Based on you said that “the websites seem to load fine for now”, so you needn’t configure the default page in the
Default Documents any more.
The old websites used the .Net 2.0 application pool, so I think you needn’t configure the application pool. I think the new website used the .Net 4.5 application pool (Server 2012 IIS 8). It can compatible .Net 2.0.