Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing NAMED SQLSERVER INSTANCE using installInstalling NAMED SQLSERVER INSTANCE using install
Previous
 
Next
New Post
2/1/2019 12:52 AM
 

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.

 
New Post
2/1/2019 1:19 AM
 

Just wanted to add that I'm using Chritocs previously excellent video on how to install using the wizard. Website name is dnndev.me, and I'm folllowing all instructions in the video.  Changed folder permissions and started the website in IIS. Wizard page shows up fine so It's not a permissions issue.

The specific SQL error I'm getting is the dreaded:

ERROR:Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 18456
Message: Sql login failed

 
New Post
2/1/2019 2:52 AM
 
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

Michael Tobisch
DNN★MVP

dnn-Connect.org - The most vibrant community around the DNN-platform
 
New Post
2/1/2019 10:02 AM
 

Hi Michael:

Thanks so much for responding! I used Christoc's video, so the login name is dnndev.me. And yes the permissions are all set, since the wizaard page shows up.  I don't understand the login name you're referring to.  I'm using 'dnndev.me' as the login.  That login has dbowner of the dnndev.me database (same name as the login per the video).

Since the apppool is /dnndev.me and the databse name is also (ack) dnndev.me AND the login name is dnndev.me, can you give me a specific example of what i should be entering as the login?  Because I'm just using the dbowner 'denndev.me'. not adding any apppoll name to it.

 

 

 
New Post
2/1/2019 10:09 AM
 

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.  

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing NAMED SQLSERVER INSTANCE using installInstalling NAMED SQLSERVER INSTANCE using install


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out