This is all set up as you mention.
However, it still doesn't work. I agree there is some sort of screwy db access issue, that's the only explanation. I will try Marc's answer later tonight.
I did your steps below, still got the Upgrade screen with the alert that a valid SQL db can't be found. Exact error for convenience is repeated here:
I browse here: http://209.213.120.92/ and get: The Auto option has been disabled as the DotNetNuke Application cannot connect to a valid SQL Server database. You can continue to use either of the other two Wizard options and configure the Database settings at the appropriate Wizard step.
Nothing suggested is working, however. And the original web content/db (the development site) all works.
For the steps below, I'd send screen shots if I could but the image manager here won't work and there is no way to upload files any longer. However, here's what is done with respect to the given outline:
1. copy your web portal to your sever, make the necessary file permissions (Network Services is a MUST)
The following accounts have access:
Authenticated Users: Modify and Write permissions(Inherited)
System: Full Control (Inherited)
Network Service: Full Control (Set directly at Website folder)
Admins Full Control (Inherited)
Users Read and Exec (Inherited)
IIS Default App Pool Modify and Write (Directly set on Website Folder)
2, Create a website from the IIS pointing to the physical location of your website.
3. Make sure the server IP binds to the domain name, both www. and .
At the moment, a DNS server isn't resolving this. It's just an IP being set. So the IP is both the " . " and the other instance is set to http, host name 209.213.120.92, Port 80, IP Address, same, Binding Info is blank on both lines
4. DO NOT create an empty DB to restore your dnn db, it will not work. Click databases and then restore database and give it a name and locate your backup file, and will will create a new database from your back up file.
I did this step locating the most recent nightly backup of the dev site.
5. Go to Security then Logins then New Login then Login Name then SQL Server authentication (give it a password)
Then click on User Mapping, then User Mapped to this login, click the name of your database, then the next window click on dbo_owner.
There is a user set up for this, it is one of the first things I thought of. This is in the connection string.
5. change the connection string tp ooint to your server, if you are using SQL server web edition or others (NOT SQL Express), the server name if it is on the same machine is (local) and not localhost
I also thought of (local) rather than localthost, here are all 3 web config strings:
<connectionStrings>
<add name="SiteSqlServer" connectionString="Data Source= (local); Initial Catalog=Production_Non_SSL; User Id=ISSI_User; Password=ISSI_User; Connect Timeout = 0" providerName="System.Data.SqlClient" />
<!-- This is the original VIS Demo db connection string
<add name="VIS" connectionString="Data Source=localhost;Initial Catalog=Development_VISDemo;Integrated Security = true;" providerName="System.Data.SqlClient" />
-->
<!--This is the VIS/DNN integrated db connection string -->
<add name="VIS" connectionString="Data Source= (local);Initial Catalog=Production_Non_SSL;User Id=ISSI_User; Password=ISSI_User;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules
<add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>
-->
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->
<add key="SiteSqlServer" value="Data Source= (local) ;Initial Catalog=Production_Non_SSL;User Id=ISSI_User; Password=ISSI_User; Connect Timeout = 0" />