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...upgrading from 05.01.01upgrading from 05.01.01
Previous
 
Next
New Post
4/25/2011 6:43 PM
 
Hi all,

I am running IIS6 with .net 3.5SP1 on a 2003R2 server.

I am new to professional edition.  Just got my license and trying to upgrde an old site.

I am trying to upgrade from 04.07.00 to the most recent and have been using the upgrade path.  After figuring out how to rename my log in module, I am now at version 05.01.00 and can't seem to go further.

The next step in the process is 05.02.03 but when I do, I get:

Current Assembly Version: 05.02.03

Current Database Version: 05.01.00



Upgrade Status Report

00:00:00.187 - Upgrading to Version: 05.02.03
00:00:01.328 -   Executing Script: 05.01.01.SqlDataProvider




Server Error in '/' Application.

Method not found: 'Boolean DotNetNuke.Entities.Host.ServerController.get_IsWebFarm()'.

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.MissingMethodException: Method not found: 'Boolean DotNetNuke.Entities.Host.ServerController.get_IsWebFarm()'.





So, I rolled back and decided to just try to go to 05.06.02 directly, but when I do, I get:

Server Error in '/' Application.


Method 'RestoreUser' in type 'DotNetNuke.Security.Membership.AspNetMembershipProvider' from assembly 'DotNetNuke.Provider.AspNetProvider, Version=5.1.0.0, 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 'RestoreUser' in type 'DotNetNuke.Security.Membership.AspNetMembershipProvider' from assembly 'DotNetNuke.Provider.AspNetProvider, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.


Can anyone offer a suggestion?
 
New Post
4/25/2011 8:45 PM
 
The first issue is likely caused by a bad web.config file, at least that would be my guess. You might need to compare your web.config to a newer web.config to see if you're missing anything in particular.

As for the second issue, I haven't seem that myself.

Can I ask what process you are using for upgrading? What steps?

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
4/25/2011 9:12 PM
 
Thank you. I will review the web.config.

As to the upgrade process, I looked around the web on how others were doing it and it looked like Beyond Compare was a tool others used. I am simply synchronizing one directory with another using that tool.
 
New Post
4/25/2011 10:00 PM
 
Regarding the second error (when upgrading directly from 05.01.00 to 05.06.02), it appears that the following assembly located in the site's \bin folder:

DotNetNuke.Providers.AspNetProvider.dll

either did not get extracted from the 05.06.02 upgrade package or did not get copied over the assembly of the same name (v 5.1.0.0) in the \bin folder. Although you could try re-extracting this assembly file from the upgrade package and copying it to the site's \bin folder, it is likely that this error prevented other parts of the upgrade procedure to execute properly making a roll back to 05.01.00 recommended followed by another upgrade attempt.

Before extracting the files from a .zip archive that you have downloaded from the web you should first "unblock" the archive by rightclicking on the .zip filename or icon, selecting "Properties" from the context menu, then clicking "Unblock". Also, I recommend first extracting the .package to a new, empty folder then copying all of it's contents over the existing DotNetNuke installation allowing any new files to replace those of the same name rather than extracting the upgrade package directly to the existing installation folder.

As for the upgrade path you should be able to go to from 5.01.00 to 5.06.02 directly but others have recommended to use an intermediate step to 5.04.04 then 5.06.02.

Also, I just noticed that you mentioned that you have received a Professional Edition license. Don't forget that you can contact DotNetNuke support (see your license and other information you have received for the contact information) for assistance with Professional Edition upgrade issues.

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
 
New Post
4/26/2011 12:43 PM
 
Thank you both! I am upgraded.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...upgrading from 05.01.01upgrading from 05.01.01


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