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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL Server Developer Edition not allowing remote connections issueSQL Server Developer Edition not allowing remote connections issue
Previous
 
Next
New Post
5/25/2008 2:29 AM
 

I just started using the 04.04.02 starter kit and since I do not have SQL Server Express Installed I went through the steps to create anew database for my application in SQL Server 2005 Developer Edition instead.  This is a blank database with all the user information working properly when logging in via SQL Server Management Studio.  I can use both the SA and the new account I created for this application.  I made all the changes noted in the setup guide pdf that came with the product and also read through all the threads on this forum with no luck.  In the connection string I have tried the following servers: <localmachinednsname>, localhost, ., <localmachinednsname>/localhost, <localmachinednsname>/<localmachinednsname>, <localmachinednsname>/. and so on and so forth.  Now when I go to compile the application I get the following error when I have already modified the Surface Area setting of SQL Server to allow both TCP/IP and named pipes.

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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Other valid information...I am using Windows Vista Ultimate and IIS 7.0 (with the entire IIS 6 Management Compatability features setup) and when I opened the solution for the first time I had it run with the original .NET 2.0 achitecture without upgrading it to 3.5 or any other version of the framework. 

Any suggestions for a newbie???  Thanks in advance for any help you can give!

 
New Post
5/25/2008 3:58 AM
 
  • if the SQL Server is default instance, simply use "(local)" as servername, otherwise ".\Instancename"
  • all db information can be added into the install wizard when calling your site the first time, and the connection can be tested inside.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
5/25/2008 9:25 PM
 

I tried using both the default instance name .\MSSQLSERVER and also (local) for the instance.  Neither worked still. 

When you say the install wizard you mean to use the full install instead of just the .vsi starter kit right?  If so, I will try that next since I have only been working with the starter kit as of thus far.

Thanks for your help.

 
New Post
5/25/2008 9:28 PM
 

I tried using both the default instance name .\MSSQLSERVER and also (local) for the instance.  Neither worked still. 

When you say the install wizard you mean to use the full install instead of just the .vsi starter kit right?  If so, I will try that next since I have only been working with the starter kit as of thus far.

Thanks for your help.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...SQL Server Developer Edition not allowing remote connections issueSQL Server Developer Edition not allowing remote connections issue


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