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 ...Desktop Module Error after 5.1 UpgradeDesktop Module Error after 5.1 Upgrade
Previous
 
Next
New Post
4/18/2010 1:15 AM
 

In Moduledefinitions.ascx.vb, binddata, there is a mismatch in type.

If Upgrade.Upgrade.UpgradeIndicator(glbAppVersion, Request.IsLocal, Request.IsSecureConnection) = ""

glbAppVersion is string, but the parameter in upgrade.upgrade.upgradeindicator is of type system.version.

Is there a workaround or replacement dll for this? or can anyone suggest the best way to deal with it?

 
New Post
8/4/2010 3:00 PM
 
For anyone still having these issues, the Upgrade and Install downloads from codeplex (as of 5.4.4) have missing modules. When the upgrade runs updating these modules fails silently (no error message) and you are left with skins and module definitions from DotNetNuke 4. Then you get errors because these modules are not forward compatible. I solved this by commenting out the sections of Module Definitions which raise errors, allowing access to a partially working page. Then I add the folders containing the correct modules (if you grab the visual studio starter kit, it has at least some of the missing files) and setup the correct modules manually. To do this, I use a locally running clean version of DotNetNuke 5 as a reference. This is incredibly tedious but it works.
 
New Post
8/5/2010 6:41 PM
 
I found this post by posting my error message into Google. I had the error going from 4.9.5 to 5.4.4. I had 2 modules with friendly name "Child Links" - I deleted one and all seems fine now. thanks, Will
 
New Post
8/6/2010 5:28 AM
 
it is always best practive for 3rd party developers, to preceed module names and friendly names with their company name / brand.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Desktop Module Error after 5.1 UpgradeDesktop Module Error after 5.1 Upgrade


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