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 ...v3.3.4 SqlDataProvider errorv3.3.4 SqlDataProvider error
Previous
 
Next
New Post
9/13/2006 1:36 PM
 
Hello all

I am attempting a fresh install of v3.3.4 and when trying to get the install to run, I get the following error  "Error Installing DotNetNuke
Current Assembly Version: 03.03.04
ERROR: Could not connect to database specified in connectionString for SqlDataProvider"

This is my SqlDataProvider String:

<add key="SiteSqlServer" value="Server=afe-srv01;Database=DotNetNuke;uid=kmachula;pwd=password;" />

I am using the name of the server as well as the name of the database which I created in SQL2000

Any assitance would be greatly appreciated.

Thanks
 
New Post
9/13/2006 5:46 PM
 
If your connection settings are correct, the most likely reason is that the user running the .net process does not have rights on the database.

 
New Post
9/14/2006 10:27 AM
 
I am not entirely sure what you mean by that. I checked which user is running the .NET service and that is "NetworkService" so I gave that user rights on the database. I have a feeling this is not what you meant though.
 
New Post
9/14/2006 7:25 PM
 
No, that is what I mean...
I guess you gave the user dbo rigthts....?
Hmmm... I don't know.....
I guess you checked your userid and pw a 100 times.....

I'll just throw in some suggestions which you probably already thought of.

Firewall blocking te access to the SQL Server?
Did you install the SQL server with the "Windows authentication only" option?
Then you will have to use:    ...........Database=Dotnetnuke;Trusted_Connection=true;
Did you try creating a simple ASP.NET testpage to check the connection to the database?

 
New Post
9/14/2006 11:56 PM
 
I did give the user dho rights. and I have also checked and rechecked the password a few hundred times.

The SQL server is on the same machine that I'm installing DNN on so a firewall wouldn't matter.

I honestly can't remember how the SQL server was installed as it was installed by an accounting software firm. I will try adding in the trusted connection bit and see if that helps.

I have not made any test pages as I honestly have no idea how to do it. I am what we call webpage retarded. Basically I need to install DNN so that a paid web developer can login and make my client a website. Times like this really makes me wish I had more knowledge on this subject though.

Btw, I really do appreciate all the ideas and suggestions you've thrown my way. Thanks :)
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...v3.3.4 SqlDataProvider errorv3.3.4 SqlDataProvider error


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