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 Server 2005 (running on different machine)SQL Server 2005 (running on different machine)
Previous
 
Next
New Post
5/13/2008 11:19 AM
 

Hi all,

I am using  
DotNetNuke_04.08.02
Windows 2003
MS SQL server 2005 (running on different machine)

After I had configured DotNetNuke_04.08.02 to run under IIS, I proceed with installation wizard until reached  the Configure Database Connection step , once I tried to test the connection I got the below error , in spite of that I connected successfully  to DotNetNuke using MS SQL server 2005
 Studio manager  with the same user and password :

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 20
Number: 2
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
The following is the connection string that I configured in web.config
<connectionStrings>
  <add name="SiteSqlServer" connectionString="Server=10.1.1.10;Database=DotNetNuke;uid=user_name;pwd=mypass;" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
 <add key="SiteSqlServer" value="Server=10.1.1.10;Database=DotNetNuke;uid=user_name;pwd=mypass;" />
 .....
<appSettings>

Thanks in advance

Suhaib AlNoursi

 
New Post
5/13/2008 11:49 AM
 

if you are able to access sql server locally on the server with same credentials but not from a different machine, this is most likely caused by missing "allow remote connections" for Named pipes provider.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...SQL Server 2005 (running on different machine)SQL Server 2005 (running on different machine)


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