none
MIM Unexpected-error on all MIM Syncs for all Synchronization Rules RRS feed

  • Question

  • Hi guru's, 

    I've been trouble shooting a problem for a while now where I'm getting "completed-sync-errors" on my MIM Delta and Full Sync's. The errors related to all Sync Rules. MIM appears to be working fine on all other fronts. 

    I've done a few searches but can't seem to find anything relating to this other than the following decription:

    "This error occurs when the synchronization engine tries to apply a change to the metaverse (including provisioning and export attribute flow). This error can only occur during runs which apply changes to the metaverse. Check the event log for more information." https://technet.microsoft.com/en-us/library/jj590332(v=ws.10).aspx

    I've had a look at the event log with no joy so far. If anyone an point me in the right direction that would be ace. 

    Sunday, September 10, 2017 11:43 PM

Answers

  • I've run into this once at a Customer.

    Try deleting the Sync Rules in the MV and importing and syncing them again from the MIMMA.


    Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

    • Marked as answer by CRpub86 Monday, September 18, 2017 12:22 AM
    Thursday, September 14, 2017 8:47 AM
  • Hi Chaz,

    1) disconnect them in the MV (the MIMMA connector)

    should do it. You don't need do to anything more.

    Your object deletion rule should already be configured to MIMMA.

    Br,

    Leo


    Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

    • Marked as answer by CRpub86 Monday, September 18, 2017 12:22 AM
    Friday, September 15, 2017 9:54 AM

All replies

  • These issues are not in the event viewere, but in the MIM Synchronization Service. Also, this has nothing to do with MIM working fine or not. These are issues with the data it is processing.

    Can you show us some details of the errors, please.

    In MIM Synchronization Service Client, under Operations, find the failures, and each there should be some details.


    Nosh Mernacaj, Identity Management Specialist

    • Proposed as answer by Leo Erlandsson Tuesday, September 12, 2017 8:07 AM
    Monday, September 11, 2017 2:14 PM
  • Thursday, September 14, 2017 5:02 AM
  • Thursday, September 14, 2017 5:03 AM
  • Thursday, September 14, 2017 5:03 AM
  • Thanks Nosh, 

    Screenshots below for the first error. I haven't been able to provide any meaningful information in the error details. hopefully you can help.

    Thursday, September 14, 2017 5:04 AM
  • I've run into this once at a Customer.

    Try deleting the Sync Rules in the MV and importing and syncing them again from the MIMMA.


    Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

    • Marked as answer by CRpub86 Monday, September 18, 2017 12:22 AM
    Thursday, September 14, 2017 8:47 AM
  • If you click the link to the right, you can see the stack trace, which has the info you need.

    The stack trace button is greyed out, but it will become available if you click the left link, the one with the hexadecimal, not the one that says unexpected-error.


    Nosh Mernacaj, Identity Management Specialist

    Thursday, September 14, 2017 12:45 PM
  • If you click the link to the right, you can see the stack trace, which has the info you need.

    The stack trace button is greyed out, but it will become available if you click the left link, the one with the hexadecimal, not the one that says unexpected-error.


    Nosh Mernacaj, Identity Management Specialist


    Usually these don't have any sort of stack IME. I'd give Leo's solution a try.

    Thanks,
    Brian

    Consulting | Blog | AD Book

    Thursday, September 14, 2017 1:35 PM
    Moderator
  • Yeah the stack trace is greyed out for both error links, I'll give Leo's solution a try and report back. Thanks guys.
    Thursday, September 14, 2017 10:34 PM
  • Leo, 

    Is there a simple way to delete these out of the MV, my only thought on how to do this is to:

    1) disconnect them in the MV

    2) create a CSV with the sync rule GUIDS

    3) create temp MA to join CSV to MV objects

    4) create an object deletion rule on the for the temp MA connector

    5) Clear the CSV file and sync.

    Chaz

    Thursday, September 14, 2017 10:52 PM
  • Hi Chaz,

    1) disconnect them in the MV (the MIMMA connector)

    should do it. You don't need do to anything more.

    Your object deletion rule should already be configured to MIMMA.

    Br,

    Leo


    Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

    • Marked as answer by CRpub86 Monday, September 18, 2017 12:22 AM
    Friday, September 15, 2017 9:54 AM
  • Hi Friends,

    It will happen If we run Full sync several times following errors occures "completed-sync-errors" and unexpected-error. In my case I have resolved this error through following steps.

    • In MIM tool go to the Tools -> click on options -> uncheck Enable Provisioning Rules Extension.
    • Go to Management Agents -> select SPMA -> In Actions pane click on Delete -> select first option and click ok.
    • Select SPMA -> In Actions pane click on Refresh Schema
    • double click on SPMA and click on ok
    • double click on ADMA and click on ok
    • Now run Full sync Start-SharePointSync -Confirm:$false




    • Edited by Rama Goud Sunday, September 17, 2017 6:54 AM
    • Proposed as answer by Rama Goud Sunday, September 17, 2017 6:54 AM
    • Unproposed as answer by Rama Goud Sunday, September 17, 2017 6:54 AM
    Sunday, September 17, 2017 5:33 AM
  • Thanks Leo, 

    I'm fairly positive your solution would have fixed the issue, however, there are no longer any errors. Appears to have righted itself on the 15th... without any influence from me. 

    I did go through the motion of disconnecting a sync rule and that imported successfully.  

    Monday, September 18, 2017 12:37 AM