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...TEXT/HTML Module Error upon upgrade to 5.6.0TEXT/HTML Module Error upon upgrade to 5.6.0
Previous
 
Next
New Post
2/22/2011 5:40 PM
 
I upgraded to 5.6.1 and received several error messages in the log, so I rolled it back to previous 5.6.0 version. Site is back, but html modules I have are showing this error message:

Error: Text/HTML is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\sons\8f21c621\8187b572\App_Web_htmlmodule.ascx.e83a8a49.boqwhdod.0.vb(54): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.6.0.459 and an indirect reference (through 'DotNetNuke.Modules.Html.HtmlModule') to version 5.6.1.238. Change the direct reference to use version 5.6.1.238 (or higher) of DotNetNuke. ---> System.Web.HttpCompileException: C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\sons\8f21c621\8187b572\App_Web_htmlmodule.ascx.e83a8a49.boqwhdod.0.vb(54): error BC32206: The project currently contains references to more than one version of DotNetNuke, a direct reference to version 5.6.0.459 and an indirect reference (through 'DotNetNuke.Modules.Html.HtmlModule') to version 5.6.1.238. Change the direct reference to use version 5.6.1.238 (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.GetVPathBuildResultWithAssert(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 ---

Any suggestions greatly appreciated.
Thanks
Leoona H
 
New Post
2/22/2011 8:33 PM
 
How did you perform the roll back ?

1. Delete all site folders and files that are children of the root install folder.
2. Restore all site folders and files from the backup.
3. Reapply permissions for ASP.Net worker process account to root install folder and all child folders.
4. Restore the MS SQL database from the database backup.
5. Restart the site in IIS Management Console.

It appears that the HTML module's assembly (DotNetNuke.Modules.Html.dll) located in the /bin folder and perhaps other related files in the DesktopModules/Html folder did not get properly restored from the backup.

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
2/23/2011 7:53 PM
 
I call it a "rollback" maybe I am using wrong terminology... I use godaddy for hosting and they have a two click option to upgrade to the newest version of DNN. After the upgrade is finished, if it appears that it was not successful, you have 14 days to go back to the previous version, which is what I did. I have no idea how to execute the 5 steps you mention, not sure if I would even have access to all of that with godaddy. I host 3 sites with them and am having problems with all upgrades I have recently done to the sites, but I have posted those problems in other threads.

Thanks for the response, Will.

LeonaH
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...TEXT/HTML Module Error upon upgrade to 5.6.0TEXT/HTML Module Error upon upgrade to 5.6.0


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