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 3.3.5 - SQL2005 Connection string errorDNN 3.3.5 - SQL2005 Connection string error
Previous
 
Next
New Post
7/6/2007 4:08 PM
 

In order to upgrade my DNN install I need to move it to another server.  I am having difficulty with the move.
Here is what is happening:

Current: DNN 3.3.5 - MS 2000, SQL2000 
Connection string:  <add key="SiteSqlServer" value="Server=(local);Database=DBName;uid=SQLUser;pwd=SQLPassword;" />

 

New: DNN 3.3.5 - MS 2003, (SQL2005 on separate machine),
Connection string: <add key="SiteSqlServer" value="Server=ServerName;Database=DBName;uid=SQLUser;pwd=SQLPassword;" />

I have tested connecting remotely to the database via VS and it works.
I have tested using both .net frameworks, and have tested using SQL 2000 compatability.

Still when I try to connect I get the following error:

DotNetNuke Upgrade Error

The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Any help getting this working would be appreciated.

 
New Post
7/6/2007 7:48 PM
 

Take a look at your Sql Server logs to see if you can find a hint about the problem. Also make sure that Sql server is running on the default Tcp/ip port 1433.

 
New Post
7/9/2007 1:42 PM
 

penra wrote

Take a look at your Sql Server logs to see if you can find a hint about the problem. Also make sure that Sql server is running on the default Tcp/ip port 1433.

I Just checked the logs.

First, there is a messages stating that the SQL server is listening on Port 1434.

Second, No SQL log entries are made on the SQL server when I attempt to start the site(resulting in the message above).

 
New Post
7/9/2007 4:53 PM
 

It would seem that DNN is not reaching the Sql server. The error about Named Pipes makes me wonder if Tcp is enabled in sql server?

 
New Post
7/10/2007 10:08 AM
 

So, Your post got me thinking.

This is a new server and the SQL server is separate and not in our DMZ while our web server is.

I looked and determined that our firewall was blocking the needed ports.

Thanks for your assistance.  Everything is up and running now.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN 3.3.5 - SQL2005 Connection string errorDNN 3.3.5 - SQL2005 Connection string 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