Hello,

I'm getting the persistent install starting up, meaning there's an error in how the db is configured and/or the connection string is wrong.

I've restored a 5.4 site restored the db.  I have NTAuthority\ system as a user with owner added as a db login.  The site folder has necessary user accounts/permissions.  Site fires up = IIS 8 is set up.  But ... I get the /install/underconstruction.htm.  That is Firefox tells me the page is being redirected in a manner that may not complete.

I enter the url dev.skydivecolumbus.com, which is in the LM Hosts mapped to 127.0.0.1, like dev.skydivecolumbus.com/ into the address bar and this becomes dev.skydivecolumbus.com/install/underconstruction.htm.

OK, DNN is trying to install meaning the db isn't being hit.  It thinks it needs to install.

Connection strings are:

<add name="SiteSqlServer" connectionString="Data Source=localhost;  Initial Catalog=DnnRdSdcmhDbWeb;  Integrated Security = SSPI" providerName="System.Data.SqlClient" />

and

<add key="SiteSqlServer" value="Data Source=Data Source=localhost;  Initial Catalog=DnnRdSdcmhDbWeb;  Integrated Security = SSPI" />

I've tried localhost, the instance name of DESIGNLAPTOP\SQLEXPRESS, the default notation of "." as this is the only instance, etc  I've tried SSPI and just plain old "true" for Integrated Security.

I think the strings are OK.  There is something I'm missing in the db restore and setup.

I downloaded the super user manual and I'm sorry -- it needs a Quick install card or something. :)   i can't find in the 1611 pages a simple "here's how you install DNN" .  It must be on page 946 instead of between 1-20 where it should be. :)

If anyone knows off the top of their head what the basic things to check for on the db are, please info me or point me to the page in the manual.

Thanks!

Mike

Am I correct that the database has been migrated from a different server? If so, and if you were using NT Authority\System as the account for integrated security login, I'm not sure if the new SQL server would see that account as the same internally as the old even though their names would be the same. I have frequently run into the "orphaned users" problem when moving databases from development to production and the reverse but have always been using SQL Server Authentication rather than Windows Authentication (integrated security).

If your instance of MS SQL Server Express is already configured or can be configured to support mixed mode authentication - that is either Windows or SQL Server Authentication I would suggest you do the following:

1. Create a new SQL Server Express login using SQL Server Authentication - with a new username and password.
2. Add the newly created login as a user for the DNN database and grant the user db_Owner schema ownership and role membership.
3. Modify both DNN connection strings in web.config to remove "Integrated Security=True" and add the newly created login's user id= and password= attributes. As for the server (DataSource) I use ".\SQLEXPRESS" on my localhost installations. The connection strings should look like the following:

<connectionStrings>
    <add name="SiteSqlServer" connectionString="Data Source=.\SQLExpress;Initial Catalog=xxxxxxxxx;User ID=xxxxx;Password=xxxxx" providerName="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings>
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Initial Catalog=xxxxx;User ID=xxxxx;Password=xxxx" />

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

Will, you're a gentleman and a scholar.  That worked, brought the site right up.

Thanks for your help.

Mike