Sometimes it is just easier to start from scratch rather than struggle with weird errors.  It seems odd that your error is a 1.1 error for a 2.0 app.  I have no clue what's wrong if you are confident of your IIS settings, but it seems like a configuration error to me.

I would just start fresh from a brand new virtual directory (make sure its .net 2.0, separate app pool from all 1.1 apps, and that you gave it read, write and execute in IIS).  Use version 4.3.7 of DNN.  Within 10 mins you could be running your portal.  It's not a good answer, but more often than not its the path of least resistance.  Sometimes maybe not all the files were extracted right, or really it's a timeout issue.  To make things a bit easier, remove the Blog, Gallery and Repository zip files from the Install\Modules folder first.  They are big and can cause timeouts.  To install them later, put them back in that folder on your site and request http://[server]/install/install.aspx?mode=InstallResources .

As for the slow start up, thats a .NET thing, not a DNN thing.  Your site has to be loaded into server memory if it has not been accessed in a while.  There are some things that can help with that, but let's see if we can get your site up first.  :)

---

Shawn Duggan MCPD
BlueTango Software - Canada Web Content Management
Website Design | DotNetNuke Hosting | DotNetNuke Tips and Tricks Blog
AuthIntegrator - The Easy Way To Integrate DNN and ASP.NET Applications
KeepAlive - Why Should Your Site Be Slow?

Shawn,

Thanks for all your help. Well I figured out the problem but still need help to fix it. I pull the site up fine. It initially installs OK and I can click and go to the initial page. Then I get a 404 when i click register or login and basically what it is that I am using a port number off of the main website so to get to this site, I use http://localhost:5566 but the links it has bult in are for http://localhost and obviously it can't find them. If I add :5566 to the link it takes me to, it works fine...well it won't login obviously but that will get me to the login page. Why am I doing this ?? Because I have our primary intranet site in te wwwroot of localhost and I need to put this dnn install on a separate port to test and build new intranet. Any suggestions? How can I fix this?

Jonathan