Forum DotNetNuke® Pro... Authentication ... NullRefExcept DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo

7/9/2008 8:54 AM

	steve conard
95 posts

NullRefExcept DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo

I have recently updated a portal to 4.8.2. One problem that seemed to occur in 3.3.5 with old auth was an occasional corruption of an account that would rise the below message. Now the problem is more frequent and considering I updated Monday, I suspect it will be more frequent than tolerable. I cannot discern yet if the problem is from our network group policies on IE security settings or some problem with the auth module. I do know that if you delete the users account, the problem goes away temporarily. I also know if you open a browser and attempt to get to the child portal; this error appears on the first attempt. The second attempt in the same browser session opens the site but does not auto-login the user.

Server Error in '/' Application.

Object reference not set to an instance of an object.

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.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


            [NullReferenceException: Object reference not set to an instance of an object.]
   DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo user) +57
   DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUser(UserInfo user) +201
   DotNetNuke.Entities.Users.UserController.UpdateUser(Int32 portalId, UserInfo objUser) +21
   DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.SynchronizeRoles(String LoggedOnUserName, Int32 intUserID) +98
   DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.AuthenticationLogon() +226
   DotNetNuke.Authentication.ActiveDirectory.WindowsSignin.Page_Init(Object sender, EventArgs e) +102
   System.Web.UI.Control.OnInit(EventArgs e) +2117356
   System.Web.UI.Page.OnInit(EventArgs e) +9
   System.Web.UI.Control.InitRecursive(Control namingContainer) +321
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692

7/9/2008 9:23 AM

	Mike Horton
3163 posts
dnn.gmss.org

Re: NullRefExcept DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo

Modified By Mike Horton on 7/9/2008 11:25:57 AM)

I did a quick google on DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership just to see what it returned and got the following two links (http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/89/threadid/86028/scope/posts/Default.aspx and http://www.datasprings.com/Products/ProductForums/tabid/727/forumid/19/tpage/1/view/topic/postid/4174/language/en-US/Default.aspx#4183). Essentially the gist of them is that there's missing information in the profile and that's what it causing the error.

Because this was an update and there were a number of changes done for DNN 4.6 I wonder if perhaps you've got some stale .dll files that also might be causing a problem. When I did my upgrade to 4.6.2 I used a program called WinMerge and compared my DNN Install to the DNN 4.6.2 install package and removed any .dlls that were no longer needed. If you decide to go that route make sure you've got a backup of the site in case you accidently delete a .dll that you need.

7/15/2008 9:09 AM

	steve conard
95 posts

Re: NullRefExcept DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo

I removed the role synchronization on all child portals as I have no settings dependent on AD roles in my child portals. This seemes to have fixed the problem and may confirm the theory that it was something missing in the profile. For those on a similar path, (always backup prior) the setting is in the update modulesettings table set settingValue = 'False' where settingName like '%synch%'

Page 1 of 1

Forum

DotNetNuke® Pro...

Authentication ...

NullRefExcept DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUserMembership(UserInfo