OK - finally got it installed - currently on dnn 5014, will confirm with 521 later in the week...

the crucial points that I found in addition to the great post at the start of this thread
- you must use your primary account for impersonation and setup DNN but you can not do the same on a Client account. (Rackspace linked the issue with medium trust and DNN)
- there seem to be some timing issues with initial MSSQL user creation... Basically it seems you have to wait 10 mins, then I verify access by connecting remotely using sql server management studio (or I guess would be same with their web based tool) with that user, to check all ok before starting installation
- generally after domain, file operations it seems to help avoid unpredictable results by waiting 10-15 mins!!! i.e. for some operations you cant tell when they are 100% complete
- at key moments I clicked rebuild application (on the site page), namely after copying the directory structure up, and at the end of installation!!!
- custom skins, containers i had to just copy up as files on disk, as I couldnt use the app to install through the ui (permissions)... (but spent no further time investigating as direct copy route worked)


My other tip would be to use ftp (I used filezilla), and not the inbuilt file manager. If you do use file manager, then just note to paste you have to double click on the recipient directory first, before paste - it doesnt behave like explorer.

Rackspace has a default document named "index.htm" that takes precedence over default.aspx. If you delete (or rename) this file in your root directory, the default.aspx file will be displayed by IIS and resolve the problem.

Nik

 

---

Nik Kalyani
Co-founder
DotNetNuke Corporation
Blog | Twitter | FaceBook