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 |
Thanks for the update, Sebastian! I really was hoping you'd stop by and set me straight. ;)
By wills on
1/2/2008 |
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 |
@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 |
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 |
@Doru Please use the table above. It shows you every upgrade step you should make.
By Will on
8/20/2009 |
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 |
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 |
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 |
@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 |
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 |
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 |
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 |
@Herb: You are absolutely correct with your findings! I have updated the listing here. Thanks! :)
By Will on
12/23/2009 |
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 |
@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 |
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 |
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 |
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 |
@Tim: All you do is use FTP. Simple! For more detailed assistance, please use the DNN Forums.
By Will on
2/1/2010 |
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 |
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 |
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 |
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 |
@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 |
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 |
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 |
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 |
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 |
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 |
@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 |
Will do! (no pun intended)
By T. J. Crawford on
5/18/2010 |
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 |
@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 |
@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 |
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 |
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 |
Time to update this post again.
By Bruce de Beer on
8/22/2010 |
@Bruce: Updated. :)
By Will on
8/22/2010 |
What about upgrade from version 4.08.00 ?
By Branislav Kurbalija on
8/26/2010 |
@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 |