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...Does a module created in version 4.9 install on DNN version 5.01.03?Does a module created in version 4.9 install on DNN version 5.01.03?
Previous
 
Next
New Post
4/19/2010 3:44 PM
 

Chris,

So, then what is the problem? Why can I not install the module? Why do I get this error of version string being too short or long? Please help.

Thanks.

 
New Post
4/19/2010 5:19 PM
 
So, what is wronfg then? Why do I get the version string too long or short error? Please help!
 
New Post
4/19/2010 5:40 PM
 
Abose, have you tried to install this module in another 4.9.x install besides your local development environment. Same question with another DNN 5.x install. Just an FYI, this is not a common issue.

Chris Paterra

Get direct answers to your questions in the Community Exchange.
 
New Post
4/19/2010 6:21 PM
 

I recall that there was an installer issue back in 5.1.x which generated that same error message if there were files with a .sql extension inadvertently included in the .zip package. Finally found the Gemini issue:

http://support.dotnetnuke.com/issue/V...

Although as I read through the issue, I believe this may apply to packaging rather than installing modules. I mention it, however, as a suggestion to also check the version format of all of the xx.xx.xx.SqlDataProvider script files in your package. Make sure that there of three groups of two digits each in the version portion of the filename.


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
4/20/2010 3:12 PM
 
Thanks to all who replied to my questions and all the helpful suggestions. I atlast found out what the problem was, but I still do not know why that would be a problem. It turns out that the line ModuleName.SqlDataProvider in the dnn file was the culprit. I had no use for this file and when I removed this snippet from the .dnn file, the installation went through fine. I do not know the rationale behind this, but this seems to be the problem in my case. If anyone can shed any light on this (may be the ModuleName.SqlDataProvider is an older feature which does not work with the 5.x.x anymore so it needs to be excluded) please let me know. Thanks. Abose
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Does a module created in version 4.9 install on DNN version 5.01.03?Does a module created in version 4.9 install on DNN version 5.01.03?


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