I know it's not their fault...  And DNN isn't magic, it just seems that way between upgrades...

I cannot go forward in steps easily on GoDaddy, but I can go from 5.5.1 to 5.6.2 and then step back to 5.6.1 and then to 5.6.0.  From this I get to effectively a 5.5.1 to 5.6 install, with the following errors:

00:00:03.937 - Installing Optional Modules:
00:00:03.937 -   Installing Package File HTML_Community_05.01.03_Install:  Error!
00:00:04.156 -   Installing Package File HTML_Community_05.01.04_Install:  Error!
00:00:04.265 -   Installing Package File HTML_Community_05.06.00_Install:  Success
00:00:04.781 -   Installing Package File HTML_Community_05.06.01_Install:  Success
00:00:05.078 -   Installing Package File HTML_Community_05.06.02_Install:  Success

AND

00:00:10.500 -   Installing Package File CoreSitemapProvider_05.06.01_Install:  Success
00:00:10.578 -   Installing Package File CoreSitemapProvider_05.06.02_Install:  Success
00:00:10.656 -   Installing Package File CoreSitemapProvider_5.6.0.0_Install:  Error!

In both cases I thought I might be OK as a ;'later' package was a success, but alas it just churns and churns...  Rollback all the way to 5.5.1 works... :(

From 5.5.1 to 5.6.x I get a Telerik.Web.UI error that is fatal and even the app_offline.htm doesn't remain effective keeping a user at bay; renaming it default.htm works, though.  

I think this tells me I have to find and install a Telerik update on my own at 5.5.1, or once I get to 5.6 (?).  To get to that point I need to discover why I'm getting the HTML 5.1.3 and 5.1.4 errors stopping the upgrade from 5.5.1 to 5.6.  Can I get install packages for each Community HTML update individually?

For now I'm back at 5.5.1 and happy as a clam [except GoDaddy says I need a critical update...]

I plan to poke around and try self-help as well, but most of the times my problems are old-hat to most of you guys.

Thanks in advance.

The site at 5.5.1 was running HTML Community 5.4.3.  I suspect that was why the errors trying to do the 5.1.3 and 5.1.4 upgrades.

Kinda cluesless on the CoreSitemapProvider error although 5.6.0.0 looks funky.

Saw posts that have me steering away from Telerik RadEditor (dnnWerks DNN 5 RadEditor looks attractive; thanks Sebastian!) but pointless unless I can get stable at 5.6.x somehow.

I have Telerik Components for DNN 5.5.0 running, the Telerik Editor Provider 5.4.2 and the Telerik.Web.UI dll dated 11/14/2010.  Will DNN 5 RadEditor work/load with that?  I also have DNN Fck HTML Editor 2.0.4 loaded but it doesn't seem to be used...

I can get a stable running 5.6.2 with a new database.  I can always get the latest version running...  What I cannot do is fold my database in and have it run.  Is there some way to decouple the database upgrade or 'test' the database for upgrade-ability or is the "smoke test" the best I can hope for?

I am willing to try the upgrade manually, but as a remote GoDaddy user.  I have access to everything I need, just not the skills.  Though DNN makes your work look like I'm a guru, we all know better on these forums...  Am I not always going to have to convert the database, though??  Seems that would be smoother in baby steps, though...

Is 5.6.2 really a "Critical Upgrade" ?   Why?  What happens if I wait; better or worse off?

Bob Hanson

I found the same issues upgrading to any version on GoDaddy.  I used the manual approach ...back up the database (just in case) then I used FireFtp, an add-on for Firefox, which always works flawlessly.

FireFtp is a great add-on and I use it regularly.

---

Regards
Hans