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 ...Configuring Dotnetnuke in Server 2012 on remote SQL 2012 ProblemsConfiguring Dotnetnuke in Server 2012 on remote SQL 2012 Problems
Previous
 
Next
New Post
11/22/2012 11:29 AM
 

Environment

Webserver - Running IIS8 on Server 2012

SQL Server - Running SQL2012 on Server 2012

The installation appears to be successful, but when connecting to the site via the browser to configure the site, (ie. http://www.<sitename>.com/dotnetnuke/) I get the following prompt. I've filled out the following.

"Configure database connection"

Select Database : SQL Server 2005/2008 Database

Server : <Servername>\<Instancename>

Database: <Database Name>

Integrated Security : Checked

Run as DBOwner : Checked

Object Qualifier : <Prefix>

When I Click next, I get the following error.

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 20
Number: -1
Message: 

And yes, the message field is blank in the error, that is not a typo.

Firewall is not blocking the two servers from communicating, and they are both on the same Network.

Anyone have any ideas?

Thanks.

 
New Post
11/23/2012 4:04 AM
 
did you enable TCP/IP protocol for both, SQL server and client?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/23/2012 8:47 AM
 
TCP/IP Protocol is enabled on the SQL Server for sure. As offsite users connect using the management console remotely.

I'm not sure what you mean by client? do you mean the webserver?
 
New Post
11/27/2012 9:42 AM
 

Anyone have any suggestions? I've been unsuccessful as of yet on googling this error.

 
New Post
12/30/2012 5:18 PM
 

Not sure if you still need help with this but i did it a little different to get it to work. Steps are listed below.

** Create a user account you will be using in AD users and computers (For security reasons i didnt not use a domain admin account)

Since it is a domain infrastructure im working in, on the IIS server i did the following:

  • Go to Advance settings on the application pool you are using > for the Identity Switch it to custom > enter in credentials Ex: DOMAIN\USERACCOUNT & password

On the SQL 2012 server i did the following:

  • Create your Database (Name it wht you would like to call it)
  •  Create a new login under SECURITY > LOGINS (if you created a new user add that one, or existing user account)
  • Go to the properties of the user added in previous set and USER MAPPINGS to the correct database and give it db_owner rights
  • on the SQL Firewall add exeptions for both inbound and outbound for the sqlserver program (i had to use dynamic ports exepetions - http://technet.microsoft.com/en-us/li...

* Make the user has modify rights to the root Dotnetnuke extracted files folder

You should be fine after that.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Configuring Dotnetnuke in Server 2012 on remote SQL 2012 ProblemsConfiguring Dotnetnuke in Server 2012 on remote SQL 2012 Problems


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