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...DNN 6 Upgrade -- An error has occurred. DNN 6 Upgrade -- An error has occurred.
Previous
 
Next
New Post
7/21/2011 9:25 AM
 
When upgrading to DNN 6 from DNN 5.6.2 I received the following error when going to the home page.

An error has occurred. An error has occurred

This is in the URL.  http://localhost/Default.aspx?tabid=6...

The eventviewer table doesn't help much.

Do I need to restore from backup and try again?  Could this be an issue with a skin?
 
New Post
7/21/2011 9:31 AM
 
Just saw the new log4net stuff. Cool!

Here is the error.

DotNetNuke.Services.Exceptions.ErrorPage - Could not load file or assembly 'CookComputing.XmlRpc, Version=2.4.0.0, Culture=neutral, PublicKeyToken=a7d6e17aa302004d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
DotNetNuke.Services.Exceptions.PageLoadException: Could not load file or assembly 'CookComputing.XmlRpc, Version=2.4.0.0, Culture=neutral, PublicKeyToken=a7d6e17aa302004d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) ---> System.IO.FileLoadException: Could not load file or assembly 'CookComputing.XmlRpc, Version=2.4.0.0, Culture=neutral, PublicKeyToken=a7d6e17aa302004d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throw , Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, Boolean loadTypeFromPartialName, ObjectHandleOnStack type)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throw , Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName)
at System.RuntimeType.GetType(String typeName, Boolean throw , Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.Type.GetType(String typeName)
at Telerik.Web.UI.WebResource.Exists(HttpContext context, String path, String applicationPath)
at Telerik.Web.UI.RadStyleSheetManager.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

The CookComputing dll is present, so I am not sure what is going on.
 
New Post
7/21/2011 9:38 AM
 
DNN was using an old version CookComputing, so I found the 2.4 version here. https://npanday.svn.codeplex.com/svn/...  I renamed it to match the original dll.

Now it is complaining:

Could not load file or assembly 'CookComputing.XmlRpc' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

 
New Post
7/21/2011 9:48 AM
 
I deleted CookComputing dll and everything is working fine now.  I am not sure which module relies on it but I believe it must be 3rd party.
 
New Post
7/21/2011 9:56 AM
 
That assembly is used by the DNN Blog and a number of third-party extensions so it is quite possible that there is a version conflict.

Please check the file/product version of this dll in the site's \bin folder. I suspect that it is an earlier version than 2.4.0.0. The version that is contained in the DNN Blog v 4.01.01 package included with the DNN 6.0.0 upgrade is version 2.4.0.0.

You may have to manually extract this assembly from the DNN Blog package and place it in the site's \bin folder. However, if another third-party module requires a specific earlier version that third-party module may then break. In that case a binding redirect element added to web.config may be able to resolve the issue.

EDIT: It looks like you found the solution while I was writing my post - I think that YAF forums, some Ventrian modules, and possibly some ActiveSocial extensions also use this assembly.

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
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...DNN 6 Upgrade -- An error has occurred. DNN 6 Upgrade -- An error has occurred.


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