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 ...DNN vs SQL.... Someone isnDNN vs SQL.... Someone isn't happy
Previous
 
Next
New Post
5/16/2006 8:11 AM
 

Blonde ? You blond too??  Ok - I actually edited it, but normally as moderators we quickly check the connection strings to make sure they are commented out and we also do this because people sometimes forget, but it has been removed and it was done as soon as I saw that post.. Thanks to you guys for watching out for this too. It's much appreciated.

Nina Meiers


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
5/16/2006 11:50 AM
 
Dkingsley wrote

I would suggest uncommenting the appropriate legacy connection string and setting the values in the string.

I was having the same problem and that seemed to solve it for me... It's easy to miss both connection strings.  For future reference, if you're running SQL Server 2000 these are the only connection strings in the webconfig that shouldn't be commented:

<connectionStrings>

<!-- Connection String for SQL Server 2000/2005-->

<add name="SiteSqlServer" connectionString="Server=YourServer;Database=DotNetNuke;uid=YourUID;pwd=YourPWD;" providerName="System.Data.SqlClient" />

</connectionStrings>

<appSettings>

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules -->

<add key="SiteSqlServer" value="Server=YourServer;Database=DotNetNuke;uid=YourUID;pwd=YourPWD;"/>

Note:  You'll want to keep the rest of the keys in appsettings, just make sure the SqlExpress connection string is commented out and the 2000/2005 is enabled with the pertinent information in the values tag.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN vs SQL.... Someone isnDNN vs SQL.... Someone isn't happy


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