Hello all,

I am trying to upgrade a portal from 4.0.2 to 4.6.2, and I think I have it figured out, but I came across something during the upgrade process that I was wondering about and I was hopping someone could shed some light on why things are working the way they are.

The issue is I tried going directly from 4.0.2 to 4.6.2.  I made sure both my connection strings where right, and I fixed my machine keys.  However when i upgrade this way I get errors in  4.04.00.log and 4.03.05.log. 

I tried to upgrade from 4.0.2 to 4.5.5.  I changed my machine keys and fixed my connection strings like before.  However this time I got errors in 4.00.04.log, 4.04.00.log and 4.03.05.log

lastley I tried going from 4.02 to 4.3.2, and everything went fine.  So I tried going from 4.3.2 to 4.5.5, and I got an error in 4.04.00.log, and some weird runtime error that had to deal with my menus.  Despite the runtime error I tried going from my new 4.5.5 to 4.6.2, and that went fine.  I also realized that when I clicked on the click here to go to your portal button that the run time error had been fixed in the upgrade, and all my modules users and pages where intact. 

I am not to worried about the error in 4.04.00.log that seems to happen to people a lot and I already found a fix for it

My question is why did I have to upgrade three different times to get the version I wanted without the errors, and has anyone ever came across a runtime error after an upgrade to 4.5.5

Any insight that you could provide on this issue would be appreciated.

Thanks

Mike

Unfortunately, the suggested upgrade paths are not published by DNN.  I saw this question and problem come up so much, I blogged about it.  Here is a link to a suggested upgrade path.

http://blog.strohlsitedesign.com/Blog/tabid/66/EntryID/102/Default.aspx

Now, to answer your question, the upgrade path works when upgrading from and to certain versions because of the database upgrade scripts that are included.  Some versions have an upgrade script that includes the upgrade from previous minor versions, and others don't.  Additionally, I believe that some versions of DNN assume that you have a previous version, and when that version includes an important new feature (such as the new authentication provider), then the wrong upgrade path can get you in a bind.

Will,

Your advice worked perfectly.  However we want to get to 4.05.05 so what I did was follow your table until I got to 4.04.01, and then I tried to go to 4.05.05, and I found a bug after I performed that upgrade

so I started again from 4.00.03, and ran through the upgrade process again.  This time I went from 4.04.01 to 4.05.03.  This worked perfectly

from 4.05.03 I found that I could successfully go to 4.05.05 or 4.06.02 without any problems