No exact match was found People Picker error message

No exact match was found People Picker error message

Issue: Assume that you configure a forest trust between two Active Directory forests and that the Windows Internet Name Service (WINS) is not enabled for Net Bios resolution. In this situation, People Picker in a Microsoft SharePoint Server 2010 site works fine for users in the local forest. However, for users in any domain in the trusted forest, People Picker does not work.

Additionally, People Picker finds the user account and seems to resolve it. However, when user clicks OK to post back to the site, the user receives the following error message:

No exact match was found. Click the items that did not resolve for more options

Cause: This issue occurs because, when you click OK, People Picker makes a NetBIOS call to try to resolve the domain name. Because the customer does not have WINS set up, a Net Bios broadcast occurs. However, the broadcast cannot find the trusted domains because broadcasts are not enabled outside the subnet

Solution: Please check the below link from MS

 http://support.microsoft.com/kb/2874332

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Configure People Picker in SharePoint 2013

Configure People Picker in SharePoint 2013

Check the below link from MS that clearly explain different scenarios of configuration of people picker.

http://technet.microsoft.com/en-us/library/gg602075%28v=office.15%29.aspx#section5 

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

The user does not exist or is not unique in SharePoint 2013

The user does not exist or is not unique in SharePoint 2013

 

Issue: The user does not exist or is not unique in share point 2013,when we check the user in people picker.

Solution: This issue could be of many reasons, In this article I am providing all the relevant solutions to resolve the issue.

Solution 1: ensure that there is no space, The most common issue that occurs with the above is inadvertently adding a space character between the elements of the path.

For example:
instead of OU=Users,DC=CONTOSO,DC=COM you type OU=Users, DC=CONTOSO,DC=COM

Solution 2: Ensure that the user account is not in Disabled state in AD.

Solution 3: Ensure that the user account is not Locked out state in AD

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

People Picker takes too long to resolve names

People Picker takes too long to resolve names 

 

This is a most common issue that we see in People search that picker takes more time to resolve the names. Microsoft has provided a fix for this. There is not impact and no downtime.

Issue: People Picker takes too long to resolve names

Cause: The problem is that we will always go to Active Directory first by default to do the lookup via the Translate To ids  function.  This isn’t desirable in this specific case because it’s a SharePoint security group that’s being passed.  The second part of the problem is with the format of the name specified on the people picker field.  The fact that there is no \ in the name causes Active Directory to submit the lookup against every domain in the forest.  In a large Forest, this can become a taxing operation.  Finally, the lookup is resolved within SharePoint.

Solution: Please run the following to resolve the issue.

1.    [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")

2.    $webapp=[Microsoft.SharePoint.Administration.SPWebApplication]::Lookup("WEB App URL")

3.    $webapp.PeoplePickerSettings.ActiveDirectoryRestrictIsolatedNameLevel=$true;

4.    $webapp.Update();

 

Related KB’s:

http://support.microsoft.com/kb/976396

http://support.microsoft.com/kb/975002/

 This property is set on the Web Application level and is false by default. In order to work around the problem, set this property to true.  

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!