Since the last 05.02.01 GRANT EXECUTION failure, more than 80% of DNN users had problems upgrading. but the last 05.02.02 upgrade is a GREAT SUCCESS. I´ve seen that many users are in trouble upgrading from different versions, i say that you should take a deep breath and double check you configurations. In the last hour i was upgrading two DNN instalations to the last 5.2.2... one from 5.1.4, and one from 5.2.0.

Upgrading from 05.02.00 to 05.02.02:

1. STOP your web application from your hosting provider CP

2.RECYCLE APP POOL from your hosting provicder CP (optional but can help in performance)

3.BACKUP you site and your SQL.DB

4.COPY and OVERWRITE the content of your site with the content of the last update DotNetNuke_Community_05.02.02_Upgrade...

5. START your web application from your hosting provider CP

6. Before anything else go to   http://ww.yoursite.???/install/instal...   to install and finish the upgrade.

If everything went well you should see something like this:

Upgrading DotNetNuke

Current Assembly Version: 05.02.02

Current Database Version: 05.02.00

Upgrade Status Report

00:00:00.046 - Upgrading to Version: 05.02.02
00:00:00.359 -   Executing Script: 05.02.01.SqlDataProvider Success
00:00:02.641 -   Executing Script: 05.02.02.SqlDataProvider Success
00:00:03.126 -   Executing Application Upgrades: 05.02.01 Success
00:00:03.235 -   Executing Application Upgrades: 05.02.02 Success
00:00:03.235 -   Cleaning Up Files: 05.02.01 Success
00:00:03.235 -   Cleaning Up Files: 05.02.02 Success
00:00:03.235 -   Updating Config Files: 05.02.01 Success
00:00:03.251 -   Updating Config Files: 05.02.02 Success
00:00:03.251 - Performing General Upgrades
00:00:03.704 - Installing Optional Modules:
00:00:03.720 -   Installing Package File HTML_Community_05.02.00_Install:  Success
00:00:04.532 - Installing Optional Skins:
00:00:04.532 - Installing Optional Containers:
00:00:04.532 - Installing Optional Languages:
00:00:04.532 - Installing Optional Providers:
00:00:04.532 -   Installing Package File AspNetMembershipProvider_05.02.00_Install:  Success
00:00:04.642 -   Installing Package File CorePermissionProvider_05.01.01_Install:  Success
00:00:04.767 -   Installing Package File DatabaseLoggingProvider_05.01.01_Install:  Success
00:00:04.845 -   Installing Package File DNNMembershipProvider_05.01.03_Install:  Success
00:00:05.001 -   Installing Package File DNNMenuNavigationProvider_05.01.00_Install:  Success
00:00:05.111 -   Installing Package File DNNTreeNavigationProvider_05.01.00_Install:  Success
00:00:05.236 -   Installing Package File FckHtmlEditorProvider_02.00.04_Install:  Success
00:00:07.455 -   Installing Package File FileBasedCachingProvider_05.01.03_Install:  Success
00:00:07.565 -   Installing Package File FileModuleCachingProvider_05.02.01_Install:  Success
00:00:08.049 -   Installing Package File MemoryModuleCachingProvider_05.02.01_Install:  Success
00:00:08.362 -   Installing Package File SchedulingProvider_05.02.01_Install:  Success
00:00:08.768 -   Installing Package File SearchIndexProvider_05.01.00_Install:  Success
00:00:08.940 -   Installing Package File SearchProvider_05.01.01_Install:  Success
00:00:09.253 -   Installing Package File SolpartMenuNavigationProvider_05.01.00_Install:  Success
00:00:09.503 - Installing Optional AuthSystems:
00:00:09.503 -   Installing Package File LiveID_01.00.01_Install:  Success
00:00:09.737 -   Installing Package File OpenID_02.00.00_Install:  Success
00:00:09.925 - Installing Optional Packages:
 

Upgrade Complete

Click Here To Access Your Portal

------------------------------------------------------------------------------------------------------

As for the other site, the 05.01.04 for some reasons did not work with a direct upgrade to the 05.02.02 and so i´ve upgraded first to the 05.02.00 and then to the last 05.02.02... those instalations worked for me on a WS2008 platform and if you follow a good configuration is almost impossible to fail.

Thanks goes to the DNN Community!

   When i first install DNN the web.config file was modified to stop the autoupgrade following a tutorial from Mitchell Sellers. Thanks for the app_offline.html file method Sebastian, is good to know.

Hi Fanny,

to create app_offline.htm create a new file using your preferred text editor (e.g. famous  Notepad.exe). Enter

<html>
   <head><title>Offline for Maintenance.</title>
   </head>
   <body>
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
We apologize, this site is curremtly offline for maintenance. Thank you for your patience.
</body>
</html>

You can display any content (text or images), but make sure, file size it at least 512 byte.
Save file named app_offline.htm in the root of your IIS web site.