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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 5 RC2 - Upgrade ProblemsDNN 5 RC2 - Upgrade Problems
Previous
 
Next
New Post
11/12/2008 8:24 AM
 

I've just tried to upgrade to DNN 5 on a copied version of the current DNN 4.9 installation and received the following error:

 

Server Error in '/' Application.

Method 'GetRoleGroupByName' in type 'DotNetNuke.Security.Membership.DNNRoleProvider' from assembly 'DotNetNuke.Provider.DNNProvider, Version=2.0.0.23759, Culture=neutral, PublicKeyToken=null' does not have an implementation.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.TypeLoadException: Method 'GetRoleGroupByName' in type 'DotNetNuke.Security.Membership.DNNRoleProvider' from assembly 'DotNetNuke.Provider.DNNProvider, Version=2.0.0.23759, Culture=neutral, PublicKeyToken=null' does not have an implementation.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[TypeLoadException: Method 'GetRoleGroupByName' in type 'DotNetNuke.Security.Membership.DNNRoleProvider' from assembly 'DotNetNuke.Provider.DNNProvider, Version=2.0.0.23759, Culture=neutral, PublicKeyToken=null' does not have an implementation.]
   System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) +0
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +78
   System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +58
   System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +64
   System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +51
   DotNetNuke.ComponentModel.ProviderInstaller.InstallProvider(IContainer container, Provider provider) +44
   DotNetNuke.ComponentModel.ProviderInstaller.InstallComponents(IContainer container) +89
   DotNetNuke.ComponentModel.ComponentFactory.InstallComponents(IComponentInstaller[] installers) +99
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +786


Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433

 

Any clues on that?  And is it something that can be easily avoided when the time comes for the Production upgrade?

 

Thanks

 
New Post
11/12/2008 8:29 AM
 

After setting Debug to True... the full details that appeared were:

Server Error in '/' Application.

Method 'GetRoleGroupByName' in type 'DotNetNuke.Security.Membership.DNNRoleProvider' from assembly 'DotNetNuke.Provider.DNNProvider, Version=2.0.0.23759, Culture=neutral, PublicKeyToken=null' does not have an implementation.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.TypeLoadException: Method 'GetRoleGroupByName' in type 'DotNetNuke.Security.Membership.DNNRoleProvider' from assembly 'DotNetNuke.Provider.DNNProvider, Version=2.0.0.23759, Culture=neutral, PublicKeyToken=null' does not have an implementation.

Source Error:

Line 79:             ComponentFactory.InstallComponents(New ProviderInstaller("friendlyUrl", GetType(Services.Url.FriendlyUrl.FriendlyUrlProvider)))
Line 80:             ComponentFactory.InstallComponents(New ProviderInstaller("members", GetType(DotNetNuke.Security.Membership.MembershipProvider)))
Line 81:             ComponentFactory.InstallComponents(New ProviderInstaller("roles", GetType(DotNetNuke.Security.Roles.RoleProvider))) Line 82:             ComponentFactory.InstallComponents(New ProviderInstaller("profiles", GetType(DotNetNuke.Security.Profile.ProfileProvider)))
Line 83: 

Source File: C:\Inetpub\DotNetNuke Dev1\App_Code\Global.asax.vb    Line: 81

Stack Trace:

[TypeLoadException: Method 'GetRoleGroupByName' in type 'DotNetNuke.Security.Membership.DNNRoleProvider' from assembly 'DotNetNuke.Provider.DNNProvider, Version=2.0.0.23759, Culture=neutral, PublicKeyToken=null' does not have an implementation.]
   System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName) +0
   System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +78
   System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +58
   System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +64
   System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +51
   DotNetNuke.ComponentModel.ProviderInstaller.InstallProvider(IContainer container, Provider provider) +44
   DotNetNuke.ComponentModel.ProviderInstaller.InstallComponents(IContainer container) +89
   DotNetNuke.ComponentModel.ComponentFactory.InstallComponents(IComponentInstaller[] installers) +99
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) in C:\Inetpub\DotNetNuke Dev1\App_Code\Global.asax.vb:81

 
New Post
11/12/2008 8:41 AM
 

David, I assume that updates of DNN4.x to 5.x was less tested than  simple fresh installations. It is a MUST that upgrades run smoothly for the final version.
My version number for DotNetNuke.Provider.DNNProvider is different than yours, it should be 5.0.0.17057. Can you plase check that your assemblies are updated?

 
New Post
11/12/2008 8:59 AM
 

Hi Stefan

Please forgive as a non-developer/tech... but where and how do I check that the assemblies are updated?

Cheers

David

 
New Post
11/12/2008 10:06 AM
 

The simplest check is that the date of the assemblies is from the day of installation. You can query the version number if you right click on that file, and examine the properties.

However, I noticed that the assembloes of the providers are getting copied during installation, so the old assemblies is still there at that time.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 5 RC2 - Upgrade ProblemsDNN 5 RC2 - Upgrade Problems


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