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 05.01.02 or 5.1.2 solpart errorDNN 05.01.02 or 5.1.2 solpart error
Previous
 
Next
New Post
9/13/2009 6:15 PM
 

 

Hi Guys,

Please help me out here.

I installed the latest version on my producation server on Friday and managed to get everything working just perfectly so I released it to live, I tested everything and it all looked good but today some errors have appeared which are related to the Solpart control. Has anyone seen this error before?

Sadly I must now work into the night and rollback to 4.9.

 

Error below:

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 'Bind' in type 'DotNetNuke.NavigationControl.SolpartMenuNavigationProvider' from assembly 'DotNetNuke.SolpartMenuNavigationProvider, Version=5.1.0.0, 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 'Bind' in type 'DotNetNuke.NavigationControl.SolpartMenuNavigationProvider' from assembly 'DotNetNuke.SolpartMenuNavigationProvider, Version=5.1.0.0, 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) +62
   System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark) +42
   System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +77
   System.Web.Compilation.BuildManager.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) +105
   DotNetNuke.ComponentModel.ProviderInstaller.InstallProvider(IContainer container, Provider provider) +59
   DotNetNuke.ComponentModel.ProviderInstaller.InstallComponents(IContainer container) +170
   DotNetNuke.ComponentModel.ComponentFactory.InstallComponents(IComponentInstaller[] installers) +121
   DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +1482


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

 
New Post
9/13/2009 9:45 PM
 

Seems some DLL related to solpart menu was not updated. you'd better try copy all the DLL in DNN 5.x upgrade package and re-write the DLLs in the bin folder of your website.

I noticed you still run DNN 5.x under .net framework 2.0, you'd better upgrade to 3.5.

 

 
New Post
9/14/2009 5:08 AM
 

Hi Nicholas,

Thanks for the info. I did a clean code install of dnn 5.1.2 but pointed it to a new database which was created from the backup of my old 4.9 installation. The database upgrade was seemless, I then simply copied all DesktopModules and missing DLL's. I didn't replace or copy the old Solpart dll into the new bin directory.

I have just tried doing an ms update which included the .NET Framework 3.5 with SP1 but it has now taken my server completely down...maybe there was some kind of underlying issue with the server.

Currently restoring yesterdays backup set.

 

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN 05.01.02 or 5.1.2 solpart errorDNN 05.01.02 or 5.1.2 solpart 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