Re: Suggested DotNetNuke Site Upgrade Path(s)
Will,
- I suggest to use 3.1.1 instead of 3.1.0 and 3.2.2 instead of 3.2.0
- From 3.2.2 I suggest to upgrade to 4.0.3
- From 3.3.x update to 4.3.7! Due to historic facts, 4.0.3 is a previous version of 3.3.x
By Sebastian Leupold on
1/2/2008
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Thanks for the update, Sebastian! I really was hoping you'd stop by and set me straight. ;)
By wills on
1/2/2008
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I suggest to upgrade 4.9.4 directly to 5.1.1 and to avoid 5.0.x totally.
By Stefan Cullmann on
8/11/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Stefan Although that can be done, I have not been able to do that consistently without errors in the upgrade, and event log.
By Will on
8/11/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Could you tell what DNN versions I should use for the upgrade from DNN 4.5.1 to DNN 4.9.4?
By Doru Pirvu on
8/20/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Doru Please use the table above. It shows you every upgrade step you should make.
By Will on
8/20/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Although I don't want to doubt your conclusions here and you probably have more experience upgrading, I'm somewhat taken aback given how DNN was designed to handle upgrades from version X to version Y where X and Y could be anything as long as Y>X. Curious to hear what Charles has to say about this.
By Peter Donker on
9/3/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Thanks for your comment, Peter. From what I have been told in the past by the folks at DNN Corp, they only test from version X to version Y, where version X is always the version that immediately preceded Y. They do not skip versions in testing.
By Will on
9/3/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I found that my 4.09.04 upgrade to 5.00.01 gave me runtime errors.
When I tweeted about it, Brinkman suggested upgrading directly from 4.09.04 to the newest version.
I am going to try it in the morning. If it works I will post back, if not, I have other issues that I need to address.
Thanks for this blog post, it helped me a lot.
By Michael Silva on
10/14/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Michael Silva: So far, I have not run into what you're describing for that version, but every DNN instance is different. I have found that most of the time a DNN upgrade goes bad as a result of a 3rd party module, control, skin, or provider. This is more true of the DNN 5.x series than ever before.
I would certainly suggest that you check out your errors, as they will likely lead you to problems relating to your default skin, or to a 3rd party component. I blogged about some of my upgrade woes when upgrading to DNN 5.x.
By Will on
10/14/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
How do I go about upgrades for older versions when there arent any upgrade packages available for old packages? Only the Install package is available.
By iPro-Andrew on
11/2/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Though it is not a "best practice" it is possible for you to successfully upgrade using an "install" package. Remember to do very good back-ups, and first upgrade on a staging site.
By Will on
11/2/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Just upgraded to 5.2.1 from 4.6.0. The steps above worked fantastic with the exception of the ModuleCachingProvider error in version 5.2.0. However, that was fixed with the release of 5.2.1 - I'm guessing 5.2.0 can be skipped since 5.2.1 fixes the Provider errors along with the web.config error.
Everything went fine with 5.2.1 with the exception of a Log Error. It seems that DNN doesn't like my database user - I have the error logged on the forum.
Thanks for the upgrade path!
By Herb Benton on
12/23/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Herb: You are absolutely correct with your findings! I have updated the listing here. Thanks! :)
By Will on
12/23/2009
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I am having a time trying to upgrade my DotNetNuke to the newest. My DotNetNuke currently says web application 4.09.00 and but my oldest module that is included with DotNetNuke as default is currently at version 3.04.00. So might be a little older. When I upgraded last time I did know how to a great the modules also. I don't remember how to upgrade. I have a host and I would have to do it through DotNetNuke. I do not have direct access to the server.
Would someone please help me with simple instructions I notice something in module definitions but that is about it. Why doesn't DotNetNuke upgrade itself?
By tim carey on
1/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Tim: Unfortunately, there are a great number of things that could be going wrong with your upgrade. Your comment only brushes the surface on the information I'd need to help you out. However, this is not the easiest way to help you out. I'd suggest going to the DNN forums to get more help faster.
By Will on
1/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I don't remember how to do it. When I am doing it through DotNetNuke. The only problem I have is I don't know how to upgrade it.
By tim carey on
1/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
There is documentation on the DNN site that explains how to upgrade DNN (Detailed Installation Guide), but Mitchel Sellers does a very good job of explaining the DNN upgrade process in greater detail.
By Will on
1/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I was at the Mitchel Sellers webpage on the upgrading. he only talks about upgrading to a new version directly on the server. I do not have direct access to a server because I am using a host. Isn't there a way to do it on DotNetNuke?
By tim carey on
2/1/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Tim: All you do is use FTP. Simple! For more detailed assistance, please use the DNN Forums.
By Will on
2/1/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Will, Trying to upgrade from 3.1.3 to 3.2.2 and followed the directions to the T but the upgrade process isn't getting kicked off. I even did the manual way:
localhost/install/install.aspx?mode=Install when I do it this way the screen just stays blank. When I just nav to localhost the site loads normally.
I'm running the site locally, with Win 7 64bit.
By Santiago Perez on
3/5/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
When an upgrade doesn't occur, the first thing that you need to do is make sure that you're performing the upgrade steps correctly - which you've confirmed to have done. The very next step is to look at any non-core modules, providers, and skins and any errors that result from them.
By Will on
3/5/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Perfect, now can someone tell me how to find out what version I'm running ?? I suspect is version 2.xx something.
By Dan on
3/15/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
In general, this query should work for you:
SELECT TOP 1 * FROM [dbo].[Version]
ORDER BY [Major] DESC, [Minor] DESC, [Build] DESC
By Will on
3/15/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Will - We have spent a lot of effort and testing in 5.2.x to improve the upgrade process. You should be able to go from 4.9.x to 5.2.3 directly. There were definitely some errors in earlier 5.0.x and 5.1.x upgrade paths, but those have since been corrected in the later builds. Please let me know if you see any errors in the 4.9 to 5.2.3 upgrade and we will do our best to fix it so that we don't require as many upgrade steps. Unfortunately, the 5.3.0 upgrade issues are out of our control, so the 5.2.3 is always going to be a recommended path unfortunately.
By Joe Brinkman on
3/17/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
That sounds great! I have seen lots of testing issues from Alex related to this. I will have to test it myself and update the blog. Thanks! :)
By Will on
3/17/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
So I got my 4.7.0 site upgraded to 4.9.5 (I am planning on getting it up to the current one after some work on the skin) ... The upgrade install wizard said it completed successfully without any error, however when I look at Host settings, it still says assembly version 4.7.0 ... any idea why or if I can figure out what version I'm really at? When I run the above query to see the db version, it correctly reflects 4.9.5.
By Ryan on
3/31/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
It could be that your cache has persisted for one reason or another since that value is caches on Application_Start. Try recycling the application pool, or otherwise clearing out the cache. Your environment may or may not need a more detailed method of clearing cache.
By Will on
3/31/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Twice now I have encountered a binding redirect error when upgrading directly from 5.3.1 to 5.4.1, and have had to manually upload the Telerik.Web.UI.dll from the 5.4.1 Install package. I have another half dozen sites to upgrade to 5.4.1 in the next week or so, I'll be curious to see if it is a consistent issue or if it is something that only happens to specific sites.
By Ron Miles on
5/17/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Hey Will,
Any news on what Joe had to say about upgrading directly to 5. 2. 3 from 4. 9. x? If so, I'm on 4. 9 .1. Do you forsee any problems with taking that to 4. 9. 5 and then proceeding to follow your upgrade path?
By T. J. Crawford on
5/18/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@T.J. : Although many people have had very successful experiences upgrading directly from version 04.09.05 to the lastest 05.x version, I would suggest doing exactly what you stated. Upgrade to version 04.09.05 first, then follow my upgrade path. That being said, there's no reason to not try to upgrade your site on a test instance directly from 04.09.05 to the latest 05.xx version. You might find it works for you too. :)
By Will on
5/18/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Will do! (no pun intended)
By T. J. Crawford on
5/18/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Following the above upgrade path from 04.09.05 to 05.04.01, there is a problem going between 05.02.03 and 05.04.01 with the Telerik.Web.UI.dll, as the required version 2010.1.309.35 is not included in the upgrade package. You have to extract it from the 05.04.01 install package. This is a confirmation of the issue reported by Ron Miles above.
By Pete on
6/28/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Pete & @Ron: This is something that Ron has shown me that happens quite often. However, while you need to be aware of it, it also does not happen with all upgrades. Thank you for confirming this.
By Will on
6/28/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Will: As a pretty inexperienced DNN user I was following the upgrade path that you have specified above exactly, and I suspect that anyone else doing the same will come across the same issue. I realise that others are trying to jump some steps and are not upgrading incrementally, but I followed the exact upgrade path specified. As version 2010.1.309.35 of Telerik.Web.UI.dll is not included in the 05.04.01 upgrade package, following the upgrade path specified cannot work without extracting the dll from the installation package. This blog is hugely useful by the way, and has saved me an enormous amount of time. Cheers.
By Peter on
6/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Will, thank you for putting this together this is a great service. I was updating a site from 4.5.5 and found that when I got to 4.9.5 that I could not go directly to 5.1.4 without an error. The upgrade script would return "error" at the 5.00.00 point.
Instead I went from 4.9.5 to 5.1.1 and then from 5.1.1 to 5.1.4 and it worked fine.
By Judy Vedder on
8/16/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Thanks for the comments, Judy. I had changed this list to skip straight from 4.x to 05.04.04 a while ago. However, I have a feeling I know what your error was, and it was an uncommon one. Glad you got it worked out though.
By Will on
8/16/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Time to update this post again.
By Bruce de Beer on
8/22/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Bruce: Updated. :)
By Will on
8/22/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
What about upgrade from version 4.08.00 ?
By Branislav Kurbalija on
8/26/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Branislav: Just like the post says... Upgrade to the next version in the list of DNN versions first, then continue with the upgrade path.
By Will on
8/26/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I had a question. do the upgrade files work when upgrading, or are you suggesting using the full versions. I'm apparently getting errors because of my web.config file. I got up to 4.09.04 without errors, but it seems like if I go higher it throws errors like crazy. It seems like this is due to the conversion to the .Net 3.5 framework. Do you have any suggestions for crossing this threshold without so many errors?
By Drew on
9/17/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Typically, upgrades from DNN 04.09.04 to 04.09.05 is not an issue. And you should be able to upgrade from that version to 05.04.04. If you're having errors, I can only tell you to study the error messages, and see if it relates to any of your 3rd party or custom extensions. 8 times of 10, the problem with upgrades is due to a 3rd party extension. The other 2 times is generally configuration issues.
By Will on
9/17/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Thanks, actually most of my errors appear to be stemming from broken references, which I would think would be corrected with the upgrade files? I'll give it another try using your path. Maybe I'm missing something...
By Drew on
9/21/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Hi Will,
First let me start by saying THANKS! for keeping this updated. I have a copy posted on the corkboard above my desk.
Might I suggest you include in your instructions a note regarding ASP.NET 2.0. It is my understanding that DNN 5.1.4 is the last version that supports ASP.NET 2.0 and all versions after that require ASP.NET 3.5.
Although I do know this (I just forgot), I just got bit by that fact when upgrading and moving some sites to another server. Luckily I make backups at each upgrade step so I was able to recover easily.
READERS TAKE NOTE...
I know when doing multiple upgrades (I just did one from 3.2.2 to 4.9.5 using Will's upgrade path) it's a pain to have to backup both the website and database each step of the way but don't shoot yourself in the foot (or a more sensitive place :-). Make the backups! It may save your butt as it did in my case!
By Chuck R. on
9/24/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Chuck: OUTSTANDING suggestion! :) Thanks. And also wonderful advice. I cannot agree more. The time you decide to not backup is exactly the time that you realize how much you can regret it.
By Will on
9/24/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I am at DNN 5.2.3 -
Do you recommend 5.2.3 to 5.4.4 then can you go from 5.4.4 to 5.5.1? Or, do you recommend going to 5.5.0 and then 5.5.1?
Judy
By Judy Vedder on
10/19/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Just tried to go from 5.1 to 5.4.4 and it was a complete disaster. There are a bunch of missing files in the upgrade package in 5.4.4 which are needed.
By Stuart on
10/19/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Judy: Go straight to 05.05.01 from 05.04.04.
@Stuart: I didn't have the same issue, but I know some people have a use case where the Telerik DLL is missing.
By Will on
10/19/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
It's an awesome post, I'm following the path and upgrading from 04.04.01 to 04.06.02 (I know, its old....)...
But the upgrades seems taking looooong time, it seems stuck on the 1/4 of the process, I don't think it should take longer than 2 hours to upgrade or does it?
By Angie on
11/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Angie: A single upgrade should not take that long. I would suggest restoring to the previous version and run a debug profiler, and an SQL profiler to see where the hold up is.
By Will on
11/30/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@ Will: Thanks, will, I have figured out the problem, it was when uploading the files, some files were missed (very strange), anywhoo, I re-uploaded again, and I had a module load warning, and then I went to do some research on this warning and found out apparently when you upgrading any version prior 4.6.2 you need manual modify the web.config file. done that, still not working, rolled the site back and now the site is working as before but can't login any more due to the module load warning....
hmmm...need a bit help here, i'm stuck on can't roll it back and can't upgrade. Only have access to webadmin, don't actually have sql mgmt studio installed anymore...
By Angie on
12/2/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Angie: You really need to roll back to the last known working version of DNN, and upgrade again. Troubleshooting your system at this point could be quite time-consuming.
By Will on
12/2/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Hi my site is running in DNN 3.37 and would like to upgrade to 5.6 without loss of any data please suggest what needs to be done and any body is there to do upgrade for a minimal charges.
Basheer
By Basheer on
12/6/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Basheer: Upgrades from that far back could be quite time-consuming, so a minimal charge is not something you should be looking for. Just like any other business, you will get what you pay for. If your website is important to you, then budget for it appropriately if you can. There are a bunch of high-quality vendors that perform DNN work listed on the DotNetNuke website. That being said, make sure you follow the path above, and upgrade your modules along the way too. Back-up before each and every upgrade!
By Will on
12/6/2010
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Hi, I upgraded my DNN site from 04.09.05 to 05.04.04 successfully but when i going to access to my portal address, it keeps with a eternal loading status and i can´t login...... I did a direct upgrade.
THANKS for help me.
Elvin
By Elvin on
1/19/2011
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Elvin: Not sure what you mean by the eternal loading status. Depending on what you mean, you might need to investigate any hidden errors in the DNN and Windows event logs, and try to correct it and/or retry the upgrade after restoring the site.
By Will on
1/19/2011
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
I have been asked to upgrade an old DNN 3.1.1 site to the latest version. It is running on a hosted site with an SQL2000 backend. From what I have read I should do this incrementally and will take some time. Do you think this is worth the effort are should they just start over from scratch. There are only a couple hundred users in the DB and less then 1G of content.
By Derrik on
2/25/2011
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Derrik: That is a great question, and it should always be asked. There are many things to consider when planning to upgrade to a newer or the newest version of DotNetNuke. First, there are minimum support requirements (i.e., .Net Framework & SQL Server version) and what it might take to upgrade to support those within your environment. Second, is the number and nature of any custom or 3rd party extensions that you might have in use. Those will need to be identified, and it may be necessary to check with the vendor to see what upgrade path they have or require for those modules (if at all). The gathered information would help greatly in determining how much time and cost would be involved in upgrading versus starting from scratch.
By Will on
2/25/2011
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Another red asterisk (*) to put below your upgrade path matrix should indicate that since 5.2.x, DNN requires SQL Server 2005 (or higher) to properly run SQL upgrade scripts. Recent upgrade attempt from 4.9.5 to 5.4.4 failed due to site's database located on SQL Server 2000 which does not support newer SQL scripting functions/methods.
By Albert CZ on
3/26/2011
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
Looks like can skip 5.6.0 and replace it with 5.6.2 ... direct from 5.5.0 to 5.6.2 is fine, no need to go through 5.6.0.
Has been working for me.
By Michael on
7/4/2011
|
Re: Suggested DotNetNuke Site Upgrade Path(s)
@Michael: Thanks. I haven't updated this in a while. You're right about skipping 05.06.00.
By Will on
7/4/2011
|