none
ambiguous-import-flow-from-multiple-connectors on initial Full Import RRS feed

  • Question

  • Hi,

    We have a new, clean FIM MV, and are looking to initialize the MV with data from multiple connected systems, before we enable provisioning logic.

    While performing a first Full Import, to import data from AD, we have encountered this error message:

    ambiguous-import-flow-from-multiple-connectors

    Import flow was rejected because the destination metaverse object had multiple connectors from the source management agent.

    Why would we see this error on a first import into an empty MV?

    thank you,

    SK

    Thursday, May 24, 2012 5:05 AM

Answers

  • SK

    That certainly will happen if you have defined your relationship in your inbound SR in terms of a value that is not unique in the partition you are importing.  The first object is imported to the MV OK but a second duplicate (in terms of your relationship, or join rule) finds a match on the first MV object and throws in the towel.

    There is one other obscure scenario where you get this error (a special case to do with incorrectly flowing a multi-value property to a single-value property), but the above should be eliminated first.


    Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

    • Marked as answer by D Wind Thursday, May 24, 2012 10:42 AM
    Thursday, May 24, 2012 7:55 AM

All replies

  • SK

    That certainly will happen if you have defined your relationship in your inbound SR in terms of a value that is not unique in the partition you are importing.  The first object is imported to the MV OK but a second duplicate (in terms of your relationship, or join rule) finds a match on the first MV object and throws in the towel.

    There is one other obscure scenario where you get this error (a special case to do with incorrectly flowing a multi-value property to a single-value property), but the above should be eliminated first.


    Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

    • Marked as answer by D Wind Thursday, May 24, 2012 10:42 AM
    Thursday, May 24, 2012 7:55 AM
  • Thanks Bob,

    Yes you are correct, after carefull examination I found that the accounts in error had a duplicate anchorID.

    Thank you


    • Edited by D Wind Thursday, May 24, 2012 10:42 AM
    Thursday, May 24, 2012 8:55 AM
  • Dear All,

    I found the same problem with you. How to check anchorID on accounts on AD?

    Thank you.

    Thanachart.R

    Thursday, September 12, 2013 9:35 AM
  • Export the AD account (including the anchor attribute) to a csv file with csvde.

    Then do analyzing in Excel or powershell for example, in powershell you can use group-object cmdlet.

    but i would suggest to use a anchor attribute that is unique to AD like samAccountName or UPN for example if possible in your solution, to avoid such error in the future.

    Regards
    Peter


    Peter Stapf - Doeres AG - http://www.doeres.com

    Thursday, September 12, 2013 6:48 PM