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 10:12 AM
 

Does it have something to do w/the backslash? Do I need to do what I used to do years ago and add another '\' to it because of ascii issues?  so it should be: server-name\\instancename?

I tried that and it doesn't even finish verify, just goes in an endless loop 'verifying database'...

 
New Post
2/1/2019 4:41 PM
 
I think you misunderstood Michael. Your sql error message seems very clear. "Sql login failed."

That usually means that the web site knocked on the door of SQL server and SQL server said no.

We normally use Integrated security. The web site's Application Pool is the process that connects to the database, and the credentials it presents represent it's own identity. That is why SQL server as a whole needs to allow that account in. And the database inside SQL server has to specify what that account is allowed to do to the database.

The wizard will not ask for the login name, because, using integrated security it does not need to know.

When you login using SSMS you are (most likely, there are other options) showing that YOUR account can access SQL server. The web site is not using your account so that test does not prove "it's not a login issue". The message is very clear. It *IS* a login issue.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
2/1/2019 5:18 PM
 

Well, after much hair pulling and fussing, I figured out what the issue was.  

In the Add New Features/IIS, I did not have Basic Authentication checked. It's amazing all the nuanced issues that can arise because of the changes M$ constantly makes in Windows features.  Windows Authentication is no longer even an option in IIS Features. One needs an encyclopedic mind to keep up.

 
New Post
2/2/2019 2:33 AM
 
Very pleased you have it working.

Very surprised that lack of Basic Authentication would lead to the Sql login failed message.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
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