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 6.02 to 7. "Error has ocurred" twice on Login Module. "Method not found": on logUpgrading 6.02 to 7. "Error has ocurred" twice on Login Module. "Method not found": on log
Previous
 
Next
New Post
6/15/2013 6:44 AM
 
 Hello, I'm lookiing for  little help.

What I'm trying to do
- Upgrade a CE 6.02.00.1610 installation to the latest 7.00.06.

What I have

- Simple 5-6 page site running since before v4.08 that has been upgraded to 6.02.00.1610 over time and has been working well so far.  Win 7 Pro, IIS 7.5, SQL Express 2008 R2
- Last upgraded 4.9 to 6.2- Custom skin I created by modifying one of the built-in skins.  Changed menu button apperance, other cosmetic changes
- One custom module: Page hit counter (originally ICPC-Counter) which I modified to compose and send an email automatically too.
- I had a custom ContactForm Module which I removed from the site and uninstalled from DNN since the upgrade process was trying to add it to the module table and was getting a duplicate primary key error.  So, I decided to upgrade without it and then deal with adding it back later on 7.00.  I restored the 6.02 site, removed the module from the page and uninstalled the module from DNN to retry upgrade

What I did
- Downloaded latest Upgrade zip on 06/13/13
- Ran the Upgrade process to 100% in less than a a minute, no errors on log file, InstallLog only showed informational messages no errors

The problem
- On loading the site I get red box errors "An error has ocurred" besides the Register and Login links on the Login Module
- The first error message logged is
"2013-06-15 00:08:47,874 [hp4520s][Thread:6][FATAL] DotNetNuke.Framework.PageBase - An error has occurred while loading page.
System.MissingMethodException: Method not found: 'System.Collections.Hashtable DotNetNuke.Services.Authentication.AuthenticationConfigBase.get_ModuleSettings()'.
   at DotNetNuke.Authentication.LiveID.Config..ctor(Int32 portalId)
   at DotNetNuke.Authentication.LiveID.Config.GetConfig(Int32 portalId)
   at DotNetNuke.Authentication.LiveID.Login.get_Enabled()
   at DotNetNuke.UI.Skins.Controls.UserAndLogin.<HasSocialAuthenticationEnabled>b__1(AuthenticationInfo a) in c:\inetpub\ITS\admin\Skins\UserAndLogin.ascx.cs:line 295
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source)
   at DotNetNuke.UI.Skins.Controls.UserAndLogin.HasSocialAuthenticationEnabled() in c:\inetpub\ITS\admin\Skins\UserAndLogin.ascx.cs:line 294
   at DotNetNuke.UI.Skins.Controls.UserAndLogin.get_UsePopUp() in c:\inetpub\ITS\admin\Skins\UserAndLogin.ascx.cs:line 107
   at DotNetNuke.UI.Skins.Controls.UserAndLogin.get_RegisterUrl() in c:\inetpub\ITS\admin\Skins\UserAndLogin.ascx.cs:line 119
   at DotNetNuke.UI.Skins.Controls.UserAndLogin.OnLoad(EventArgs e) in c:\inetpub\ITS\admin\Skins\UserAndLogin.ascx.cs:line 144
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)"

My thoughts
- Well, it seems to be a problem with the authentication service, but I don't know what it could be.
- I have never enabled LiveID, Facebook or any other authentication method, but all 7 providers are Enabled according to table Authentication. 
- I thought perhaps there could be a problem with my custom skin, but I have a page using the default  Minimal Extropy skin and it displays the same errors described. So, I tend to discard that reason.

I tried
- Tried to login in order to look around the settings and test some other skins but I can't.  Tried SITE/login.aspx but get to the home page with additional error "An unexpected error has ocurred"

Questions
- Should SITE/login.aspx work in normal circumstances or is that not the URL to use?

- Any ideas of what could be happening or how to troubleshoot this?
- Some people have posted that some Authentication providers may be causing the problem and would try going into Authentication table and deleting records for offending providers.  Is this feasible?  Apparently setting the IsEnabled field is not enough and you need to delete the records?

Thanks.
Iván Torres
 
New Post
6/16/2013 4:49 AM
 
Prior to starting the upgrade, you may uninstall all authentication providers (besides DNN).
Next, please make sure running the application pool on .Net 4, when upgrading.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/18/2013 12:16 AM
 
Sebastian Leupold wrote:
Prior to starting the upgrade, you may uninstall all authentication providers (besides DNN).
Next, please make sure running the application pool on .Net 4, when upgrading.

Thanks for the reply, Sebastian.

Did that and the problem is apparently resolved, as I see so far.  But is there a problem with the upgrade process or was this a problem uniquely related to my installation?

This is the story in case it can help others
Before I got to see your message, I traced the error message on the log back to LiveID and OpenID authentication modules.  I checked the dlls and saw their file dates where from 2008 instead of 04/29/13 like all the other Authentication dlls.  So, that gave me the idea that these dlls were not installed or upgraded from previous 6.02.00.

After the failed upgrade I couldn't login to DNN to check Extension versions or elegantly update LiveID and OpenID.  So, as a test I overwrote the dlls with current ones downloaded from CodePlex. The errors went away and I was able to login and verify extension versions were all 6.02, except these two were registered as 1.00.

I had the option of elegantly re-installing and registering both modules through DNN and leaving it at that, but I couldn't be sure if that would correct all problems created by upgrade routine not processing LiveID and OpenID. So, I followed your suggestion of running the upgrade again after restoring 6.02 and uninstalling the two extensions.  Upgrade went well.  I logged in 7.00  and installed the two missing extensions through DNN.  Perhaps my first solution would have been equivalent, but as a user, one couldn't be sure and was better to run upgrade again.

Anyway, is there any reason why LiveID and OpenID authentication extensions would not be correctly upgraded?

Thanks.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrading 6.02 to 7. "Error has ocurred" twice on Login Module. "Method not found": on logUpgrading 6.02 to 7. "Error has ocurred" twice on Login Module. "Method not found": on log


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