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 ...SQL 2005 connectionSQL 2005 connection
Previous
 
Next
New Post
5/28/2007 12:06 PM
 

Hi,

I'm  settting up 4.5.1 on my local machine under XP pro. 

On the configure database selection part of the install script , I encounter the error below, though I have  TCP and named pipes enabled.

Other than the name of the server (PC) I'm leaving all other settings to default.

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 20
Number: 10061
Message: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)

 
New Post
5/28/2007 9:23 PM
 

if connection is accepted, ensure that the server name is entered correctly.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/29/2007 1:03 AM
 

leupold wrote

if connection is accepted, ensure that the server name is entered correctly.

If connection is rejected?

I've tried leaving it as it default, setting to (local) as in the DNN wizard video all these cause immediate errors . What I've entered is the name of my PC, which corresponds with the security account   for  ASP.NET  -  ( MY-PC/ASPNET )

Jeff

 

 
New Post
5/29/2007 6:13 AM
 

Assure that the TCP/IP protocol for the MSSQL Server 2005 is activated (when you're using it). You can doing with the MSSQL Server configuriation tool.
When you're using a remote connection check you're personal firewall.

 
New Post
5/29/2007 6:44 AM
 

Yes,  I'd already done that as I said above. The TCP/IP protocol was enabled but the IP address in the IP ADDRESS tag weren't, so I activated them but that still made no difference. I'm working locally and allowing server access for SQL through my firewall anyway.

SQL is configured to run as a network service. Maybe that needs to be changed?

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL 2005 connectionSQL 2005 connection


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