Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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 04.08.04 using remote SQL Server with Windows Authentication..Installing 04.08.04 using remote SQL Server with Windows Authentication..
Previous
 
Next
New Post
6/25/2008 4:23 PM
 

I hear this is a nice product. But there is no way in hell anyone has ever successfully installed this app by following the install document when their database is SQL Server with only windows authentication enabled on a separate server. Period. I would love to write an install doc that actually works if/when I figure out how to install the product.

I have tried a lot of things but I do not want to enable SQL authentication. The current setup I have is this:

-  User mydomain\some_user has full control of everything in the folder DNNTest. (I am getting desperate)

- Anonymous access for site DNNTest is enabled and the user is: mydomain\some_user

- On my sql database there is a login for: mydomain\some_user  Also, that user has been added to the database DotNetNuke and is marked as db_owner under Owned Schemas and Role Members.

I have tried every combination/permutation of options on the Configure Database Connection page. The current attempt is to have integrated security checked. Since this is what I am doing. The user mydomain\some_user is the anonymous user account that is connecting to sql server. Yet it doesn't work. The error is as follows and is completely untrue.

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 11
Number: 4060
Message: Cannot open database "DotNetNuke" requested by the login. The login failed.

Index #: 1
Source: .Net SqlClient Data Provider
Class: 14
Number: 18456
Message: Login failed for user 'SIENA\CCXXSDAP010$'.

First of all, that login listed above is the damn machine name with a dollar sign appended to it. It is not the account that the site is running under. 2nd of all, if the application would use the right username that I have specified in the web.config file it could open that database just fine. I specified the domain\username just as the install document specified. Same domain\username specified in directory security, file permissions, database and at this level. I have tried dozens of combinations of ways to get this thing to work and it does not seem that there is any way short of enabling SQL authenticaton. That is just silly. Man I am frustrated.

Any help is really appreciated. Thanks!

P.S. What is with the double spacing with this text editor?

 
New Post
6/26/2008 3:40 PM
 

Can you open the database from the DNN machine in SQL Manager using the domain/account login you specified?  Is Port 1433 open on the firewall?  SQL 2000, 2005 or 2005 Express?

Jeff

 
New Post
6/27/2008 11:05 AM
 

Thanks for the reply! Yes, I can connect via SQL Management studio to the SQL 2005 instance. Both servers are behind the firewall so it should not be a firewall issue. My experience with integrated security and sql server is only with old school ASP.  A coworker pointed out that I needed to set the Identity for DefaultAppPool to the same domain account. Once I did that the install started. However, it created the table "Version" and then it appears that the install crashed. Going to try to mess with it again later today.

Chris

 
New Post
6/27/2008 11:24 AM
 

It installed this time. Not sure why it crashed during the install last time. For anyone attempting this in the future, you need set your domain user as the anonymous user for your site in IIS, set the Identity for DefaultAppPool to the same domain user, grant the domain user the appropriate permissions to the site directory and setup the domain user in SQL Server. The problem I had was I did not set the Identity in DefaultAppPool.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing 04.08.04 using remote SQL Server with Windows Authentication..Installing 04.08.04 using remote SQL Server with Windows Authentication..


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