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 ...4.6.24.6.2
Previous
 
Next
New Post
10/4/2007 9:50 AM
 

the only thing that stands out right now is that the version number of the AspNetMembershipProvider that it is trying to create the instance of, in the 4.6.2 version, is:

DotNetNuke.Security.Membership.AspNetMembershipProvider, DotNetNuke.Provider.AspNetProvider, Version=3.2.2.13431, Culture=neutral, PublicKeyToken=null

But the version number, in the 4.4.1 install, in the bin direcorty (Right click -> Properties -> Version) is 3.2.2.26645

Did they roll back a version?  or was the wrong version included in the upgrade package?

Thanks!

 
New Post
10/4/2007 10:08 AM
 

-line 312 of PortalInfo.vb
-Tries to create the Membership instance in the UserController Line 60
then the membership instance tries to create the DataProvider in the "AspNetMembershipProvider.vb" Line 59 in which the:

dataProvider

As dataProvider = dataProvider.Instance() throws the exception since it is null

 
New Post
10/4/2007 10:59 AM
 

Ok, I am officially out of ideas...It just refuses to make an instance of the user membership data provider.

 
New Post
10/4/2007 11:26 AM
 
If you are:

1) Absolutely certain that your web.config is configured properly for membership (I don't see any problems with it), and
2) That the assembly that you are referencing, DotNetNuke.Provider.AspNetProvider, exists in your bin directory, AND
3) You've established that there are no versioning problems,

Then the next step I would suggest would be to load the project for DotNetNuke.Provider.AspNetProvider into your solution, add a reference to it within the main DNN project, and see if you are able to directly instantiate the class DotNetNuke.Security.Membership.AspNetMembershipProvider. I've run into this type of issue before, and on several occasions there was a hidden problem with the instantiation of the class that was not included in the stack trace.

Brandon

Brandon Haynes
BrandonHaynes.org
 
New Post
10/4/2007 11:54 AM
 

I have no ideas either and am not aware, that there was a roleback of the membership component.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...4.6.24.6.2


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