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 !!!!!

The management agent MOSSAD-Connection with AD failed on run profile “DS_FULLIMPORT” because of connectivity issues

The management agent MOSSAD-Connection with AD failed on run profile “DS_FULLIMPORT” because of connectivity issues.

Issue: After configuring the User profile service application, when we start the full synchronization, we see the error” The management agent MOSSAD-Connection with AD failed on run profile”

Cause: As in my view and experiance, This error  is generally caused by the User running the task not having the right permissions set up on Active Directory. 

There could be many reasons, This is the most common.

Event ID:

·        Log Name:      Application

·        Source:        FIMSynchronizationService

·        Event ID:      6050

·        Task Category: Management Agent Run Profile

·        Level:         Error

·        Keywords:      Classic

·        User:          N/A

·        Computer:      SharePoint2013

·        Description:

·        The management agent “MOSSAD-Connection with AD” failed on run profile “DS_FULLIMPORT” because of connectivity issues.

Solution: please follow the below steps if you have the Access to AD. If not, please check the steps with AD team.

1.   Open the Active Directory Users and Computers snap-in.

2.   On the View menu, click Advanced Features.

3.   Right-click the domain object, i.e. for EX: “Sharepoint.com”, and then click Properties.

4.   On the Security tab, click Add. If for some reason the user account you are using to run this service is already on the list you can skip to step 7.

5.   In the Select Users, Computers, or Groups dialog box find the user account under which the profile sync service is running and then click Add.

6.   Click OK to return to the Properties dialog box.

7.   Select the recently added user account // user account under which the profile sync service will run under.

8.   Ensure to Select the “Replicating Directory Changes” check box from the list.

9.   Click Apply and then click OK.

10.     Now start a new full sync from your SharePoint Central Administration to verify the issue has been resolved!

I have Explained in very Detail about User profile in SharePoint 2013.Please check the POST Categories tab for User Profile on Blog.

 

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