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...No login after upgrade 7.4.2 > 8.0.3No login after upgrade 7.4.2 > 8.0.3
Previous
 
Next
New Post
8/29/2016 6:21 AM
 

Ok so I've managed to carry out an upgrade from 7.4.2 to 8.0.3 by removing the Google Analytics and Security Analyzer modules from the installation, but now I can't login as there is no login box. Nothing displays on the login page. Other modules on other pages seems to display fine.

I've switched to the Xcillion skin before the upgrade to avoid any skin/container/menu issues.

I can see a couple of exceptions in the database that may have something to do with it - This one:

Type 'DotNetNuke.Web.Client.ClientResourceManagement.DnnJsInclude' does not have a public property named 'Name'.

and this one:

The base class includes the field 'ctlProfile', but its type (DesktopModules.Admin.Security.DNNProfile) is not compatible with the type of control (ASP.desktopmodules_admin_security_profile_ascx).

   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.UI.TemplateControl.LoadControl(VirtualPath virtualPath)
   at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc)
   at DotNetNuke.UI.Modules.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration)
   at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration)
   at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl()

 

Any ideas are appreciated

Rob

 

 
New Post
8/29/2016 8:09 AM
 

Updating this further...

I uninstalled and deleted all traces of the Solpart menu and also the old DNN Survey module, and also an old skin that was not in use but had a container with a solpart menu reference.

With all of the above gone and a fresh upgrade, I still get the same issue... no login box.

I've wiped the events and restarted to ensure I get the error that specifically related to this from the log:

 

The base class includes the field 'ctlProfile', but its type (DesktopModules.Admin.Security.DNNProfile) is not compatible with the type of control (ASP.desktopmodules_admin_security_profile_ascx).   
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.UI.TemplateControl.LoadControl(VirtualPath virtualPath)
   at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc)
   at DotNetNuke.UI.Modules.WebFormsModuleControlFactory.CreateModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration)
   at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration)
   at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() 

The base class includes the field 'ctlProfile', but its type (DesktopModules.Admin.Security.DNNProfile) is not compatible with the type of control (ASP.desktopmodules_admin_security_profile_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) System.Web

 

Any ideas still appreciated

Regards
Rob

 

 

 
New Post
8/29/2016 8:58 AM
 
there seem to be an issue including proper libraries - it seems to refer to asp.net libraries prior to DNN libraries.
Did you make sure, your installation is meeting DNN 8 requirements (App Pool running .Net 4.5.1 or above in integrated pipeline mode)?

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/29/2016 10:36 PM
 
Hi Sebastian

I installed .Net 4.5.2 via the IIS Web Platform Installer prior to the upgrade tests. I do note however that it is hard to determine what version the application pool is running because there is this silly inconsistency between the advertised .Net numbers and the actual version displayed in the application pool settings.

The clarify: The IIS manager application pool listing only shows v2.0 or v4.0 in the .Net CLR Version column. When one opens the 'Advanced Settings' for a given pool. it only offers the same two version numbers as options. When one accesses the 'Basic Settings' for a given pool, one can see a more detailed number for v4.0: v4.0.30319
I don't believe this number changed after installing the .Net 4.5.2 package.

Do you have any idea how exactly one is meant to identify and select .Net4.5.1 or above in any of this?
Regards
Rob

 
New Post
8/29/2016 11:22 PM
 

ok, using the information in this Microsoft KB article:

https://msdn.microsoft.com/en-us/libr...

to find the dword values to look up on this page:

https://msdn.microsoft.com/en-us/libr...

I can determine that I am actually running .Net 4.6.1 (dword 394271 on Server 2012)

So that should be sufficient to run the upgrade?

I note there are some commands for applying the specific version through the command prompt. I'll have a look at those.

Regards
Rob

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...No login after upgrade 7.4.2 > 8.0.3No login after upgrade 7.4.2 > 8.0.3


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