HI Everyone:

I'm having a strange issue with DNN 4.5.x and, despite 4 reinstallations, I can't figure the issue out.

I'll describe the problem first and then the steps taken that lead to it.  The problem:  the request for http://localhost:8012/Default.aspx results in IE just sitting there and spinning.  The progress bar flashes very oddly as it moves to the right.  Behind the scenes, the ASP.NET worker process eats up 80-90% of the CPU consistently and doesn't let go until I cancel the request (which never seems to time out, either).  Upon examining IIS logs, I see a couple hundred entries for my single request for Default.aspx; all are being responded to with 302 return codes (temporarily moved).  This would explain the number of entries for a single request.

My configuration:  Windows 2k3/IIS 6, SQL Server 2005, DNN 4.5.2 Source.

Steps to reproduce the problem: 

 - Unzipped the contents of the DNN distrib to c:\inetpub\DotNetNuke and set the security appropriately.

 - Configure a web site in IIS admin pointing to above site and listening on port 8012.  Create a new AppPool and assign the site to that AppPool.  Confirmed the site is targeting ASP.NET 2.0.

 - Create a DB called DotNetNuke; login DNN/user DNN and assigned DBOWNER role.

 - Modified web.config to contain correct connection string info.

 - Go to site (http://localhost:8012/Default.aspx).  Installation wizard confirms appropriate security rights, DB connectivity, etc.  All scripts execute without error.  Click go to site and the site loads.

 - Obviously, since I'm using a port other than 80, any link clicks from here won't work.  They all target localhost instead of localhost:8012.  So, I modify the httpalias value in the portalalias table and change it to localhost:8012. 

 - Now I try to access the site.  The problem described at the top of the message shows its head.  I can't access the site.

STRANGE:  If I change the httpalias value back to just localhost, the initial request to localhost:8012/Default.aspx works fine.  Can't get to anything else as expected but the initial request is fine.  Change the httpalias and I get the problem.

So, I've isolated the problem at least to involving the httpalias in some way.  However, aside from just going back to port 80 and using host headers (I'm working on two different sites), I'm at a loss.  Didn't have this problem in 3.x so I don't know if there's a change in 4 that I'm missing.  I thought there was a small chance that it was an issue with 4.5.2 but I get the same behavior in 4.4.1 so that's not it.

Any ideas?  I'm stumped on this one.  Thanks!