MIM 2016 and SharePoint 2016 syncing RRS feed

  • Question

  • Hello,

    I am running into an issue where I am unable to fully sync all information to SharePoint and could use some guidance. For some reason I cannot get the Manager to push into SharePoint. Other information will however push and update.

    I have 3 tasks running in the Task Scheduler. A FullSync (Once daily), DeltaSync (30 minutes), and a PhotoProfileUpdate. When I review their history in SSM they show success 98% of the time. Occasionally I will get a completed warnings on the SPMA DeltaImport. The details specify "exported-change-not-reimported" and reference the manager field.

    I know the field is pulling for AD because when I search the Metaverse I can see managers for users and am able to click them to confirm the linking is correct. Not sure what I am missing as users will add/delete and change information as it is updated in AD. Only thing not pushing is the Manager info.


    Friday, October 28, 2016 3:29 PM

All replies

  • Is manager a reference attribute in FIM? How are you obtained manager?

    Paste the whole error here, please. stack trace

    Nosh Mernacaj, Identity Management Specialist

    Friday, October 28, 2016 4:50 PM
  • Yes, the manager field is a reference type in FIM. I am pulling it from Active Directory.

    Event ID: 6105 FIMSynchronizationService

    The management agent "SPMA" step execution completed on run profile "DELTAIMPORT" but

    some objects had exported changes that were not confirmed on import. Additional Information Discovery Errors : "0" Synchronization Errors : "0" Metaverse Retry Errors : "0" Export Errors : "0" Warnings : "1" User Action View the management agent run history for details.

    The error in SSM will list as follows:

    Synchronization Errors: [DOMAIN]_{Username}_guid

    Error: exported-change-not-reimported

    Opening the connector space object properties the old value is eith blank or null and the new value shows the manager reference string.

    Friday, October 28, 2016 6:54 PM
  • This means that the manager it is being overridden and deleted.  So, you need to check the order of precedence and make sure AD has 1 and SharePoint has 2. 

    exported-change-not-reimported = It was exported but we cant confirm it is still there. 

    Nosh Mernacaj, Identity Management Specialist

    Friday, October 28, 2016 7:45 PM
  • Only the ADMA agent is listed in the flow precedence for the manager field under the person object type.

    • Edited by bambuhiphop Friday, October 28, 2016 9:35 PM
    Friday, October 28, 2016 9:35 PM
  • Something is deleting Manager in SP.  It is being exported fine but deleted right away.

    FIM is doing its work.

    Nosh Mernacaj, Identity Management Specialist

    Friday, October 28, 2016 11:21 PM
  • bambuhiphop, same issue here using SharePoint 2016 and Microsoft Identity Manager 2016.  The manager property is coming in for some employees but not all.  The ones that aren't populating manager are showing 'exported-change-not-reimported', and the only change for each is going from a blank manager to a populated manger.  I can see in the metaverse that the manager for all users is correctly populated.  I've tried deleting all profiles and doing a full sync but I end up with the same thing.  Also cannot get user profile photos to be pulled in from AD.  They are making it into MIM's metaverse, but never making it to the User Profile (although no errors are being thrown on that).  Please post follow-up if you find a solution.
    Wednesday, November 2, 2016 12:45 PM
  • I am experiencing the same issue.  Has anyone made any progress on this issue?
    Monday, November 28, 2016 10:53 PM
  • Having the same issue. Manager is not being populated in SP.
    Tuesday, December 13, 2016 10:59 AM
  • Hi everyone,

    We're experiencing the exact same thing for one of our customers who wanted the external sync service instead of the AD import.

    Wednesday, December 14, 2016 10:46 AM
  • Any update on this? We are experiencing the same issue.



    Friday, January 27, 2017 9:27 AM
  • Same problem here - MIM 2016 SP2016 SP1
    Monday, February 27, 2017 12:32 AM
  • This has been fixed in Feb'17 CU for SharePoint 2016.


    Follow the instructions as per the below article.



    Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

    • Proposed as answer by Dominik Nolte Friday, September 7, 2018 10:11 AM
    Monday, June 26, 2017 2:59 PM