DNN Blog

This is how I upgrade a DNN instance.

by Chris Hammond on Friday, December 29, 2006 3:48 AM

THIS IS AN OLD BLOG POST, for my latest instructions on How to Upgrade DotNetNuke check out this new post.

I see this requested all the time, so I figured I'd blog how I proceed with upgrading a DNN Instance.

If you're upgrading your DotNetNuke instance, here is a list of simple steps to follow during the upgrade process.

First tip, test the upgrade on a staging site first, pull a copy of the database and files down, try the upgrade, make sure all your functionality is still there. Then upgrade production (backup everything first)

 

Here’s the steps to upgrade

 

1.       Backup the database.

2.       Backup the file system.

3.       Make sure you did 1 & 2

4.       Extract the latest DNN ZIP file somewhere, i usually use the installation package, not the upgrade package out of preference.

5.       Edit the web.config file from DNN package

a.       Modify the SQL connection strings, there are two places, you can get the string from your original web.config

b.      Be sure to copy the Machinekey ValidationKey and Decription key values from your original web.config file

c.       Double check the DatabaseOwner and ObjectQualifier values in the web.config file, if you changed them in your original web.config file you’ll need to change them in the new one.

d.      Make any other changes to the new web.config that you added to the original config file, anything your custom modules required? codeSubDirectories node perhaps?

6.       Copy the new files, including the changed web.config file, over the old files.

7.       Load the website, this will cause the upgrade to begin when the page loads. Make sure the upgrade process completes successfully.

8.       At this point you should be done.

 

Like I said, test first, just to be sure you have everything working properly.

Hope these steps help, I've upgraded many a DNN website, and even a few today.

UPDATE 6/2008: Check out a more recent blog post I made about upgrading newer versions of DNN.

UPDATE 6/2010: THIS IS AN OLD BLOG POST, for my latest instructions on How to Upgrade DotNetNuke check out this new post.

Chris Hammond
Author

Chris Hammond has been working with DotNetNuke since January of 2003. He has created hundreds of videos, blog posts, and tutorials for DotNetNuke. Be sure to chat with Chris at dnnCHAT.com

35 comment(s) so far...

Sebastian Leupold 12/30/2006

Please be aware, that an upgrade from DNN3 to 4 requires additional steps:
- delete all existing .vb source code files prior to copying over new files
- in IIS configuration of web site / virtual directory set ASP.Net version to 2.0 and make sure, the app pool is not shared with ASP.Net 1.1 applications.

 
Chris Hammond 12/30/2006

Good tips Leupold, thanks for the input.

 
totti37 12/31/2006

Hi Chris,

little great Blog Entry. I work with WinMerge to find the difference between new and old web.config.

Thanx's and a happy new year from Berlin (Germany)

 
Shawn Mehaffie 1/1/2007

Amen on steps #1 and #2. It amazes me how many will update a mission critical production server without staging an upgrade first to make sure it all works as expected.

Also, do not forget to add an alias for the staging URL to the aliases tablee in the staging database.

 
David Hanousek 1/1/2007

As I found that, after some time, it can become really tedious to extract custom changes from web.config, I do it in the reverse way: I add new things from new web.config to my "good old" web.config. For the purpose of comparison of web.configs in various DNN versions, see my page dedicated to it: www.pcsecurity.cz/dnn.

 
Mike Grace 1/4/2007

Chris,

Why do you use the install package instead of the upgrade package? What is the difference?

 
Chris Hammond 1/4/2007

MS, I believe the upgrade package doesn't include modules, but I'm not positive on that one. I've always used the Install package, so it's just easier to keep using the same methods I've followed for years performing upgrades.

 
Anonymous 1/5/2007

Surely if you overwrite all the folders, all your modules (in the bin and provider older) will be over written?

 
Chris Hammond 1/5/2007

I'm not following your problem Drew? If you extract the Install package, the modules are located in the Install folder, they get reinstalled, updating any of the core modules with the newer versions.

If you don't want to upgrade the modules, you can remove them from the install/modules folder. Either way, copying over the folders doesn't touch the module files in the BIN or Providerfolder. Unless of course you modified Core Provider files, of which I don't recommend when dealing with client work.

If you need to make changes to the FriendlyURL provider for example, I recommend creating a new project with new namespaces, for your new provider, that way, when you upgrade a DNN instance the changes to the core provider don't overwrite your changes.

 
B Neel 1/9/2007

I have 2.1.2, Need to upgrade it to any higher version with Access database, can some let me know what version can i upgrade to 3.3 or 4.4 ??

 
Chris Hammond 1/9/2007

Neelbh, there aren't any (that I know of) access providers for any versions newer than DNN 2.1.2. You could potentially write your own, but I'd suggest investing your time in converting from access to SQL server and upgrading.

 
Anonymous 1/9/2007

I gave a presentation last night to the C# User's Group here in St. Louis on how to get started with C# module development in DotNetNuke. I said I'd put together a blog post with some resources, so he ...
# Chris Hammond

 
Anonymous 2/7/2007

On a busy site, what will happen someone loads your site while you still coping files over in 6? Do you have to shut down the site for an upgrade?

 
Anonymous 2/13/2007

Any suggestions on upgrading an older version? I have a version 1.0.10 in the database Version table...

 
Joe Schmo 2/7/2007

Not sure if my last post made it. Any ideas on upgrading a 1.0.10 (db version table) site to latest release (4.4.0)?

 
Chris Hammond 2/7/2007

Kurt, my recomendation to you, test the heck out of it first. You should be able to upgrade and go, but I'd test it before I touched the production instance.

 
Joe Schmo 2/13/2007

FYI. The upgrade did not go well. All modules failed to load, the only thing that looked like it worked was the menus. I'll probably just end up installing a new 4.4 instance and manually porting the sites.

 
Kurt Meredith 5/4/2007

I found that, in order to create a seprate version of my site for testing, I had to change several settings in order to get the test site working. The URL in the PortalAlias table of the database had to be changed to the test site URL, and I ended up having to give the test site a different cookieName in the web.config.

 
Chris Hammond 5/4/2007

The cookie thing may just be related to "localhost", at least that's what I'm guessing Kurt, but yes, you will need to change the PortalAlias, thanks for the heads up.

 
Anonymous 12/27/2007

Well, the 4.8.0 release of DotNetNuke came out today, and some people are having some problems, so I figured I'd take the time to put together what I hope will be a short post with my professional opi ...
# Chris Hammond

 
Ariane 8/21/2008

what about the skins and containers? if the files are overwritten - would those be lost in the upgrade process?

 
Chris Hammond 8/21/2008

If you've modified the Core skins then yes they would be overwritten, if you haven't modified the core but are using custom skins, they wouldn't be included in the upgrade package so they wouldn't be overwritten.

 
Anonymous 1/28/2009

Tnx very good

 
dnndev 1/29/2009

how would you upgrade if you modified some dnn core files ?

 
Chris Hammond 1/29/2009

I wouldn't modify core files ;)

 
ponki.d.monkey 4/13/2009

Hi, we have a DNN version 04.09.00. Can we upgrade it to version 05.00.01by following the steps you provided above? We're not really sure how to upgrade a DNN instance and we're just doing this to use LINQ in one of our modules...

 
Chris Hammond 4/13/2009

Monkey, I would simply extract the UPGRADE package over your current site to upgrade, after backing everything up of course.<br>Though I would only go to 4.9.3, not .5.0.1

 
ponki.d.monkey 4/14/2009

Thanks for the advice, Chris. By any chance, do you know if LINQ would work on version 4.9.3?

 
Chris Hammond 4/14/2009

monkey, I believe you can manually upgrade DNN 493 to 3.5sp1 if you want, the source is available so you can do what you wish with it ;) <br>

 
ponki.d.monkey 4/14/2009

Ok great. Thanks again, Chris!

 
Debendra Nandi 12/29/2009

Good Information

 
Armando Quiroz 4/7/2010

Hi, the site that i receive is in DNN 455 ¿what can i do if i wish upgrade to DNN 531? (i need to install an intermediate version?) thanks

 
bill huber 5/13/2010

Are there extra steps to do the upgrade from 4.0 to the latest version. I tried and it made some refrences to...<br><br>Could not load file or assembly 'System.Web.Extensions, Version=3.5.0.0... asking for a earlier version. <br><br>When i tried just copying the install files over the old version it made an error refrence to the global.asax...<br><br>What am i missing?

 
Papayas 5/19/2010

Bill, <br><br>Please make sure that your web.config has correct references for old "System.Web.Extensions" versions:<br><br><br><br><br><br><br><br><br><br>Such command in web.config should help you.<br><br>Also if you want to proceed with automatic DotNetNuke upgrade, you can use our module DnnAutoUpgrade: www.company.papayas.ru

 
sunil shetty 10/8/2010

Hi Chris,<br /> This is sunil here, i am trieng to upgrade from dnn5.2.2 to dnn5.4.4 and dnn5.4.4 to 5.5.1 locally. In both the case's i am getting same error. It shows the upgrade screen when i do give<br /><br /><br />"http://localhost:50264/upg/Install/Install.aspx?mode=install"<br /><br />Current assembly version: 05_05_01<br />Current Database version: 05_04_04 <br /><br />Upgrade Status Report<br /><br />"Install package file Telerik_05_05.00_Install" for 5.5.1<br />"Install package file Telerik_05_04.00_Install" for 5.4.4<br /><br />for both cases.<br /><br />I hope you wil help me out in this in finding out what i am doing wrong in this one.

Attend A Webinar
Start  Professional Edition Trial
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke (DNN) provides a suite of solutions that make designing, building and managing feature-rich sites and communities fast, easy and cost-effective. The DotNetNuke Platform CMS is the foundation for more than one million websites worldwide. DNN Social, our newest solution, enables businesses to create immersive, interactive communities. Thousands of organizations like True Value Hardware, Bose, Cornell University, Glacier Water, Dannon, Delphi, USAA, NASCAR, Northern Health and the City of Denver have leveraged DNN to deploy highly engaging business- critical websites. Our rapid growth in product sales and deployments resulted in DotNetNuke Corp. being named one of the fastest growing private companies in America by Inc. Magazine in 2011 and 2012.