After creating a working DNN portal I now get stuck in an endless redirection loop when attemping to view the portal. This occured after adding an additional alias (which can be seen in the portalalias table)  in preparation to pushing the DNN website to our production server. I have tried to manually adjust the aliases in the table but either it doesnt make any difference or I end up getting a file not found error.  I am using Visual Studio 2005 on Windows XP with SQL Server Express and was preparing for a move to the production server running Windows Server 2003 and SQL Server 2005. We got the database detached and retached ok and then FTP'ed the DNN Website files accross ok. It was then after restarting every thing that the problem occured on both the server and development machine. I have reviewed several DNN sites and blogs but have not been able to find a solution that fixes my problem.

Ideas anyone?

Thanks in advance,

Scott

Thanks for the reply. It turns out that when I pushed the site to the production server the upgrade wizard got triggered and a incorrect default.aspx file got placed in the one and only (parent) portal. The code in this file was causing the redirect loop. Aparently there is bug? I saw a post about this for the next version but not 4.5.1. Not sure if its the exact same bug but appears so. See http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=5799 . So I replaced the default.aspx file and had to restore my local database and then my development site was working again. I still do not have the production server fixed yet. At one point I had triggered the install wizard so I think my production database is toast. Im new to dotnetnuke and unsure of what the upgrade and install wizards do behind the scenes. Need to understand this now...