I am trying to move a dnn (vr6) to Windows Server 2012, IIS 8 and Sql Server 2012. I am now trying to export the application from WS 2003, IIS 7, and SQL Server 2008.

I have also tried to move the database from 2008 to 2012 and the files. The only result I can get in IE is 'The page cannot be displayed".

When I created a new database in 2012, FF gives the error message that the page redirect failed. SQL shows the login was successful.

Has anyone put together the steps one needs to take to move to the WS 2012 environment?

Bill

Bill,

The recent tutorial on installing DNN to Windows 7 contains most of the pieces. The two major changes are:

After creating the empty database, you'll want to RESTORE it from a backup copy of the existing database. You'll make the backup using SQL Server Management Studio on the old SQL Server, and then reverse the process on the new SQL Server.

Rather than copying the install DotNetNuke package, you'll need to ZIP up all files in your web directory on the old server, and then UNZIP on the new server. Then, edit connection strings appropriately for the new SQL Server.

Creating the new website on the new server should pretty much follow the instructions in the tutorial.

--------
A great way to learn all of this would be to make your way to the Southern Fried DNN event in Charlotte, NC and come to the Admin 101 class that I'll be teaching.

But, as I'm getting a presentations together for that class, it's a good opportunity to share it.

In the meantime, approach those steps one at a time and ask questions when you hit snags. I can't tell from your description what the error is, but "page cannot be displayed" implies that the IIS website part has a problem.

Joe,

From the SQL SERVER Logs, I have been able to establish the database connection is being made. FF shows there is a redirect error. How can I find the error from the browser?

The files that were moved to WS2012 worked fine on WS2003. I have updated the connection strings in the web.config file.

When is the class in Charlotte?

Bill

Bill,

It is possible that you have a default portal alias defined and that could be causing a redirect error if the new site has a different URL from the old site.

If so, open up the database with Management Studio, look in the PortalSettings table and delete the value for the Default Portal alias (make it blank).

If the site is on a public url, I'll be happy to take a look.

For the DotNetNuke meeting: http://southernfrieddnn.com

Joe, I will give that a shot.

Chrome gives this message from a remote computer to the server:
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects

Here is what is in the PortalSettings table:
0 DefaultAdminContainer [G]Containers/Aphelia/Title.ascx
0 DefaultAdminSkin [G]Skins/Aphelia/twoColumn-rightAside.as
0 DefaultPortalAlias localhost/dnn614 -1 2013-04-
0 DefaultPortalContainer [G]Containers/Gravity/Title_h2.ascx
0 DefaultPortalSkin [G]Skins/Gravity/Home.ascx -1
0 EnableSkinWidgets True -1 2013-04-03 08:40:28.667
0 GettingStartedTabId 55 -1 2013-04-03 08:40:32.997
0 PortalAliasMapping CANONICALURL -1 2013-04-03 08:40
0 TimeZone Pacific Standard Time -1 2013-04-03 08:40

I will look at my successful new version 7 installs before I remove anything here. I do have the db backed up.

This is in a home network and I am not sure if the ip address will get you in.

Your help is appreciated.

Bill

Joe, I am still getting the same error message:

This webpage has a redirect loop
The webpage at http://192.168.20.227/dnn614/Default.aspx has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.
Here are some suggestions:
Reload this webpage later.
Learn more about this problem.
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects

FINALLY!!! It works. I started with a new folder under wwwroot / dnn6 instead of dnn614. I also attempted to create a new database dnn6. I succeeded in doing so. Then I tried to restore the dnn6 with my original dnn614 database. SQL Server absolutely would not let me do this even though I have been able to do so with earlier versions. Finally I gave up and pointed the app to the dnn614 database. I restored it to the dnn614 that I brought over from SQL Server 2008.

The web config file came from the old system (WS 2003). The connection strings were updated to the new server (local) and new log in name and password. Then I got to the http://localhost/dnn6 site -- but it kept redirecting me to the Getting Started page. Also the log in was funky.

Then I copied in a good web config file from a new successful install on the new system. The connection strings were updated for the dnn6 site. Next I got the Could not load file or assembly 'Telerik.Web.UI.Skins' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045) error. The newVersion was updated.

Finally I went to my desktop and plugged in the serverip/ dnn6 and got my web site!!!

Now on the local server, I am getting the DotNetNuke error when I do the browse thing. Oh well, I can use the desktop for updating the site.

Whew! and Whew.