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 from 5.3.1 to 5.4.4 having taxonomy and messaging upgrade errorsUpgrade from 5.3.1 to 5.4.4 having taxonomy and messaging upgrade errors
Previous
 
Next
New Post
7/9/2010 5:52 PM
 
I'm trying to upgrade from 5.3.1 to 5.4.4 and I keep getting the same three errors during the upgrade.

00:00:12.812 -   Installing Package File HTML_Community_05.04.03_Install:  Error!
00:00:15.296 -   Installing Package File Messaging_01.01.00_Install:  Error!
00:00:15.640 -   Installing Package File Taxonomy_01.01.00_Install:  Error!

I 'm using SQL Server Express 2005, and asp.net  3.5, meeting the minimal requirements. 2 portals, default language English for both has been chosen, the XML, chat modules are not installed and I did unblock the upgrade zip file before unzipping. I have researched each of these three errors for hours and have not learned anything that helps.

Does anyone have an idea on how to get past these errors?


Here is the full log:

Upgrading DotNetNuke
Current Assembly Version: 05.04.04
Current Database Version: 05.03.01



Upgrade Status Report
00:00:00.375 - Upgrading to Version: 05.04.04
00:00:01.015 -   Executing Script: 05.04.00.SqlDataProvider Success
00:00:04.625 -   Executing Script: 05.04.01.SqlDataProvider Success
00:00:04.687 -   Executing Script: 05.04.02.SqlDataProvider Success
00:00:04.921 -   Executing Script: 05.04.03.SqlDataProvider Success
00:00:05.046 -   Executing Script: 05.04.04.SqlDataProvider Success
00:00:05.078 -   Executing Application Upgrades: 05.04.00 Success
00:00:12.250 -   Executing Application Upgrades: 05.04.01 Success
00:00:12.250 -   Executing Application Upgrades: 05.04.02 Success
00:00:12.250 -   Executing Application Upgrades: 05.04.03 Success
00:00:12.437 -   Executing Application Upgrades: 05.04.04 Success
00:00:12.437 -   Cleaning Up Files: 05.04.00 Success
00:00:12.437 -   Cleaning Up Files: 05.04.01 Success
00:00:12.437 -   Cleaning Up Files: 05.04.02 Success
00:00:12.437 -   Cleaning Up Files: 05.04.03 Success
00:00:12.437 -   Cleaning Up Files: 05.04.04 Success
00:00:12.453 -   Updating Config Files: 05.04.00 Success
00:00:12.453 -   Updating Config Files: 05.04.01 Success
00:00:12.453 -   Updating Config Files: 05.04.02 Success
00:00:12.453 -   Updating Config Files: 05.04.03 Success
00:00:12.453 -   Updating Config Files: 05.04.04 Success
00:00:12.453 - Performing General Upgrades
00:00:12.750 - Installing Optional Modules:
00:00:12.812 -   Installing Package File HTML_Community_05.04.03_Install:  Error!
00:00:15.296 -   Installing Package File Messaging_01.01.00_Install:  Error!
00:00:15.640 -   Installing Package File Taxonomy_01.01.00_Install:  Error!
00:00:16.031 -   Installing Package File Telerik_05.04.00_Install:  Success
00:00:18.093 - Installing Optional Skins:
00:00:18.468 - Installing Optional Containers:
00:00:18.531 - Installing Optional Languages:
00:00:18.531 - Installing Optional Providers:
00:00:18.687 -   Installing Package File AspNetMembershipProvider_05.02.00_Install:  Success
00:00:18.921 -   Installing Package File CorePermissionProvider_05.01.01_Install:  Success
00:00:19.093 -   Installing Package File CoreSitemapProvider_5.2.0.0_Install:  Success
00:00:19.312 -   Installing Package File DatabaseLoggingProvider_05.01.01_Install:  Success
00:00:19.531 -   Installing Package File DNNMembershipProvider_05.01.03_Install:  Success
00:00:19.781 -   Installing Package File DNNMenuNavigationProvider_05.01.00_Install:  Success
00:00:20.078 -   Installing Package File DNNTreeNavigationProvider_05.01.00_Install:  Success
00:00:20.375 -   Installing Package File FckHtmlEditorProvider_02.00.04_Install:  Success
00:00:45.203 -   Installing Package File FileBasedCachingProvider_05.01.03_Install:  Success
00:00:45.469 -   Installing Package File FileModuleCachingProvider_05.04.03_Install:  Success
00:00:45.812 -   Installing Package File MemoryModuleCachingProvider_05.02.01_Install:  Success
00:00:46.047 -   Installing Package File SchedulingProvider_05.02.01_Install:  Success
00:00:46.297 -   Installing Package File SearchIndexProvider_05.01.00_Install:  Success
00:00:46.844 -   Installing Package File SearchProvider_05.01.01_Install:  Success
00:00:47.250 -   Installing Package File SolpartMenuNavigationProvider_05.01.00_Install:  Success
00:00:47.640 -   Installing Package File TelerikEditorProvider_05.04.02_Install:  Success
00:00:48.656 - Installing Optional AuthSystems:
00:00:48.672 -   Installing Package File LiveID_01.00.01_Install:  Success
00:00:50.984 -   Installing Package File OpenID_02.00.00_Install:  Success
00:00:51.953 - Installing Optional Packages:

Upgrade Complete

 
New Post
7/9/2010 10:13 PM
 
I have seen the triad of upgrade/install errors:

Installing Package File HTML_Community_05.04.03_Install:  Error!
Installing Package File Messaging_01.01.00_Install:  Error!
Installing Package File Taxonomy_01.01.00_Install:  Error

a number of times here in the forums but with no resolution. Your's however, is one of the few cases in which an "Executing Application Upgrades" or "Updating Config Files" error did not preceed the Installing Package errors. The lack of other errors helps to eliminate a number of potential causes of the installing package errors. Unfortunately, these errors do not produce a log file entry nor one in the (Event Viewer) EventLog. I have tried several times in the past to replicate the error(s) and just now tried a 5.3.1 install followed by a 5.4.4 upgrade without error.

It appears that you did everything correctly to prepare for the upgrade and are familiar with some of the issues that have caused failed upgrades.

To help us get closer to finding the cause of these errors, please answer the following:

1. Can you confirm that you have ASP.Net 3.5 SP 1 and not just ASP.Net 3.5 installed?
2. What is the install/upgrade history of the site PRIOR to the upgrade to 5.4.4? For example, was DNN 5.3.1 the version first installed? Do you recall noting any errors during prior installs/upgrades?
3. Had you noted any errors or issues with the HTML module, HTML provider, or the new Messaging and Taxonomy features prior to the 5.4.4 upgrade?
4. Is the site completely down following the upgrade?
5. If not completely down, are any HTML modules displaying their contents properly or are all showing errors?
6. Are you able to log into your site as host or admin user and examine the Event Viewer for any errors logged during the 5.4.4 upgrade?
5. If this is a public facing site would it be possible for me to have temporary access to the database and file system and host access to the DNN installation or would you be willing to provide a backup of both the database and filesystem for me to examine? A backup of the database and filesystem prior to the 5.4.4 upgrade would also be helpful.

Regarding #5, you may contact me via email to bill (at) wesnetdesigns (dot) com.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
7/10/2010 9:46 AM
 

Bill,

Thank you for addressing my upgrade problems directly.  I’ve seen you in the forums quite a bit while researching my problem. It is so refreshing to see people like you step in and help. Thanks.

I’ll try to answer your questions:

1. Can you confirm that you have ASP.Net 3.5 SP 1 and not just ASP.Net 3.5 installed?

Confirmed ASP.NET 3.5 SP1

2. What is the install/upgrade history of the site PRIOR to the upgrade to 5.4.4? For example, was DNN 5.3.1 the version first installed? Do you recall noting any errors during prior installs/upgrades?

This site began with DNN 4.8.2 or so I believe. It’s been a while and I have quite a few other sites, so my memory may not be perfect. I do remember that there have been upgrade issues.

This site was moved from 4.8.2 to 5.1.1. There were a number of issues when I tried to go the whole distance at one time. So I started over and did then one at a time and completely resolved the errors each step of the way.

Here are a few of the errors this site has seen and resolved: These are posts in my blog.

Upgrading the Events Module causes it to report "Argument 'Length' must be greater or equal to zero."
http://letitshine.biz/Support/DNNSupp...

There was a lot of trouble upgrading the Events Module independent of a regular DNN  upgrade.

Error when upgrading DNN: Executing Script: 05.01.00.SqlDataProvider Error!
http://letitshine.biz/Support/DNNSupp...

Cannot insert the value NULL into column 'DefaultLanguage', table
http://letitshine.biz/Support/DNNSupp...

It was also hacked by Soyletmez once

There was a problem once that threw errors with the verbiage “Exception has been thrown by the target of an invocation”. This was resolved. I’d have to think hard to remember the cause and solution.

There were probably a few more.

3. Had you noted any errors or issues with the HTML module, HTML provider, or the new Messaging and Taxonomy features prior to the 5.4.4 upgrade?

I think this is the first time to have errors with these components.

4. Is the site completely down following the upgrade?

The site is up.

5. If not completely down, are any HTML modules displaying their contents properly or are all showing errors?

The HTML modules are working fine. I can’t see anything not working on my casual run through. I have not attempted to work with Taxonomy or messaging yet.

6. Are you able to log into your site as host or admin user and examine the Event Viewer for any errors logged during the 5.4.4 upgrade?

I’m logged in as host on first try.  There are errors in the event log. Most of them are related to the Orizonti Nuke News module. I have not attempted to resolve these yet. I am focusing on the upgrade first.

5. If this is a public facing site would it be possible for me to have temporary access to the database and file system and host access to the DNN installation or would you be willing to provide a backup of both the database and filesystem for me to examine? A backup of the database and filesystem prior to the 5.4.4 upgrade would also be helpful.

This is a public site. I’ll correspond with you in email about the rest.

Thanks a whole lot for helping Bill.

Mark


 
New Post
7/16/2010 9:32 PM
 
To bring closure to this thread so that others having similar issues with the upgrade of the HTML, Taxonomy, and Messaging modules when upgrading, the original poster did contact me off-forum and was trusting enough to provide me with backups before/after the upgrade and access to the live site files and database. The findings were as follows:

  • With the exception of one third party module that was frequently logging null reference errors the site appeared to be functioning well. All HTML modules were displaying properly and their content could be edited. Although Taxonomy and Messaging modules were not being used their management UI functions were working and a check of Host-->Extensions showed they had upgraded correctly from their 1.0.0 versions to 1.1.0.
  • No upgrade errors were noted in the Event Viewer log. All SqlDataProvider scripts had run without errors in their log files.
  • Noted that some of the core modules upgraded immediately following the site upgrade to 5.4.4 were displaying their Supported Features checkboxes in Host-->Extensions. A check of the DesktopModules table showed a -1 value in SupportedFeatures column for those upgraded modules.
  • Created localhost clone of pre-5.4.4 upgrade installation and upgraded with same errors being noted in HTML, Taxonomy and Messaging modules. No error details were logged.
  • Rolled localhost clone back to pre-5.4.4 upgrade, added debugger symbols file and in VS set breakpoints in module installer code. Following error was thrown (but not caught or logged) in non-debugger upgrades for EACH module upgrade - HTML, Taxonomy and Messaging :
    • System.Xml.XmlException: Data at the root level is invalid. Line 19, position 1 at System.Xml.XmlTextReaderImpl.Throw(Exception e) at
      . . . . . . System.Xml.XmlDocument.LoadXml(String xml) at DotNetNuke.Services.EventQueue.Config.EventQueueConfiguration.Deserialize(String
      configXml) at DotNetNuke.Services.EventQueue.Config.EventQueConfiguration.GetConfig() at
      DotNetNuke.Services.EventQue.EventQueueController . . .
  • Tried installing a core module and found extensions installer did display the same error as above in its report.
  • Located the xml file Portals\_default\EventQueue\EventQueue.config and did find that its structure was badly corrupted.
  • Rolled back to pre-5.4.4 upgrade and noted same corruption of xml which I guessed had happened during a prior upgrade to 5.3.1 knowing that in 5.3.0 the EventQueue.config file had been modified to add the Application_Start_FirstRequest event.
  • Deleted the EventQueue.config file which would allow it to be automatically regenerated when needed.
  • Reran the upgrade to 5.4.4 without any errors.
  • Was able to install/upgrade site modules without errors.

The poster later found a backup taken immediately after the prior 5.3.1 upgrade which showed that the EventQueue.config file was not corrupted during that upgrade but also that it had not been modified to include the new Application_Start_FirstRequest event. Since the config file would have beenregenerated when needed if the file was missing or the Application_Start_FirstRequest event had not been added previously the corruption could have occured at anytime since the 5.3.1 upgrade.

Without being able to process the EventQueue.config file when adding events in the EventQueue to be run following an application restart, these are some of the potential effects:

  • ModuleInstaller.Commit cannot run to completion.
  • UpdateSupported Features processor command is never added to EventQueue resulting in SupportedFeatures column in DesktopModules table being  set to the default value of -1 with the result that a module implementing Search, Import/Export will loose those features.
  • Modules implementing IUpgradable will never run their UpgradeModule code which can have widely varying impact depending on what changes to folders,  files, database, etc. are supposed to have been made in that code.
  • In some multi-portal installs, a reference to the module's entry in DesktopModules table may not be added to the PortalDesktopModules table resulting in availability of the module in some portals but not others.

I have a support issue in Gemini (DNN-13176) to suggest that a Try..Catch be added to EventQueue.Configuration.GetConfig that should the file throw an XmlException when being read, it would be deleted and allowed to regenerate and the error/recreation possibly logged.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade from 5.3.1 to 5.4.4 having taxonomy and messaging upgrade errorsUpgrade from 5.3.1 to 5.4.4 having taxonomy and messaging upgrade errors


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