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 ...Error when editing content of the Html module after fresh install v7.4.2Error when editing content of the Html module after fresh install v7.4.2
Previous
 
Next
New Post
10/11/2015 2:21 PM
 

Hi all,

I have following problem: When editing the content of the Html module after a fresh install 7.4.2 in my dev environment (Win 8.1, , SqlServer 2008 R2 express) the exception shown at the end raises. When installing 7.4.2 in the test environment (Win 2K8 64bit, SqlServer 2008 R2 express) editing the module is without an error and all works fine.

Installing was done using an empty database, modifying web.config to point to this database and calling http://dnndev.me/install/install.aspx. The web site has its own application pool and the application pool user has been granted the necessary rights to the installation folder(s). BTW: This procedure has been used successful (with modifications) beginning with DNN v4.

A google search did not show to much results. What I tried was to clear the "v4.0.30319\Temporary ASP.NET Files" folder - no success.

Does anyone has an idea what the reason for this error can be?

Thanks for your ideas,
Robert

 

--- exception - start

Error: is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: The base class includes the field 'plCurrentWorkVersion', but its type (System.Web.UI.WebControls.Label) is not compatible with the type of control (ASP.controls_labelcontrol_ascx). ---> System.Web.HttpParseException: The base class includes the field 'plCurrentWorkVersion', but its type (System.Web.UI.WebControls.Label) is not compatible with the type of control (ASP.controls_labelcontrol_ascx). ---> System.Web.HttpParseException: The base class includes the field 'plCurrentWorkVersion', but its type (System.Web.UI.WebControls.Label) is not compatible with the type of control (ASP.controls_labelcontrol_ascx). at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildFieldDeclaration(ControlBuilder builder) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.BaseTemplateCodeDomTreeGenerator.BuildSourceDataTreeFromBuilder(ControlBuilder builder, Boolean fInTemplate, Boolean topLevelControlInTemplate, PropertyEntry pse) at System.Web.Compilation.TemplateControlCodeDomTreeGenerator.BuildMiscClassMembers() at System.Web.Compilation.BaseCodeDomTreeGenerator.BuildSourceDataTree() at System.Web.Compilation.BaseCodeDomTreeGenerator.GetCodeDomTree(CodeDomProvider codeDomProvider, StringResourceBuilder stringResourceBuilder, VirtualPath virtualPath) at System.Web.Compilation.BaseTemplateBuildProvider.GenerateCode(AssemblyBuilder assemblyBuilder) at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) --- End of inner exception stack trace --- at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---
--- exception - end

 

 
New Post
10/12/2015 6:59 AM
 
most likely there are different settings for the IIS website or IIS machine.config.
sometimes it helps, if you clear .net temporary files.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/12/2015 9:15 AM
 

In my understanding the web.config of a web application inherits settings from the machine config which is unique per CLR. The application web.config defines settings at its own level - but I am really not the expert with that configurations.

The .net temp file cache I deleted before as described in the initial message.

There are existing older website versions on my dev machine - and with the above given logic the version 7.4.2 has to run as all the older ones.

This said I repeated the installation of a 7.3.4, 7.4.1 and 7.4.2 with its own hostnames - with success!

Then I got the idea, that an existing website (dnndev.me) which had been running with different versions - please note, that the application pool was a new one - could be the problem. I deleted that website (dnndev.me), deleted the application pool an created new ones and repeated the installation procedure - success!

Conclusion: Performing a New Install should include creating a New application.

p.s. If somebody has the detailed explanation (like: the application configuration had been stored in the folderAAA\fileBBB and will be reused until you recreate the application - or something other) - I do really appreciate this.

Best regards
Robert

 
New Post
10/12/2015 10:19 AM
 
your understanding of *.config hierarchies is correct -however its not the case that a new install requires a new application, asp.net should handle the changes fine (I use localhost/dnn_platform for dozens of different builds without issue), However as with everything there will be occasions when it doesn't handle it and it seems this is one of them - typically when this occurs we suggest you change the debug attribute in web.config to "true" , save the changes and browse to the homepage, now change the debug attribute back to "false", save the changes and browse to the homepage. This seems to force asp.net to "flush" any corrupted assemblies in the temporary storage locations and resolves unexpected problems (note: this is still pretty rare, I find I have to suggest this advice only once or twice a year)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
10/12/2015 11:54 AM
 

Cathal,

I took your comment to reread the config documentation in http://www.iis.net/learn/get-started/planning-your-iis-architecture/the-configuration-system-in-iis-7.

Here I mentioned the applicationHost.config - this is in my understanding the only point which can change when deleting and creating an application. 

Whith this in mind I restored an older applicationHost.config and compared this one with the current file.

Here I found the root cause: there was an additional entry <virtualDirectory> which pointed to a full qualified path of an other (older) version. This resulted in a mixed compilation of two different versions.

Thanks to all
Robert

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error when editing content of the Html module after fresh install v7.4.2Error when editing content of the Html module after fresh install v7.4.2


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.