Skip to content

How to Upgrade from DNN 4.x & up

by on September 14, 2010

Note: Upgrading does not change the core modules; you will need to change these individually!

Resources:

Upgrading from DotNetNuke 4.3.5 (and other 4.x versions) -> 4.4.1

http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/22/pageid/13.aspx

Upgrading to DNN 4.9.0 from 4.x

http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/244/pageid/123.aspx

Streamlined Upgrades from 4.6.2 and Later

http://www.mitchelsellers.com/blogs/articletype/articleview/articleid/216/pageid/114.aspx

Sourceforge DNN Versions Repository

http://sourceforge.net/projects/dnn/files/

This will follow an incremental upgrade:

  • From 4.4.0 or below to 4.4.1
  • From 4.4.1 to 4.6.2
  • From 4.6.2 to 4.9.3
  • From 4.9.3 to 5x (currently 5.4.2)

Note: When upgrading from 4.9.3 (and up) to later version (5x and up), follow Upgrade to 4.9.3 instructions

Upgrade to 4.4.1

1) Be sure site has been backed up ( DB and files)

2) Rename web.config to web.config.old (and be sure keep track of any custom core edits to fck editor, etc. so you can recreate it)

3) Get 4.4.1 Upgrade files from Sourceforge

4) The last item that you should do prior to starting the upgrade process is to create an "app_offline.htm" file (new > text > rename it app_offline.htm > put upgrade message on this page).  This is a simple HTML document that you can place in your DNN root directory and it will take your website offline.  This serves two purposes; first you prevent your users from experiencing any errors as the files are copying and secondly you prevent anyone else from accidentially triggering your upgrade process before all files are uploaded.  For my websites I simply put a notice that the site is temporarily unavailable due to upgrades in process, this same message will be displayed to visitors from ALL portals.  You MUST remove this file before you will actually be able to trigger the upgrade, that is why we will turn off "AutoUpgrade" later in this guide!

5) Extract files from 4.4.1 Upgrade package to website root folder

6) Confirm overwriting of folders

7) Rename release.config to web.config & update the following based on your web.config.old, use BeyondCompare or other file comparison tool

a. Connection strings

b. Machine Key & Validation keys

c. codesubdirectories

d. InstallationDate

e. Any Additional custom configs

f. Favicon.ico

8) Complete installation process by typing install directive into the browser (ex: http://www.yoursite.com/Install/install.aspx?mode=upgrade)

9) Check all modules

 

Upgrade to 4.6.2

1) Download 4.6.2

2) Follow steps above to rename (web.config.old2) & compare webconfigs, there will be more differences

3) Back up custom core files (favicon.ico, etc.)

4) Check if app_offline.htm is working (see above)

5) Extract to root folder, allow overwrite

6) Complete installation process by typing install directive into the browser

    (ex: http://www.yoursite.com/Install/install.aspx?mode=upgrade)

7) You may get an under construction message, simply repeat the above step

 

Upgrade to 4.9.3 (Valid for 5x & up, from 5x to 5x, etc.)

Note: For later upgrades, .Net 3.5 must be installed on server

1) Download 4.9.3 Upgrade

2) This is a little easier, duplicate web.config & rename it web.config.old3 ( there should be no need to compare after 4.6.2 due to XML merge capabilities)

3) Backup custom core files – favicon.ico, etc.

4) Check if app_offline.htm is working (see above)

5) Extract to root folder, allow overwriting

6) Remove, archive or rename app_offline.htm

7) Complete installation process by typing install directive into the browser

(ex: http://www.yoursite.com/Install/install.aspx?mode=upgrade)

8) You may get an under construction message, simply repeat the above step

 

Install Upgraded Modules

1) Be sure entire site has been backed up

2) Go to host settings > module definitions

3) You should find necessary core module upgrades in the “available modules” section at the bottom of the page. If not:

a. Click on green link or navigate to http://www.dotnetnuke.com/tabid/125/default.aspx

b. Download the latest compatible version to Proteus > DNN Installations & Upgrades > CoreModules

c. Install as any third party module

d. Check for successful installation

4) Check off relevant modules

5) Click install

6) Check for version issues on site

Advertisements
3 Comments
  1. how it create page name with (-) in dnn
    LIKE : http://www.youchange.com/how-it-works.aspx

    thanks

    • Not sure why you would want to…

      Most search engines have no problem pulling words out of page names. That is the only reason I could think to bother with this.

  2. Brian permalink

    Hi, can you help me with this error? Upgrade from dnn 4.4.1 to 4.6.2 step by step and its work, but when I go to the main page appears this error

    Server Error in ‘/DotNetNuke’ Application.
    ——————————————————————————–

    Object reference not set to an instance of an object.
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [NullReferenceException: Object reference not set to an instance of an object.]
    DotNetNuke.Entities.Portals.PortalSettings.GetSiteSetting(Int32 PortalId, String SettingName) +66
    DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +2389
    System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +79
    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +170

    Please help me!!!!!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: