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 ...upgrade from 2.1.1upgrade from 2.1.1
Previous
 
Next
New Post
7/9/2008 2:59 PM
 

I recently inherited an intranet site created with DNN 2.1.1.  We are going to be upgrading our SQL Server from 2000 to 2005.  Do I need to upgrade DNN?  If so, what is my upgrade path?

 

Thanks,

Mike

 
New Post
7/9/2008 3:44 PM
 

The problem is I know nothing about DNN.

When I look at my web.config file I am not seeing the keys that I am supposed to replace as per installation guide......

"Replace the following keys in your new web.config, with the values in your backup. 

SiteSqlServer

MachineValidationKey

MachineDecryptionKey

InstallationDate (this may not be present in web.config, so add the key

Any help would be appreciated.

that is in web.backup.resources to web.config)"

 
New Post
7/9/2008 4:01 PM
 

Based on the "I know nothing about DNN" my first reaction is to suggest that you hire someone knowledgeable about DNN to do this for you.

There are legacy versions of DotNetNuke on SourceForge that go back as far in time as your installation.

If you want to upgrade, you'll probably want to upgrade first to a 3.x version, then to 4.x, and then to 4.6.2.  From there you can jump to the current version.  There may be some steps in between, but I do know (and you can tell from the matching timestamps on the versions) that there were a series of 3.x and 4.x versions that differed only in the ASP.NET version required.  So, it's easy to go from 3.x to the corresponding 4.x version.

And, assuming that you don't have custom modules to any great degree, someone who knows what they are doing should be able to do this update for you with 2 or 3 days of work -- and I'm kind of wagging a wet finger in the wind to make this estimate.  Certainly the size of the site, what modules you are using, available resources, etc. will be important.




Joe Craig
Patapsco Research Group, Ellicott City, MD
DotNetNuke Development and Services (http://patapscorg.com)
 
New Post
7/9/2008 5:39 PM
 

Michael wrote

The problem is I know nothing about DNN.

When I look at my web.config file I am not seeing the keys that I am supposed to replace as per installation guide......

"Replace the following keys in your new web.config, with the values in your backup. 

SiteSqlServer

MachineValidationKey

MachineDecryptionKey

InstallationDate (this may not be present in web.config, so add the key

Any help would be appreciated.

that is in web.backup.resources to web.config)"

Erik has some good general instructions @ http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1459/Default.aspx

I agree that you're better to upgrade to a 3.x release first, then follow instructions to switch to asp.net 2.0 (http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/106/upgrading-dnn-3x-to-dnn-4x.aspx and http://www.ventrian.com/Resources/Blog/tabid/243/articleType/ArticleView/articleId/335/Upgrading-DotNetNuke-3x-to-4x.aspx are both good guides to read).

As for the values you mean, they were only introduced in 3.0 -the only value you need to bring across is the connection string details from 2.12 and set it for both SiteSqlServer values.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
7/9/2008 5:43 PM
 

Michael wrote

I recently inherited an intranet site created with DNN 2.1.1.  We are going to be upgrading our SQL Server from 2000 to 2005.  Do I need to upgrade DNN?  If so, what is my upgrade path?

 

Thanks,

Mike

never noticed the first post - you do not need to upgrade your dotnetnuke version to use sql 2005, all you need to do is change the connection string, and then do a backup of your sql 2000 database and restore it to sql 2005 just like a normal restore.

Cathal


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade from 2.1.1upgrade from 2.1.1


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