Skip to main content

Dotnetnuke 05.01.00 Upgrade Screenshot

[PS: As part of consolidation, I am moving all my Dotnetnuke & SharePoint related blog post from to]

NOTE: BETA versions of DotNetNuke 05.01.00 are NOT to be used for production sites. Also always do the testing first on a development envirnment e.g. I have created a copy of my website at my local machine using host file. Also always ensure you backup your sites and data before attempting any upgrade. 

This post cover upgrade from Dotnetnuke 04.09.02 to Dotnetnuke 05.01.00.

Upgrade Steps:

  • Download the UPGRADE package for the 05.01.00 version of DotNetNuke from the website. Please note download UPGRADE package.
  • Take a backup of your current Dotnetnuke installation folder (website folder).
  • Unzip it UPGRADE package over your existing Dotnetnuke installation folder (website folder). This will update all DotNetNuke core files and prepare you to install the upgrade.
  • Open e.g. This will start the upgrade wizard.  All needed web.config changes will be merged and your site will be upgraded. 
  • Once upgrade complete you will see a success message as shown bellow. Note any error message you may see. In my case I saw following errors:


    Text version of success and error messages:

    Upgrading DotNetNuke

    Current Assembly Version: 5.1.0

    Current Database Version: 04.09.02

    Upgrade Status Report

    00:00:00.034 - Upgrading to Version: 5.1.0
    00:00:00.076 -   Executing Script: 05.00.00.SqlDataProvider Success
    00:00:08.163 -   Executing Script: 05.00.01.SqlDataProvider Success
    00:00:09.388 -   Executing Script: 05.01.00.SqlDataProvider Error! (see 05.01.00.log for more information)
    00:00:11.896 -   Executing Application Upgrades: 5.0.0 Success
    00:00:24.450 -   Executing Application Upgrades: 5.0.1 Success
    00:00:24.464 -   Executing Application Upgrades: 5.1.0 Success
    00:00:24.586 -   Cleaning Up Files: 5.0.0 Success
    00:00:24.962 -   Cleaning Up Files: 5.0.1 Success
    00:00:24.988 -   Cleaning Up Files: 5.1.0 Success
    00:00:25.045 -   Updating Config Files: 5.0.0 Success
    00:00:25.048 -   Updating Config Files: 5.0.1 Success
    00:00:25.049 -   Updating Config Files: 5.1.0 Success
    00:00:25.054 - Performing General Upgrades
    00:00:25.620 - Installing Optional Modules:
    00:00:25.623 - Installing Optional Skins:
    00:00:25.627 -   Installing Package File DNN-MinimalExtropySkin_01.00.02_Install:  Error!
    00:00:26.293 - Installing Optional Containers:
    00:00:26.293 -   Installing Package File DNN-MinimalExtropyContainer_01.00.02_Install:  Error!
    00:00:26.417 - Installing Optional Languages:
    00:00:26.418 - Installing Optional Providers:
    00:00:26.469 -   Installing Package File AspNetMembershipProvider_05.01.00_Install:  Success
    00:00:26.632 -   Installing Package File CorePermissionProvider_05.01.00_Install:  Success
    00:00:26.722 -   Installing Package File DatabaseLoggingProvider_05.00.00_Install:  Success
    00:00:26.861 -   Installing Package File DNNMembershipProvider_05.01.00_Install:  Success
    00:00:26.944 -   Installing Package File DNNMenuNavigationProvider_05.01.00_Install:  Success
    00:00:27.022 -   Installing Package File DNNTreeNavigationProvider_05.00.00_Install:  Success
    00:00:27.104 -   Installing Package File FckHtmlEditorProvider_02.00.03_Install:  Success
    00:00:37.334 -   Installing Package File FileBasedCachingProvider_05.01.00_Install:  Success
    00:00:37.435 -   Installing Package File SchedulingProvider_05.01.00_Install:  Success
    00:00:37.511 -   Installing Package File SearchIndexProvider_05.00.00_Install:  Success
    00:00:37.576 -   Installing Package File SearchProvider_05.01.00_Install:  Success
    00:00:37.702 -   Installing Package File SolpartMenuNavigationProvider_05.00.01_Install:  Success
    00:00:37.928 - Installing Optional AuthSystems:
    00:00:37.928 -   Installing Package File LiveID_01.00.01_Install:  Success
    00:00:39.443 -   Installing Package File OpenID_02.00.00_Install:  Success
    00:00:39.960 - Installing Optional Packages:


  • Now click at browse your website link. Regardless of above error you should see your website working fine. Test all the pages and functionality.image

Following are open issues:

Dotnetnuke 05.01.00 Beta – Upgrade Issues 1 – Host->Module Definition page are blank
Dotnetnuke 05.01.00 Beta – Upgrade Issues 2 – Error on Host->Dashboards page

Discuss 05.01.00 Beta Testing at


Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get

TIME – 25 Best Blogs of 2009

Every year Time makes a list of best blogs in the world. They chose 25 blogs from millions of blogs in the world, spanning politics, housekeeping, astronomy and everything in between. Below if a direct link to the TIME website for the list. I also copied it to easy comparison of last year best with this year best blogs.   25 Best Blogs of 2009     25 Best Blogs 2008   25 Best Blogs of 2009 Talking Points Memo The Huffington Post Lifehacker Metafilter The Daily Dish by Andrew Sullivan Freakonomics BoingBoing Got2BeGreen Zen Habits The Conscience of a Liberal: Paul Krugman Crooks and Liars Generación Y Mashable Slashfood Official Google Blog synthesis bleat /Film Seth Godin's Blog Deadspin: Spor

Howto Run Your HTML Static Website Locally In IIS On Windows PC

WHAT & WHY: As a developer many time you may wish if you could run your static HTML website locally on your computer (Windows 7, Windows Vista, Windows XP, Windows 2008). Although with Static website, you could easily download and double click the index.html or home.html file to open and run other pages. But this will not give you the real world senario. For example you will not able to use a path like /images/home-page-banner.jpg. You will have to use a relative paths like ../images/home-page-banner.jpg. Following are very easy steps to do so. These steps are for Static HTML website. I will also post steps for more advance websites that uses ASP, ASP.NET, Dotnetnuke etc and uses database server.   WHAT YOU NEED: 1. IIS Server installed on your local machine 2. FTP username, password to download files form your FTP server 3. Administrative rights on local machine. Many task will display messages requesting Administrative privilege to run the task.    STEPS: 1.