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 ...ERROR: Could not connect to database specified in connectionString for SqlDataProviderERROR: Could not connect to database specified in connectionString for SqlDataProvider
Previous
 
Next
New Post
10/29/2006 2:11 AM
 

But I've received this instructions:

Error Installing DotNetNuke

Current Assembly Version: 04.03.05

ERROR: Could not connect to database specified in connectionString for SqlDataProvider

what I need to do now? can someone help me?

Change the string from .\SQLExpress to YOUR_MACHINE_NAME\SQLExpress

Cheers,

Jonathan.

 
New Post
3/14/2007 10:28 PM
 
For the recors, I used this to make it work:


You need to replace "WORKSTATIONS" with your real workstation name! And DotNetNuke is the name of your database, of course - if you do not have one you need to create it... It beats me why there needs to be the reference to attaching Database.mdf - but when I took that out I got errors!!!
Another pitfall - the security on database needs to be set correctly - use your SQL Serever Management Studio Express to tweak that - the easiest is perhaps to make ASPNET user the OWNER of the database "Dotnetnuke". Still, I could not work out how to make this work with a specific user not just ASPNET - when I tried that the connection error came up again...

My recommendation for the next version is to make this part a little bit more straightforward if possible - if there need to be two versions of web.config file (one for SQL SERVER, the other onefo r SQL SERVER EXPRESS) then it might help many new users.

 
New Post
10/29/2007 10:21 AM
 
Hi,
 
I read many people screaming for help when I also came across the same problem.
It took around 2 hours to crack the problem but finally it was done. Here is the solution for you guys…
 
My system configuration is: XP + VS2005 + SQL Server 2005 Express
 
 
Let’s start solving problem with few checks.
 
  1. You have unzipped the directory let’s say in d:\dnn
  2. Virtual directory let’s say dnn is created in IIS which points to d:\dnn\website
  3. Virtual directory has enough rights in IIS e.g. Read, Write, Execute….
  4. ASP.Net framework version number is 2.0.50727 in Asp.Net tab of IIS.
  5. In Directory Security tab of IIS we have Integrated Windows Authentication “checked”.
 
Now let’s check rights on the d:\dnn:\website directory
1.      Network full rights (in case d drive is NTFS).
2.      Network services full rights (in case d drive is NTFS).
3.      ASPNET account full rights.
4.      SQL Server (All 3 services) full rights.
Right click folder -> Properties -> security -> Add -> Advanced -> Find Now.
You will find 3 services starting with SQL. All should be given full rights.
 
One important thing to note is: I have database.mdf in my App_Data folder. 
 
Log into SQL server and detach database.mdf file.
Make sure that while detaching “Drop connection” and “Update Statistics” checkboxes are checked.
 
Now, make sure that
d:\dnn:\website\app_data has above mentioned rights as well.
 
Now go to d:\dnn:\website\app_data \database.mdf file and apply all above mentioned rights.
Same for d:\dnn:\website\app_data \database_log.ldf.
 
If they already have those rights then.. it’s fine.
 
Bingo…. You are done…
 
Make a request in the browser….    http://localhost/dnn/default.aspx
have patients… it will take some time…
 
Wait… still if it’s not done ?    …. Go to command prompt…. And type “iisreset”
 
Once again make request…. http://localhost/dnn/default.aspx
 
 
This solution worked for me … if you have Windows 2003 then you might have to look for some more settings…
 
I hope, I have not forgotten any steps in hastiness…  J
If so… write me back …
 
 
Cheers!
Sraddhan.
 
New Post
2/17/2009 10:21 AM
 

Brilliant! I ran into the same problems in my development environment after attaching /App_Data/Database.mdf in SQL Management Studio Express. Apparently the Management Studio messes up the file permissions when attaching.

 

The solution for me:

1) In Management Studio, detach the database with “Drop connection” and “Update Statistics” checked.

2) In Explorer, go to the Website/App_Data folder and grant that the [machinename]\ASPNET account full control to the .mdf and the .ldf files.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...ERROR: Could not connect to database specified in connectionString for SqlDataProviderERROR: Could not connect to database specified in connectionString for SqlDataProvider


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