0

I have just taken over an environment. I am not too familiar with SP and am temporarily managing the farm. Every night there are errors from FIMSynchronizationService. Example one below.

In the UPS I see that 90% of our users are correct with the xyz\accountname as we use this as our login, but all new synced users are AD\accountname. Looking for some guidance here.

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> Microsoft.Office.Server.UserProfiles.UserProfileException: Exception while trying to migrate account 'xyz\test' to 'AD\test'. ---> Microsoft.SharePoint.SPException: The user does not exist or is not unique. ---> System.Runtime.InteropServices.COMException: The user does not exist or is not unique.0x81020054 at Microsoft.SharePoint.Library.SPRequestInternalClass.SelectSitesAndUserInfoForMigration(Object& pvarContentDsns, Object& pvarContentIds, String bstrOldLogin, String bstrNewLogin, String bstrFullUserKey, Boolean bEnforceSidHistory, Guid guidSubscriptionId, String& pbstrNewLogin, Byte[]& ppsaOldSid, Byte[]& ppsaNewSid, Object& pvarSidHistory, Object& pvarSiteIds) at Microsoft.SharePoint.Library.SPRequest.SelectSitesAndUserInfoForMigration(Object& pvarContentDsns, Object& pvarContentIds, String bstrOldLogin, String bstrNewLogin, String bstrFullUserKey, Boolean bEnforceSidHistory, Guid guidSubscriptionId, String& pbstrNewLogin, Byte[]& ppsaOldSid, Byte[]& ppsaNewSid, Object& pvarSidHistory, Object& pvarSiteIds) --- End of inner exception stack trace ---

Improve this question
1
  • Are you performing a domain migration? Is it possible these two accounts have a matching SID or one has a SID with the other matching that value in the sidHistory attribute? Commented Mar 14, 2018 at 23:00

1 Answer 1

Reset to default
0

Looks like the NetBIOS Domain Name differs from the Full Qualified Domain Name. This requires some configuration in UserProfileService:

  • Note all Settings inside your current Sync connection
  • Delete the existing faulty Synchronization Connection in the User Profile Service Application.
  • Open the SharePoint 2013 Management Shell with administrative rights.
  • Run Get-SPServiceApplication and copy the GUID of the User Profile Service Application.

  • Run this script in with the correct GUID.

    $UserProfile = Get-SPServiceApplication -Id GUID
    $UserProfile.NetBIOSDomainNamesEnabled=1
    $UserProfile.Update()

  • Create a new Synchronization Connection with Active Directory Domain Services.

  • Run a full “Start Profile Synchronization”.

Some References:
Enable NetBIOS Name for User Profile Service Application in SharePoint
Rational Guide to implementing SharePoint Server 2010 User Profile Synchronization

Improve this answer
4
  • Will this have any effect on the current mysites or profiles that are correct there at xyz\username? Commented Mar 15, 2018 at 16:52
  • Is "XYZ" NetBIOS Domain Name or FQDN? Commented Mar 16, 2018 at 6:33
  • XYZ is the netbios name Commented Mar 16, 2018 at 15:15
  • This should not affect existing xyz-users as UPS will recognize them again with their NetBIOS-Domain. If you rely on those profiles and their MySites, i suggest you to implement this in a testing-environment first. Also be aware that MySites get deleted 30 days after UPS does no longer recognize the Profile. platinumdogs.me/2012/10/18/… Commented Mar 16, 2018 at 15:49

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.