I had the same error, and fixed it by increasing the default application timeout in the IIS virtual directory properties from the default 110 seconds to 900.  Basically the install takes the longest when it's creating its stored procedures (I think in particular for the shopping modules), and if the asp.net application is not given enough time to create these via IIS then it will timeout and disconnect without any real description error in the events log.

Here's the fix:

1. Open IIS, and right click on the virtual directory you set up for running the dotnetnuke install.  Choose "Properties".

2. Open the "ASP.NET" application tab, press "Edit Configuration", and then select the "Application" tab.

3.  Change the "Request execution timeout (seconds)" value to be say 900 or more.

4.  Try the install again, it should work this time if you were getting some tables being installed before the timeouts were occurring.  Otherwise, it might be another issue.

Good luck :)

Shan

This fix worked for me as well. My database scrips install itself took 380 seconds to accomplish, so 900 is a good number.

Um, you might want to recheck that IIs remembered your change. I made the change, it failed at 110 seconds. So I tried again to discover that IIs didn't remember my initial change to 900 seconds. One would think 'someone' would create an 'apply' button or something....sigh. Anyway,

Thanks Shan for the help!

This error has kept me from upgrading to SQL 2005 for some time. I also want to say that when the install fails without this fix, I was getting an Domain Name Does Not Exist In The Database error. And, since the database was not being properly installed, of course it didn't exist. I thought by posting this error here here someone doing a search on such an error might find this solution since it has nothing to do with child portal issues but is an install failure issue because it is timing out and thus the thread is aborting.

Paul,

I just switched to ixwebhosting.com as well...not knowing there would be problems with installations. Did you ever resolve this issue? If so, what did you do?

Thanks,

Mike