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 ...3.2.2 Install Issues3.2.2 Install Issues
Previous
 
Next
New Post
1/12/2006 11:12 AM
 

When attempting to install 3.2.2 i am receiving the following error. 

Error Installing DotNetNuke
Current Assembly Version: 03.02.02
ERROR: Could not connect to database specified in connectionString for SqlDataProvider

Here is the install procedure i followed...

1. unzipped the file DotNetNuke_3.2.2_Source.zip to c:\DotNetNuke

2. Created a virtual directory called DNN322 for it in the IIS Manager pointing to c:\DotnetNuke

3. Set permission on the c:\DotNetNuke directory for ASPNET to "full control"

4. Created a new database in sql2000 called DotNetNuke and created the user NukeUser with ownership permissions on the db.

5. Renamed release.config to web.config and adjusted the connection string to this <add key="SiteSqlServer" value="Server=mycomputername;Database=DotNetNuke;uid=NukeUser;pwd=xxxx;" />

6. Opened a browser and opened the url 'http://mycomputername/DNN322' and then received the above error.

 

 

 
New Post
1/12/2006 1:38 PM
 

I've ran into the same problem after installing it several times before.

Which version of VS.NET and SQL Server do you have installed?

 

 
New Post
1/12/2006 2:37 PM
 
SQL 2000 and VS.NET 2003
 
New Post
1/16/2006 3:12 PM
 
jojopus wrote

When attempting to install 3.2.2 i am receiving the following error. 

Error Installing DotNetNuke
Current Assembly Version: 03.02.02
ERROR: Could not connect to database specified in connectionString for SqlDataProvider

Here is the install procedure i followed...

1. unzipped the file DotNetNuke_3.2.2_Source.zip to c:\DotNetNuke

2. Created a virtual directory called DNN322 for it in the IIS Manager pointing to c:\DotnetNuke

3. Set permission on the c:\DotNetNuke directory for ASPNET to "full control"

4. Created a new database in sql2000 called DotNetNuke and created the user NukeUser with ownership permissions on the db.

5. Renamed release.config to web.config and adjusted the connection string to this

6. Opened a browser and opened the url 'http://mycomputername/DNN322' and then received the above error.

 

 



I'm getting the same error too with DNN 3.2.2.  Any ideas?
Although I did a few things differently:
- I installed both SQL Server 2000 & 2005 on the same machine  as different named instances side-by-side.  Is this an issue?  So my connection string is:
"Server=<machine name>\MSSQL8;Database=test;uid=test_admin;pwd=password;"
- I've named by database test, which has user test_admin (owner)
- I've unzipped the source to D:\test, and pointed my IIS (v6.0) to D:\test (I created a new website as opposed to creating a new virtual folder using port 81)
- Browsed to http://localhost:81 and got the error

Please help!
 
New Post
1/16/2006 3:17 PM
 
jojopus wrote

When attempting to install 3.2.2 i am receiving the following error. 

Error Installing DotNetNuke
Current Assembly Version: 03.02.02
ERROR: Could not connect to database specified in connectionString for SqlDataProvider

Here is the install procedure i followed...

1. unzipped the file DotNetNuke_3.2.2_Source.zip to c:\DotNetNuke

2. Created a virtual directory called DNN322 for it in the IIS Manager pointing to c:\DotnetNuke

3. Set permission on the c:\DotNetNuke directory for ASPNET to "full control"

4. Created a new database in sql2000 called DotNetNuke and created the user NukeUser with ownership permissions on the db.

5. Renamed release.config to web.config and adjusted the connection string to this

6. Opened a browser and opened the url 'http://mycomputername/DNN322' and then received the above error.

After much trial and error, I had to do several things, but with Sql Server Express 2005.  You may try any of the following:

first get a better error.  Try turning remote errors off.

I had to end up moving my .mdf to a new location and givein the aspnet (or whatever version of os you use) and the mssql$computer access as well as the user I have.  if this helps experiment with which on you actually need.

Hard code the new path of your .mdf (c:\mypath)

I had to manually attach the database under databases, right click attach.

I also had to enable named pipes (I did this don't know if it was really necessary, but it was turned off).

Hope this helps some.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...3.2.2 Install Issues3.2.2 Install Issues


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