SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When certain users are added to a SharePoint group in a particular site collection, they do not appear in the user list in the browser. If added outside of a SharePoint group (ie: given a permission directly), they appear normally.

They are added, as they can get access, and I can see them listed in the permissions in SharePoint Designer, however within the browser - they are not listed. There are no errors, messages, or warnings at any point. This only happens in one site collection, even though many other site collections use the same User Profile Synchronization Service.

The only similar situation I can find through Google is Cannot add user to SP group, SP 2010. We recently (within the last month) upgraded from 2007 to 2010, however we did not use any third party tool like Avepoint in the aforementioned thread - we used the database detach reattach option.

After some digging, we've found that the affected users are not listed in the "User Information List" (sitecollectionURL/_catalogs/users/simple.aspx), however it is possible to view the user's entry in this list if you force-change the ID URL variable to their tp_id # from the UserInfo table in SQL (ie: http://sitecollection/_layouts/userdisp.aspx?ID=123.

Using PowerShell, we can found some commonalities in the users that are experiencing the problem:

  1. ForwardLinks and BackwardLinks contain empty arrays({}) in working users. Affected users contain nothing.

  2. FirstUniqueAncestorSecurableObject = "User Information List" for working users. Affected users have nothing.

  3. FirstUniqueAncestor = "User Information List" for working users. Affected users have nothing.

I've tried the following to resolve the issue:

  1. Full profile synchronization in central admin. (No Effect)

  2. stsadm -o sync deleteolddatabases 0 followed by a full User Profile sync in Central Admin (No Effect)

  3. Manually updating the missing properties in Powershell to match a working account (didn't work, list is read-only).

EDIT: Tried deleting an affected user from the site collection and then re-adding their permissions. Issue persists.

share|improve this question

I realize that this topic is a year old, but I was having a very similar issue. I had a site that had been migrated from MOSS to SharePoint 2010 and then again to SharePoint 2013. I could add users to the Members SharePoint group through the UI, however none of the users would show. I was able to verify that the users were being added to the group via the Content Database's GroupMembership table. The previous answer led me to try the PowerShell route. I executed the following script, and upon completion, ALL groups for this particular site collection began functioning correctly:

$web = Get-SPWeb <site url>
$group = $web.Groups["<group name>"]

$users = $group.Users

foreach ($groupUser in $users)
share|improve this answer

We had exactly the same problem and were able to fix it by just "reading" and writing all users via SP-Powershell:

foreach ($user in get-spuser -web http://CONTOSO.EXAMPLE.COM –limit all) {$user.Update()}
share|improve this answer
Dang! I wish I had of seen your comment earlier, Stuart. We ended up fixing it using the content deployment method. – Nik Craik Oct 9 '12 at 17:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.