Hi all.

I was a long time DNN developer back in the day. Had some health issues, but after some years recovering I'm back to using DNN. However, I used to just change the web.config file when I created new sites.  I never bothered with the 'easy install' feature of DNN.

Since there obviously have been many changes in the last few years I need to use the install feature.  However, I am using a named sql instance.  Let's say the named instance is (servername\instancename) is:

 

my-server-name\instancename

When I attempt to use that in the install, and select sqlserver/sql server expess, I can't get a valid connection.  The sql server database is correct, and all permissions are correct. I just keep getting an error!  I've now spent hours just trying to connect to the product and am about to give up.  There is no documentation on what to do w/a named instance that isn't 10+ years old.  And doesn't apply. I've also tried changing the web.config sqlserver but that isn't working either. Keeps getting changed by the install and doesn't accept a previous value.

Can someone please give me a heads up on why a perfectly valid servername\instance name is not connecting?  I have no issues connecting w/umbraco.  just dnn.  It's something to do w/how I'm presenting the server\instance.

Alan,

I guess you have already created a database in your SQL Server's instance.

Have you created a login for the ApplicationPool Identity on SQL Server and mapped this login to the database with the db_owner role (at least for the install process)?

If the SQL server is on the same machine, the login is propably something like "IIS AppPool\AppPoolName", if it is on a different machine within the same domain it is something like "DOMAIN\WEBSERVERNAME$". If the two machines are not in the same domain you have to use an SQL Server login, not a windows user.

Happy DNNing!
Michael

---

Yeah, now I'm really confused. I just went back and looked at the wizard. It doesn't even *ask* me for the login name, just the database name.  Again, if I have a server\instance named:

server-name\instancename

And the database name is:

dnndev.me

That is *exactly* what I am typing into the 2 fields that are offered.  The login is set in the actual database, which again, is working fine. I can log directly into sql mgmt with the above 2 specifications, and adding dnndev.me as the login name.  So it's not a log issue. I also listed the specific error I'm getting.