Hi !
After spending almost a day and half on installing DNN on a remote server I thought I would describe my experience, now that I finally succeeded! Installing on localhost, there was not a lot that went wrong and the forums provided good help. Installing on a remote server that didn't have a lot of experience with managing DNN portals was another matter, a lot of the time the advice on the forums sometimes confused more than helped.
Clean install what I did:
1. Upload via ftp client the Install package, I unzipped the folder first on my local machine.
2. Made the changes to the web.config that was included in the install folder.
Changed the database connectionstring:
<connectionStrings>
<!-- Connection String for SQL Server 2005 Express -->
<add name="SiteSqlServer" connectionString="Server=212.214.136.60;Database=hemslojd;uid=gardin;pwd=xxxx;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<add key="SiteSqlServer" value="Server=212.214.136.60;Database=hemslojd;uid=gardin;pwd=xxxxx;" />
<add key="InstallTemplate" value="DotNetNuke.install.config" />
<add key="AutoUpgrade" value="true" />
<add key="InstallMemberRole" value="true" />
<add key="UseDnnConfig" value="true" />
3. Browsed to my url in Browser + added the install directory :
http://www.myurl.com/Install/Install.aspx?mode=Install
4. Voila the installation process started.
5. SAVED THE WEB.CONFIG FILE from server to my local harddrive
A lot of forums say that I have to do something with my release.config I have not touched it.
Though I appreciate the need to make a backup of the config file to save the machine key that was generated in
installation on the server. Overwriting the config file on the server with a config file with different machine key will make it impossible for users to log in to your site.
6. Browsed to my portal and changed the password for admin and host user.
Good Luck