Recently, a server of ours running Windows Server 2003 SP2 began showing signs that it is going to die soon and so I have been given the task of moving certain sites before it passes on to our new server running Windows Server 2008 R2.

The site in question runs DotNetNuke 6.1.3 and has worked, without incident, since we brought the site up. I have moved the site last night (as stated above) and moved it's database from a SQL 2005 server to a SQL 2008 server. After these moves, I changed the security on the site to allow "NETWORK SERVICE" to Modify rights, updated the site to .NET 4.5 protocol, placed it in a .NET 4.0 application pool, and started the site again.

1. The first complication comes from the home page of the site, which was working prior to the move. There is a page within our site called "Home.aspx", and which Admin >> Site Settings >> Page Settings >> Home Page is set for "Home". However, the site goes to a blank page (which I assume to be "Default.aspx") and does not redirect.
   
   
2. The second is that, in assuming this to be a configuration error from the move, I attempted to upgrade the site to DotNetNuke 6.1.4. I unzipped the upgrade files into its location on the server as I have with countless DotNetNuke sites that my team and I work with. When I reloaded the site, there was no change and no Installation Wizard initialization. However, the information in Host >> Host Settings >> Basic Settings >> Configuration >> DotNetNuke Version now reads 06.01.04 without having gone through the upgrade steps.

Assistance on both of these matters are imperative as my company wishes to move several move sites off of the dying server, but if I cannot move one without incident, we are concerned about our future with DotNetNuke.

Thank you.

All permissions are the same as they were on the old server. The web.config reads that it was running in the .NET 3.5 framework, but when it was compiled as such when it was brought over to the new server, we received the error message "Parser Error Message: Unrecognized attribute 'requestValidationMode'" so it has been recompiled in .NET 4.0 to relieve this error.

Otherwise, the same problems exist: We cannot upgrade the site and the home page does not redirect properly.