Hello there Lee or Joe, Just wondering if you could take a stab at this one. I had a couple modules on my site which have been their for a while now allowing visitors to select where they would want to dine, stay or what they wanted to do depending on the page they went to. These have worked ever since DNN 4.5 but now that I have upgraded to 5.1.2 two of them disappeared while the other stayed. Point is they all are still in the host definitions but if you try to install or uninstall these particular modules you get the following sql error: Version string portion was too short or too long. Here is the trace -------------------------------------------------- DotNetNuke.Services.Exceptions.ModuleLoadException: Version string portion was too short or too long. ---> System.ArgumentException: Version string portion was too short or too long.at System.Version..ctor(String version)at DotNetNuke.Services.Installer.Installers.FileInstaller.ReadManifestItem(XPathNavigator nav, Boolean checkFileExists)at DotNetNuke.Services.Installer.Installers.FileInstaller.ReadManifest(XPathNavigator manifestNav)at DotNetNuke.Services.Installer.Installers.InstallerFactory.GetInstaller(XPathNavigator manifestNav, PackageInfo package)at DotNetNuke.Services.Installer.Installers.PackageInstaller.ReadComponents(XPathNavigator manifestNav)at DotNetNuke.Services.Installer.Installers.PackageInstaller..ctor(PackageInfo package)at DotNetNuke.Services.Installer.Installer..ctor(PackageInfo package, String physicalSitePath)at DotNetNuke.Modules.Admin.Extensions.UnInstall.UnInstallPackage()at DotNetNuke.Modules.Admin.Extensions.UnInstall.cmdUninstall_Click(Object sender, EventArgs e)--- End of inner exception stack trace --- Source: -------------------------------------------------- Again this is the exact message I get if trying to uninstall ------------------------------------------------ Error: is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Version string portion was too short or too long. ---> System.ArgumentException: Version string portion was too short or too long. at System.Version..ctor(String version) at DotNetNuke.Services.Installer.Installers.FileInstaller.ReadManifestItem(XPathNavigator nav, Boolean checkFileExists) at DotNetNuke.Services.Installer.Installers.FileInstaller.ReadManifest(XPathNavigator manifestNav) at DotNetNuke.Services.Installer.Installers.InstallerFactory.GetInstaller(XPathNavigator manifestNav, PackageInfo package) at DotNetNuke.Services.Installer.Installers.PackageInstaller.ReadComponents(XPathNavigator manifestNav) at DotNetNuke.Services.Installer.Installers.PackageInstaller..ctor(PackageInfo package) at DotNetNuke.Services.Installer.Installer..ctor(PackageInfo package, String physicalSitePath) at DotNetNuke.Modules.Admin.Extensions.UnInstall.UnInstallPackage() at DotNetNuke.Modules.Admin.Extensions.UnInstall.cmdUninstall_Click(Object sender, EventArgs e) --- End of inner exception stack trace --- ------------------------------------------------- Don't know why once updating to DN 5.1.2 this happened but these modules were good to go from 4.5 - 4.9.4 versions. Seemed two of them just sort of vanished from the page and when you try to place them again you didn't see them. You could go through the motions of still ading the stay and dine modules but when you click add module it would seem like it was added as no error would pop up but no module would be placed on the page either yet with the do module (which also receives the same string error when trying to install or uninstall in DNN 5.1.2 but not in DNN 4.9.4 or before) it will place fine. The website I am working with is called www.berkshires.org. If you want you can click on the word Do on the horizontal menu just to see the concept of the module that works. The ones that are supposed to show up on the stay and dine pages have a similiar architecture except that their is a list of categories for dining and staying on the given pages but now as I mentioned they just vanished with the latest upgrade. Don't know if you have heard of certain modules remaining installed when doing an upgrade but disappearing off the pages they use to be on and not being able to re add these modules once upgraded. If you have heard of this and have any idea of what could be done concerning such an error any insight woudl be appreciated. Thanks, Bo

I would check with the modules' creators to see if there are versions available for 5.x. That is, assuming that these aren't custom modules.

these are custom modules that is the problem and the ones who designed them didn't do the greatest job either.

If you remember me asking you about the problem I was having with annonymous user space just building and building up I found out this past weekend after I had a chance to do so serious checking that a good portion of that build up was coming directly from one of the custom modules this company developed for us.

What it was doing was creating a new folder in directory called temp with the upload file in it so every time you did an upload to our directory the txt file would be placed in a brand new directory that was labeled some long string. In fact I found I had over 1000 of these folders with these txt files in them. No wonder annonymous user kept building up in size.

For your information (or maybe you guys already new) I learned that anonymous asp.net user build that comes from actual DNN tasks such as emptying the recycling bin by going to admin>recycle bin is stored in Portols>_-default>cache. Don't know if deleting all cache files within this folder would have grave consciquences on the stability of the portal or not as I tested it after a failed upgrade to DNN 5.1.2 and so felt it best to delete all the files on my remote server anyway so at that time guessed at specific folders that just might have waste from the DNN application and that Cache folder was a logical guess so unless you have a poorly constructed module that requires DNN to dump files in new folders every upload than possibly this Cache folder is the way to go to reduce the size from your annonymous aspnet account if indeed you feel the need to do this.

Anyway thanks Joe for the council I do have a module developer actually looking at these modules for reason of expanding them for more functionality so have instructed that they see if they can understand what would cause this type of error in DNN 5.1.2 but not in the DNN 4 platform. When I learn what it was I'll post the solution in case others have come across legacy modules breaking up in this way in DNN 5.

Thanks,

Bo

Have you considered staying at your 4.x version, or just upgrading to 4.9.5 while you work out these issues?

Legacy modules, by the way, are not supposed to break across the 4.x to 5.x boundary.  I assume that means for modules that adhere to the framework and "good" programming standards.  So, it would be helpful to identify what is causing your problems so that things like that can be avoided.

Ya Joe,
I'm going to have to stick with 4.9.5 until such a time that this thing can be ironed out. Also a couple other issues I have run into in the 5.1.2 upgrade howbeit smaller but still no less important. Also I know that 5.1.2 has been having issues in regards to the ability to update the site settings area having making some tweaks to it.

What I think is I should wait for DNN 5.1.3 and in the meantime I'll allow this person who has been looking at these modules try to get to the bottom of what happened when the company first made these modules.


So I have rolled back my upgrade back to 4.9.5 for now and will probably upgrade to DNN 5.1.3 when the dust settles on these module issues.

Take care,

Bo

That seems like the right decision.  I'm working on getting a site of mine from 4.9.3 to 5.1.2 and am encountering some issues/errors in the  upgrade.  Other sites have gone swimmingly.

Another site (has been running 4.6.2 for several years) upgraded smoothly, but require a module upgrade for one third-party module.