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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...5.1.2 error (new thread)5.1.2 error (new thread)
Previous
 
Next
New Post
9/21/2009 7:40 AM
 

I, too, received this error (Installing Package File HTML_Community_05.01.03_Install:  Error!) when upgrading to 5.1.2 yet all my HTML modules seem to be behaving as they should.  What is the recommendation?  Revert back to 5.1.1 or just wait until a fix is available?  Thanks, Joan

 

 
New Post
9/21/2009 4:47 PM
 

I reverted to 5.1.1

For some reason the error is unassigned in Gemini, so I'm not sure if it will be fixed with the next DNN release.

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=10717&PROJID=2

 
New Post
9/21/2009 5:36 PM
 

This was actually the only error I encountered amoing dozens of upgrades. If you're comfortable with sql, it fails because of some existing entries in the ModuleSettings table. I don't have time at the moment to post any sql for fixing the issue, but if anyone needs it I could probbaly post something tomorrow.

What I really liked was that because of the way things are now structured in v5, a module upgrade like this didn't bomb the whole upgrade process. All sites could be upgraded, and then circled back to fix the 1 or 2 that had this particular problem.


Eric Swanzey
www.swanzey.com
 
New Post
9/21/2009 6:39 PM
 

The problem with this issue is that the error message displayed dureing upgrade (that there was an error in Installing the HTML module) does not correspond to the Exception in the Viewer.

The issue with the HTML module is documented here - http://support.dotnetnuke.com/issue/ViewIssue.aspx?p=0&id=10706 - and is due to the 5.1.3.Sqldataprovider in the HTML module not checking before renaming a SettingName.

The Exception is caused in UpgradeApplication() and will be thrown by any upgrade from version 5.x to 5.y - it is happening because the UpgradeApplication code is trying to "create" th default Authentication system but is not checking for existence before doing so - http://support.dotnetnuke.com/issue/ViewIssue.aspx?p=0&id=10717

Unfortunately the initial post assumed that the exception logged was related to the HTML module error.


Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here
MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...5.1.2 error (new thread)5.1.2 error (new thread)


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