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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade Woes - Where did it all go wrong?Upgrade Woes - Where did it all go wrong?
Previous
 
Next
New Post
1/9/2011 6:20 AM
 
I first was introduced to DotNetNuke four years ago with version 4.8.x and I must admit I was blown away with what I was able to do with only basic web skills. I've upgraded my site from it's initial release to 4.9.5 and during this process I was also impressed with how simple it was.

Then version 5 came along, and the wheels seem to have come off the DNN upgrade wagon. The web is littered with DNN 5.x upgrade horror stories. I've held off trying to get into DNN 5.x because of the reported issues, and also the lack of information about how to do the upgrade. There used to be upgrade manuals on the DNN site, but now you are hard pressed to find these details. Now your dependent on blogs and forum posts.

And then there is the upgrade process itself. Deciding that we shouldn't put off the upgrade any longer I tried to jump from 4.9.5 to 5.6.0 having read somewhere that 5.6 was a safe version to use. Having solved the full install versus upgrade package issue. I went about upgrading my site last night only for the upgrade to crash and leaving me no option other than to return to my trustee 4.9.5 version.

My problems seem to have been caused by a DLL (Telerik.Web.UI.dll) not being in the bin folder… why wasn't it. It was in the full install package which is were I found a copy after finding the answer on a blog site. That wasn't the end of the problem because the upgrade package does not include a new web.config file, mine was left with many inconsistencies. I eventually got back into my site by using the web.config from the install package (after changing the personal keys).

This got me back into the site but unfortunately the damage was done, I could not get into the modules area or edit any html module. So, regrettably I have had to abandon my attempt and I don't feel confident enough to re-try this any time soon.

DNN must address the issue with upgrades which seems to be very problematic. Take my site, it's as basic as you can get with no foreign third-party modules, it's DNN through-and-through, but still I can't go from 4.9.5 to 5.6.0!

Has anybody else made this jump and what issues (if any) did you encounter.

Steve Le Monnier
 
New Post
1/9/2011 12:22 PM
 

I ran upgrade to 5.6 against 4.9.5 last night. The database upgrades go without a hitch. When the application upgrades start, so do the problems.

I got errors at application upgrades for 5.01, 5.03, 5.04.03, 5.06.00.
 
I got errors cleaning up files at 5.00.00 and 5.06.00.

Then the site won't load, and when I set custom errors to "Off" I see that the error is about not being able to access the bin/system.web.extensions.dll.

The file is there, and the permissions are correct so that there shouldn't be any problem accessing it.

I rolled back and tried again with exactly the same results. So I'm back to 4.9.5.

Guess I'll leave it there for now ...

Not sure why it will help, as Will suggests, to wait until 5.6.1 to upgrade, unless changes are going to be made in the application upgrade steps for earlier versions where the errors occur.

I see a recommendation from PowerDNN to upgrade in steps: 4.9.5, 5.2.0, one other in between, and then 5.6. Not sure I'll try that at this time.

pmgerholdt
 
New Post
1/9/2011 12:35 PM
 
Please take a look at the suggested upgrade path page on the wiki - http://www.dotnetnuke.com/Resources/Wiki/tabid/1409/Page/Suggested_Upgrade_Path/Discuss/1/Default.aspx . It also has information on the changing pre-requisites for new versions.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/9/2011 12:36 PM
 
sorry, wrong link, heres the correct one - http://www.dotnetnuke.com/Resources/Wiki/tabid/1409/Page/Suggested_Upgrade_Path/Default.aspx

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/10/2011 4:48 PM
 
Just from my own experience, you are MUCH better off keeping up with the updates.

I had huge issues when upgrading any 4.x version to a newer 4.x version.  It usually involved lots of trying it, restoring from backup, fixing the config issues, trying again.

Once it hit version 5 the updates have gone much smoother.   Meaning, I haven't had to roll back a site update.

One thing I learned with the version 4 updates was that you had to do a file comparison between your config file and the one provided by DNN and make all the changes.

Personally, I'm glad the config file is missing from the 5.x series.  I haven't had to worry that a bad config file was going to completely hose me.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade Woes - Where did it all go wrong?Upgrade Woes - Where did it all go wrong?


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