Some time ago, I worked on a case, where the membership displayed on the MySite ran out of sync.
ISSUE
On My Site page ( …/MyMemberships.aspx…) we usually see the memberships to sites the user is a member of (see figure below):
For some reason, we still have memberships for sites on which the user is not a member anymore.
For some other sites the memberships are correct.
In the customers environment (Build 14.0000.5136.5002) the issue seems to start occurring only on sites from content databases that were detached and reattached. This symptom, were reproducible by the following repro steps:
Repro (detached/Reattached DB)
Pre-Requ’s:
- a running instance of User profile import and sync
- already created MySite host location and active MySites
- existing memberships on any sites in farm
Now check on the MySite as shown above, that the memebership appears (can take a while to be updated).
You can force it by running the timer job “UPA User Profile to SharePoint Full Synchronization” as shown below
You can also check the membership by SQL query:
1: select MemberGroup.Id,MemberGroup.DisplayName,MemberGroup.AllWebsSynchID from MemberGroup
2: inner join UserMemberships on UserMemberships.MemberGroupId = MemberGroup.Id where UserMemberships.RecordId =
3: (select RecordId from UserProfile where NTName = 'domainusername');
So far, everything is fine yet.
Now detach the test content DB and execute the timer job again.
If we now kick off the stsadm command stsadm -o sync -listolddatabases 0 – we’ll see that our Content DB is not in sync anymore.
Now we’re using the previous SQL query again to check for changes: User and membership is still there!
Ok, reattach now the content DB, remove the user from the sites membership group and ensure that the user is entirely removed from the site (not having any other membership, coming from another added AD-Security group, domain users or so).
Run again the “User Profile to SharePoint Full Synchronization” timer job and the SQL Query,
– User still is there! Hmmm… here we would expect, that the user’s membership has been removed and should not appear anymore in the MySite view ….!?
Well, after several attempts and tests I also could find out, that the issue also happens, if a site was deleted without prior removing the user’s membership and or the site was moved to another content DB, etc.
Workaround/Resolution:
However, it took a long time to finally get this particular issue fixed and this supposed to be fixed with the August or October 2011 CU – please ask MS support if you have a similar issue with the membership although applying the CU’s to investigate why it did not fix in your environment/circumstance!
Note! The membership problem is not that trivial as prior assumed and can have more than one cause or dependency. So even if your problem seems to be similar or even match the described one, it might have additional causes and thus may be investigated deeper by Support agents if it still persists with latest CU (currently Oct. 11) installed.
We’re actually aware of several other cases but not all of them are fully reproducible or based on same causes! By now, we only can make more pressure for getting this fixed soon, if we have lots of service requests reporting this issue! So don’t hesitate to call MS support 
*** Update 2011-12-15 ***
The fix for the membership issue is definitely pushed out in the August 11 CU although not mentioned in the according KB article!
But the fix only applies for those changes on membership that happened after applying the fix!
It does not fixing reverse a membership that was broken before installing the fix.
Note!
Against any previous made statements or other blogs posting it:
you must not run the stsadm command (stsadm –o sync deleteolddatabases 0)
If you did, and you also have applied the August 11 CU but still having your issue, please call MS Support and open a case for assistance and further investigation!!
*** End Update 2011-12-15 ***
*** Update 2012-01-23 ***
“User Profile to SharePoint Full Synchronization job stops computing Membership” KB 2703630, Updated December 19, 2012
– provides a Workaround that maybe can help to Repair a broken membership.
“Microsoft acknowledges this to be a product issue regarding cleanup of removed site collections which was fixed in August 2010 cumulative update for SharePoint 2010 (Server package KB 2352342 (http://support.microsoft.com/default.aspx?scid=kb;EN-US;2352342) ).
However this fix does not affect site collections which got into this state by detaching their databases prior to the hotfix installation. To restore membership synchronization for these affected site collections, please follow the resolution steps.” -> KB 2703630
*** End Update 2012-01-23 ***
Note!
This is provided “AS-IS” and does not guarantee the success or Full Resolution. It worked in this particular case and might considered as a “Hint” but not as a resolution for ALL cases!
Hth, cheers, Steve
SharePoint mysteries and more... 
our farm is in sp1 + April 2012 cu, still we are facing this issue.
LikeLike
our farm is in sp1 + Feb 2012 cu, still we are facing this issue.
LikeLike
Still no fix, applied Oct 2011 CU. Hoping MSFT will get this fixed soon!
LikeLike
This site membership issue has been plaguing our environments for several months now. I've just installed the lastest Oct 2011 CU and still no fix.
If this site memberships web part is not considered to have enough business impact to fix then why have it there in the first place!!
I've add yet another complaint to MS premier support.
LikeLike
I'm a sad Panda, as just upgraded to SP1 and CU Aug 2011, and still have this darn error.
Users apparently sync'ed with a sitecollection on a webapplication that now even here anymore.
And links still point to that location..
Best regards
Michael Thøgersen
LikeLike
Hi Michael (sad panda),
I'm sorry if the august 11 CU does not fix your problem. Are you verfied all above noted "Repro steps" as exactly the same?
If your repro does not match teh above decription, the fix most probably is not the one you'd need!
We have lots of support cases, all complaining about broken membership relations or out of sync issues but none has ever raised a hotfix request due to lack of a "business Impact" which is required for it.
Nevertheless, it is highly recommended to call MS Support at least to make them aware of each reproted case as we then can determine a solid business impact by just having lots of cases with all same or similar issues!
So go ahead and open a service request as this is the only way to make enough pressure for getting this fixed!
Besides that, consider that the "membership" can be broken due to variuos reasons or causes whereas each case needs to be investigated individually!
I know, this does not sounds very sufficient but, hey! – as long as no one "starts the queue of complaints" this is rather not going to be a recognized "pain"!
greetz, Steve
LikeLike
@Dev and @senthil (assuming it is the same person):
hey guys, this blog post is just a little part of providing some more understanding and a bit of self-help to the folks out there.
As outlined several times before, this is just "one" possible issue, detailed and described here and may have lot of other causes that might not be fixed with my suggestions.
The update patch is only one recommendation and if it does not fix, this is honestly subject for a support case rather than "discussing" its cause here.
I can only repeat my ask for you to go ahead and open a service request with Microsoft instead of complaining here as this is the only way to make this issue trackable and well recognized by product group. That said, we need those cases to get enough pressure for getting this fully fixed!
Besides that, consider that the "membership" can be broken due to variuos reasons or causes and dependencies, not only the described one above.
Each case needs to be investigated individually if the post did not help yet! This can only be covered in a Support incident and will not be handled via this post.
Your complaints here will not provide better or more awareness to the product team since only support cases are tracked and reports of it being recognized well.
If we ask the PG for a fix, they will ask for how many cases are tracked and if there are just a couple, it seems quiet clear that the effort to develop a fix with all dependencies for testing and ensuring still keeping the product stable, might be limited, right?
But of course you can refer to this post and its comments in your support case once raised, because then its also tracked in our SR-databases and may help somehow to get more recognition on this "symptom".
Hope that gives you more understanding from our perspective and may help somewhat further.
LikeLike