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 ...No valid default database connection detectedNo valid default database connection detected
Previous
 
Next
New Post
12/4/2013 11:05 AM
 

I installed a fresh copy of 7.01.02 on Server 2008R2 with SQL 2012 Enterprise.  I settled on SQL authentication and updated the Web.config.  When I launch the installwizard I see the error "No Valid default database connection detected.  Standard Database setup option is unavailable" 

I see the SQL user account I set in the web.config successfully connect to the database.  I have temporarily given every possible permission to my SQL User, Network Service and AppPool Identity but the error persists.

I was able to find a few posts regarding the issues but the only fix was to switch the appPool to classic.  Wondering if there is a different solution.  

 
New Post
12/4/2013 12:24 PM
 
that usually indicates an incorrect connection string, or an attempt to use a netlib (such as local pipes) or a remote server. The easiest way I find to debug these is to create a UDL file (http://www.sophos.com/en-us/support/knowledgebase/65525.aspx) and use it to verify the connection. Once it works, open the udl file in notepad and check you are using the right connection string.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
12/4/2013 1:19 PM
 

I followed your instructions .

Original connection string: <add name="SiteSqlServer" connectionString="Server=(local);Database=whgonline;uid=SqlUser;pwd=XXXXXXX;" providerName="System.Data.SqlClient" />

UDL Built:  <add name="SiteSqlServer" connectionString="Persist Security Info=False;User ID=SqlUser;Password=XXXXX;Initial Catalog=whgonline;Data Source=whg-mdc-db-02;" providerName="SQLOLEDB.1"/>

Same error as before.  I have even tried to install SQL express and use the default express connectionstring.  After providing what I believe to be all the correct permission to SQL Exress 2012 I still get the same error.  Anything else I can try?

 
New Post
12/4/2013 1:28 PM
 
Pete wrote:

I followed your instructions .

Original connection string:

UDL Built:  

Same error as before.  I have even tried to install SQL express and use the default express connectionstring.  After providing what I believe to be all the correct permission to SQL Exress 2012 I still get the same error.  Anything else I can try?

After looking at the authentication logs I noticed that a Windows Use was access the database at the same time mySQL user was.  Both network service and the AppPool Identity have access too the database so I was still confused.  I figured I would try to hit the site from my PC instead of from the servers browser.  I normally use the server to see detailed errors.  Now the site is up.  Is there an explanation?  I didn't change the connectionstring.  It still uses SQL authentication.

 
New Post
12/4/2013 3:28 PM
 
you need to make sure you install and use 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
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...No valid default database connection detectedNo valid default database connection detected


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