I've been struggling to upgrade an old DNN 2.1.2 installation to DNN 3 basically since DNN 3 was released (I keep running into roadblocks, struggling, giving up, and coming back later).  At this point I have "successfully" completed the upgrade to DNN 3.2.2, but the problem comes in when I first click on "Click Here To Access Your Portal" after the upgrade process.

After I "click here", I get redirected to http://localhost/rt/Default.aspx?alias=localhost/rt.  When the browser goes to retrieve http://localhost/rt/Default.aspx?alias=localhost/rt, it gets redirected right back to the same URL over and over again, until I tell the browser to stop.

I've been reading around, and from what I can tell the accepted cause of this is that the portal alias cannot be found in the db.  That doesn't seem to be the case here.  I even completely removed "localhost/rt" from the portalalias table - I still get redirected there.  I've tried requesting http://localhost/rt/ and I've also tried requesting http://mydomain/rt/ (I have the local and remote copies of the files) - either way I just get continuously redirected.

Any ideas?  I must be missing something.  I suppose if nobody can help me, the next step is to download the source and run it in debug mode in VS.

Hi John - thanks.  That did help.  Now:

WITHOUT localhost/rt in the portalalias table, I do a request for http://localhost/rt/.  I get redirected to the only portal alias I had setup:  http://mydomain/404.htm.  Good.

So I go to add localhost/rt in the portalalias table as the 2nd row.  I do a request for http://localhost/rt/.  I get redirected to http://localhost/rt/Default.aspx?alias=localhost/rt.  I do that request, and get redirected to the same place over and over.  Back to square one.

 

Lance

You might need to look into exporting old users from DNN2 and importing them in DNN3. I believe there's a tool on SnowCovered that does this. I'm not familiar with the DNN2-3 upgrade script so I can't say exactly how it works. You shouldn't need to worry about the machine keys, tho. Try logging in with the default host/admin account. Also, take a look in the aspnet_Membership table to see how the passwords are stored. If you want to override a login, set the PasswordFormat column to 0 and the Password column to the desired password.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com