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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Upgrade 5.2.1 to 5.4.0 HTML Module errorUpgrade 5.2.1 to 5.4.0 HTML Module error
Previous
 
Next
New Post
9/29/2010 1:25 AM
 
Hi

I'm in the process of upgrading site to 5.5.1... i've upgraded now from 5.2.1 to 5.4.0 and got this in the HTML/Text modules... any ideas for fixed...

Error: Products and Services is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\309b34b3\8f4bcb0e\App_Web_htmlmodule.ascx.e83a8a49.0fajhbjv.0.vb(54): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.4.0.107 and an indirect reference (through 'DotNetNuke.Modules.Html.HtmlModule') to version 5.5.0.653. Change the direct reference to use version 5.5.0.653 (or higher) of DotNetNuke. ---> System.Web.HttpCompileException: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\309b34b3\8f4bcb0e\App_Web_htmlmodule.ascx.e83a8a49.0fajhbjv.0.vb(54): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.4.0.107 and an indirect reference (through 'DotNetNuke.Modules.Html.HtmlModule') to version 5.5.0.653. Change the direct reference to use version 5.5.0.653 (or higher) of DotNetNuke. at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---
 
New Post
9/29/2010 4:56 AM
 
please make sure that the folder /app_code/html has been cleared. This might have failed during the upgrade due to files being in use.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/29/2010 7:34 AM
 
Hi Sebastian Thx for your response... ...no folder like that under /app_code only /app_code/Iframe /app_code/Reports /app_code/Survey /app_code/XML could it be that the change between editors is causing this...?
 
New Post
9/29/2010 8:50 AM
 
It appears that you had first tried to upgrade to DotNetNuke 5.5.0 or 5.5.1 (which included an upgrade of the Html module) and then when you rolled back to DNN 5.4.0 the rollback was not complete leaving the assembly dll file from the newer Html module version still in place. Since that version references DNN 5.5.0, there is a version conflict with the 5.4.0 DotNetNuke assembly dll.

I would try restoring the site files and database back to version 5.2.1 (hope you have the backups), correct whatever caused the upgrade to 5.5.1 fail, then try upgrading from 5.2.1 to 5.5.1 in one step.

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
9/29/2010 9:01 AM
 
Thx William... yip I did roll back because of an skin incompatibility... my isp is restoring the files and db from last night... I take it that one can upgrade from 5.2.1 to 5.5.1 in one step...without major issues..??? Thx for your kind help...
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Upgrade 5.2.1 to 5.4.0 HTML Module errorUpgrade 5.2.1 to 5.4.0 HTML Module error


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