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 ...Upgrading DNN 5.2.2 to 5.5.1Upgrading DNN 5.2.2 to 5.5.1
Previous
 
Next
New Post
10/16/2010 3:59 PM
 
Due to a namespace ambiguity introduced in DotNetNuke 5.03.00, you must upgrade the XML module to v 04.03.05 or uninstall it prior to upgrading. If you had no other errors during the upgrade, you should also be able to delete all files from the App_Code\XML folder to stop the application (compilation) error from preventing access to the site then either upgrade or uninstall the XML module.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
10/16/2010 4:28 PM
 
Thanks Bill! You are the man... That was precisely the issue. The site upgraded with no further issues. I've also upgraded to the latest XML and Feedback (the reason I was upgrading DNN to begin with).

Thanks again for the help.
JR
 
New Post
10/18/2010 7:46 AM
 

Background:

It is highly recommended to the administrator to take a back up of the whole website and database along with web.config file before starting upgrade process. It is also good practice to upgrade your DNN version at your localhost and understood the process clearly before you move to your live site. After you get upgrade with the latest version, it is very essential to test the whole site along with all third party modules you have used in your site and look if all the modules are compatible and working fine with the latest version of DNN you upgraded with. It is really good to keep updating your DNN version once it is released by DotNetNuke group.

When To Upgrade:

If you are upgrade you site locally then you can upgrade it at any point of time. But if you upgrade your live site then it is good practice to upgrade your site when less number of user are access your site, preferably at midnight. If you are using install “User Online” module then you can easily track the user traffic of your site and do the upgrade process when less number of user are using your site.

Upgrading DotNetNuke:

I am here discussing the process of upgrade from DNN 4.9.4 to DNN 05.01.04. you can follow the same steps for upgrading from your current version to any latest DNN version.

~ Take a complete backup of your entire website.
~ Take a complete backup your database.
~ Take a back up your web.config file.
~ Rename the web.config file to backupweb.config
~ Take a back up your other files like custom error pages, fav.ico etc.
~ Download the DotNetNuke Install.zip (DNN 05.01.04) from the DotNetNuke site.
~ Unzip the downloaded Installation folder.
~ Open the web.config file of the newly downloaded folder (DNN 05.01.04)
~ Open the backupweb.config file.
~ Modify the SQL connection strings in web.config file. There are two places, you can get the string from your original backupweb.config file

(A) Copy the connection strings form backup file (backupweb.config) and paste is in web.comfig file under ConnectionStrings.

<connectionStrings>

<!-- Connection String for SQL Server 2005 Express -->

<add name="SiteSqlServer" connectionString="Data Source=458.236.25.29;Initial Catalog=MfsReport;User ID=userid;Password=password" providerName="System.Data.SqlClient" />

<!-- Connection String for SQL Server 2000/2005

<add name="SiteSqlServer" connectionString="Server=(local);Database=DotNetNuke;uid=;pwd=;" providerName="System.Data.SqlClient" />

-->

</connectionStrings>

(B) Copy the connection strings form backup file (backupweb.config) and paste is in web.comfig file under appsettings.

<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->

<add key="SiteSqlServer" value="Data Source=458.236.25.29;Initial Catalog=MfsReport;User ID=userid;Password=password" />

~ Copy the Machinekey ValidationKey and Decription key values from your backupweb.config file to web.config file.

<machineKey validationKey="8E04731852A7A16B1C70CE67CD4BE8B40A4B6A16" decryptionKey="E5499A1ED3D9AC245BCA138E8FBDC4286A3839D0C8DEFA0F" decryption="3DES" validation="SHA1" />

~ If you have made any further changes to your web.config file for third party modules, HTTP compression, or database object qualifiers, copy these changes across to the new web.config file from your backup.config file.

Note: If you upgrade the DNN version at your live site then make the

<add key="AutoUpgrade" value="true

" />

to

<add key="AutoUpgrade" value="fakse" />

So that user will not get any error message if they access your site at the same time when you do the upgrade process.
~ Save the web.config file.
~ Now the first file to move from the lastest version of DNN folder to the old version of DNN folder is dotnetnuke.dll file.

The reason is to inform your user that you are upgrading the website and it will now display an under construction page.

~ Now copy all the new file including web.config file and paste it at the old DNN folder.

~ Now run the site at browser with URL like http://www.mysite.com/Install/Install...

Note: I asummed the site name as mysite.com

~ Now application will triger the installtion process and you will see the message like “Upgrade Complete” and “Click Here To Access Your Portal”
~ Click on the link “Click Here To Access Your Portal” to access your portal.
~Login with Host account and go to 'Host Settings' then you will see the latest DNN vertion under “DotNetNuke Version” coloumn.

Thanks,

Debendra Nandi
Mindfire Solutions
www.mindfiresolutions.com

 
New Post
10/18/2010 8:53 AM
 
@Debendra -

Although your post includes many good tips for upgrading, please note that it has not been necessary to make any manual changes to or merge old and new web.config files when upgrading from version 4.06.02 or later. In fact, it is strongly discouraged due to the potental of introducing errors to the configuration file or causing automatic web.config file updates to fail. When upgrading, please use the appropriate upgrade package, not the install package. The upgrade packages by design do not include a web.config file.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrading DNN 5.2.2 to 5.5.1Upgrading DNN 5.2.2 to 5.5.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