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...Can't log in after 7.1 upgrade.Can't log in after 7.1 upgrade.
Previous
 
Next
New Post
11/4/2013 12:38 PM
 

Ted solution worked for me, I upgraded from 7.0.5 to 7.1.1 with no errors but could not log in.  I changed the web config to match his suggestion and now everything works great.  Thanks Ted!!

 
New Post
12/28/2013 1:15 PM
 

Ted, you nailed it on the head! Great detective work and  many thanks for posting this to the forums! That issue was becoming quite a road block for us trying to get to the latest version of DNN community.

Now that I have migrated from 7.00.06 to 7.01/00, I feel I can proceed to 7.02.00..

Cheers!

 

 
New Post
1/17/2014 8:51 AM
 
Nicely done! I thought I had broke a site at my new company, but Ted saved the day!
 
New Post
2/11/2014 1:15 PM
 

Doh - I wish I had found Ted Demetro's answer yesterday.  It would have saved me a lot of time.  I did my own research and fixed the problem by comparing the source code of DNN 6 and DNN 7.  I blogged about my research and the resolution here:   http://kevinlawry.wordpress.com/2014/...

In DNN 7, the AspNetMembershipProvider was moved from its own DLL into the main DotNetNuke.dll assembly.  The upgrade wizard fails to update the web.config to the new assembly location, and it does not delete the old unnecessary DLL.  When the application runs UserController.UpdateUser() it is actually calling the DNN 6 membership provider.  The stored procedure changed between versions, hence this error:  "System.ArgumentException: Parameter count does not match Parameter Value count."

The resolution is as simple as changing one line in the web.config.  Just remove ".Provider.AspNetProvider" from the AspNetMembershipProvider reference as follows:

<add name="AspNetMembershipProvider" type="DotNetNuke.Security.Membership.AspNetMembershipProvider, DotNetNuke.Provider.AspNetProvider" providerPath="~\Providers\MembershipProviders\AspNetMembershipProvider\" /> 

 
New Post
2/19/2014 3:54 AM
 

Hi all I have been searching for days to no avail.

I upgraded from 7.0.6 to 7.2.1 and now I'm getting the same error when I log in, No admin bar/ribbon and the "A critical error has occurred. An unexpected error has occurred" and the URL has "www.mywebsite.co.uk/Default.aspx?tabid=56&error=An%20unexpected%20error%20has%20occurred"

I have looked at the web.config and everything is as should be.

Any other ideas on this error?

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Can't log in after 7.1 upgrade.Can't log in after 7.1 upgrade.


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