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 ...DotNetNuke Upgrade Error on previously working siteDotNetNuke Upgrade Error on previously working site
Previous
 
Next
New Post
3/9/2007 11:13 AM
 

I have a DNN4 site running on Windows 2003 server with a SQL Server2000 DB. It has been running great until about an hour ago when Microsoft-released Security patches were installed. The site now give the following error. Any ideas? Oh, NO upgrade was performed on DNN. The installation has been untouched.

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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)

 
New Post
3/12/2007 10:15 AM
 

Seems to be something with your database connection.
Check if your connection string is setup correctly.
Perhaps you should check the install documentation of DNN for the correct format.

    <add name="SiteSqlServer" connectionString="Server=[SERVERNAME];Database=[DATABASENAME];uid=[DATABASEUSER];pwd=[DATABASEUSERPASSWORD];" providerName="System.Data.SqlClient" />

Perhaps your [SERVERNAME] was (localhost) and should now be the REAL servername or something.

Perhaps you could look if something changed the SQL Server Configuration Manager settings or something

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke Upgrade Error on previously working siteDotNetNuke Upgrade Error on previously working site


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