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 http://www.laksha.net/Dotnetnuke.aspx to http://blog.laksha.net.]

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. http://www.lakshadev.net. 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 DotNetNuke.com 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 http://www.websitename.com/install/install.aspx?mode=install e.g. http://www.lakshadev.net/install/install.aspx?mode=install. 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:

    image 

    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

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/168/scope/threads/Default.aspx.




Comments

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 the correct value. The WebPartName.we…

How To Create Virtual Machine Using Existing vmdk file in VMWare Workstation

vmdk file is hard disk of the VMWare virtual machine. There are many scenarios where you may need to create a new virtual machine for an existing vmdk file. This is also an alternate Method to the “vmx is not a valid virtual machine configuration file – Could not open virtual machine” issue.Please refer to the previous post “Could not open virtual machine – vmx is not a valid virtual machine configuration file” for a full list of possible resolution. This post is to describe one of the solution in more details. How To Create a new virtual machine & attach the existing .vmdk file:1. Open VMware and select create a new virtual machine with custom (advanced) configuration option.2. Chose “I will install the operating system later”. and chose “I will install the operating system later”. 3. Select the operating system that matches the operating system in your existing .vldk file.4. Select a location of the new virtual machine5. Chose “Use an existing virtual disk”. This will allow yo…

How to Fix WordPress Site Address (URL)

If you are caught in middle between changing your WordPress website/blog URL - Site Address (URL) setting in the WordPress then there is a simple solution available to override WordPress Site Address (URL) values that is saved in database. You need access to the wp-config.php file which can be found in the root of your WordPress install. Make sure you make a back up copy of this file before you open it. If you are using shared hosting, then please use control panel provided by hosting company or use FTP application such as FileZilla.
Open the wp-config.php file and add following lines to this config file where the “http://example.com/” is the URL you want to access.
define( 'WP_SITEURL', 'http://example.com/' );

define( 'WP_HOME', 'http://example.com/' );

This should solve your issue with WordPress Site Address URL. If this post helped you then please let me know.