Joe LaTulippe Posts:20

 |
| 03/28/2010 7:46 PM |
|
Good day,
The following errors were encountered during an upgrade from 4.9.5 to 5.3.1:
40.546 - Executing Application Upgrades: 05.03.00 Error 43.703 - Installing Package File HTML_Community_5.02.00_Install: Error! 44.937 - Installing Package File Messaging_01.00.00_Install: Error! 45.187 - Installing Package File Taxonomy_01.00.00_Install: Error!
Things seem to be still working, however I didn't test everything yet. Can someone comment on these errors and what I should do, if anything?
Also, does the upgrade process upgrade the core modules as well, or do I have to go back, download and install them as well?
Thanks alot!
- Joe |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 03/28/2010 9:31 PM |
|
These are errors that will affect you in the future. It would be best to revert to 4.9.5 and look at the upgrade issues with a copy of your site. You might also want to report these errors to the DotNetNuke team.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joe LaTulippe Posts:20

 |
| 03/28/2010 10:10 PM |
|
Thanks for the insight. I wouldn't want to waist my time further developing the site if I am eventually going to run into problems! I did create a backup and have just reverted back to 4.9.5.
Can you suggest a method of resolving my problems, as I do have very little experience in these matters, unfortunately!
Thanks so much!
- Joe |
|
|
|
|
Joe LaTulippe Posts:20

 |
| 03/29/2010 6:01 AM |
|
Perhaps I could upgrade to a stable "version 5" series that wouldn't be so new! Could you recommend a version I could try that has proven reliable and not had too many issues upgrading to?
Thanks,
- Joe |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 03/29/2010 9:04 AM |
|
I would have recommended an upgrade to 5.3.1. I've used that, but only in a new install, and only for some minor testing. I am using 5.2.3 and 5.2.1 on other sites.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 03/29/2010 9:09 AM |
|
I reported your problem at support.dotnetnuke.com.
In the meantime, can you provide any more details?
What were the steps that you went through to do the upgrade?
The errors indicate that the three modules you mentioned were not installed.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joe LaTulippe Posts:20

 |
| 03/29/2010 9:28 AM |
|
Thanks. I think I'll attempt the 5.2.3 upgrade. The basic steps I followed for the 4.9.5 -> 5.3.1 upgrade are below:
- made a complete backup
- verified the skins I am using (Flex from Dr Nuke) were compatible with 5.3.1 (Dr Nuke provided a minor fix). The other skin I am using on a second portal (from dnnskin.net) was verified ok.
- verified my 3rd party modules were 5.3.1 compliant (all was good there).
- downloaded and unzipped 5.3.1 (upgrade package) to different area on my server.
- created "app_offline.htm" in the root of my DNN site.
- verified autoupgrade=false" in web.config
- copied the unzipped 5.3.1 upgrade package over top of my DNN installation
- browsed to my site with /install/install.aspx?mode=install
- the installation began normally, but with the error messages indicated in my original post.
Have I missed anything that you would have suggested for the upgrade process?
Thanks,
- Joe |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 03/29/2010 9:35 AM |
|
As part of the upgrade process and after copying the unzipped package on top of your existing installation, verify one more time that permissions are set correctly on everything in the website's directory. Bad permissions could cause the module installations to fail if the ASP.NET worker task cannot create new subdirectories and/or files.
If you get errors this time, see if you can find -- in the log files -- exactly what failed.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joe LaTulippe Posts:20

 |
| 03/29/2010 9:45 AM |
|
Thanks. I did forget to mention that I did verify that the "NETWORK SERVICE" account had "Full Control" permissions after copying over the upgrade files.
I will try the 5.2.3 upgrade and report back my results!
Thanks alot Joe for all your assistance...it is invaluable!
- Joe |
|
|
|
|
Joe LaTulippe Posts:20

 |
| 03/30/2010 2:35 PM |
|
The results are in...the 4.9.5 --> 5.2.3 upgrade went flawlessly. I think I'll make a backup of it, and then try an upgrade from 5.2.3 --> 5.3.1.
For now...
- Joe |
|
|
|
|
Joe LaTulippe Posts:20

 |
| 03/30/2010 5:16 PM |
|
Well, the upgrade from 5.2.3 --> 5.3.1 didn't get as far as the previous attempt (4.9.5 --> 5.3.1). Once I copied over the upgrade files, verified security rights and browsed to /install/install.aspx?mode=install I received the following error:
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.En ies.Portals.PortalInfo.get_Pages() +38 DotNetNuke.En ies.Portals.PortalSettings.GetPortalSettings(Int32 tabID, PortalInfo portal) +896 DotNetNuke.En ies.Portals.PortalSettings..ctor(Int32 tabID, PortalAliasInfo objPortalAliasInfo) +100 DotNetNuke.Common.Globals.GetHostPortalSettings() +96 DotNetNuke.Common.Globals.GetPortalSettings() +82 DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) +51 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75
Anyone have any ideas of the source of this latest issue?
Thanks all!
- Joe
|
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 03/30/2010 6:30 PM |
|
Are you using Active Directory authentication?
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joe LaTulippe Posts:20

 |
| 03/30/2010 8:23 PM |
|
I was using a third party AD Authentication module (Easy Active Directory Ultimate 4), but have since discontined using it and uninstalled it prior to upgrading from 4.9.5. There may have been some lingering configurations from this module kicking around, depending on how well the uninstall cleaned up things? |
|
|
|
|
Joseph Craig DNN MVP Posts:11667

 |
| 03/30/2010 8:55 PM |
|
The error message that you quoted refers to ActiveDirectory. Perhaps you really didn't delete it. Go back to your 5.x upgrade -- the one that worked -- and see if you can remove it completely. Then try the upgrade again.
|
|
Joe Craig, Patapsco Research Group Complete DNN Support |
|
|
Joe LaTulippe Posts:20

 |
| 03/30/2010 9:34 PM |
|
Awesome! There was a "DNN_Active Directory" provider that was version 1.0.5 with an green "Upgrade" notification beside it that was indicating a newer version (5.0.2)! I uninstalled the older AD provider, tried the 5.3.1 upgrade and voila! Worked like a charm!
Thanks so much for your time and wisdom Joe! Saved me hours and hours of work and frustration (I actually probably would have never gotten it working without you)!
Thanks again!
- Joe |
|
|
|
|