Category: People Picker

SharePoint People Picker – The user does not exist or is not unique – Trailing Space

This one is likely to be somewhat rare, but when it happens, the logging doesn’t give you many clues outside of the original “user does not exist or is not unique” error, which is pretty generic. I have two other posts about the same error with different root causes: https://joshroark.com/sharepoint-people-picker-error-user-does-not-exist-or-is-not-unique-similar-account-names/ https://joshroark.com/sharepoint-quick-edit-with-people-picker-field-the-user-does-not-exist-or-is-not-unique/   Symptoms: When using

SharePoint – Users from trusted forest are not found with People Picker

Update 8/13/20 – Added info about RPC Endpoint Mapper Client Authentication, which can break people picker in forest trust scenarios. Consider the following scenario: You have your SharePoint servers in the “Contoso.com” domain. You have the peoplepickersettings.searchactivedirectorydomains (SearchADForests) People Picker property configured properly to search trusted forest “fabrikam.net”. You search for a user that exists

SharePoint – Slow People Picker – Troubleshooting Performance

Poor people picker performance is usually caused by one of two things: 1. People Picker (hereafter abbreviated as PP) is connecting to a Domain Controller across a slow network link. 2. People Picker is trying to query domains that are not available on the network (usually due to firewall settings). Note: If PP performance is

Keeping SharePoint happy during your domain migration

We’ve seen a few of different problems occur in SharePoint (2013, 2016, 2019) when users are being migrated from one domain to another. They usually come up in one of the following areas: People Picker People Picker may show either or both accounts depending on which domain SharePoint is in, and how PP is configured

SharePoint – People Picker: PeoplePickerSearchInMultipleForests

Today I’m writing about a little-known SharePoint People Picker property that can influence your People Picker results. First some background: In SharePoint 2010, People Picker searched all two-way trusted Active Directory (AD) forests by default. In SharePoint 2013 and above, only the local forest is queried, but similar to Exchange, we also leverage the mxExchMasterAccountSid

SharePoint: People Picker error: “user does not exist or is not unique” – similar account names

Consider the following scenario: SharePoint 2013 or 2016 servers are in the contoso.com domain contoso.com has a trust relationship with the corp.fabrikam.com domain. The peoplepicker-searchadforests property is configured like this: “forest:contoso.com;forest:corp.fabrikam.com,corp\SPadmin,*****“ You use People Picker to find a user. If the users account name (samAccountName) is unique, you have no issues adding it to SharePoint.