Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Error when running sync profile on each MA

Answered Error when running sync profile on each MA

  • Thursday, January 17, 2013 5:10 PM
     
     
    Sign In to Vote
    0
    Hi,

    I'm preparing a FIM server machine which has the sync service and the portal already installed. I've created some MA and added some sync rules from the portal to provision to AD users coming from HR . All was working fine till yesterday.

    I've made some changes to the sync rules. Also I've added some advanced flow rules using MA rule extensions, and now I'm unable to synchronize. Each MA I try to sync it tells me there were flow errors: "sync-rule-invalid-xml-attribute-flow"

    Using the "Search Connector Space" and looking for "Import Errors" on the "FIM MA", I'm getting a LOT of "sync-rule-invalid-xml-attribute-flow" on all objects type: Person, ExpectedRuleEntry. The same if I look for "Import Errors" on the "AD MA". There are a LOT of "sync-rule-invalid-xml-attribute-flow" on "user" object type.

    Any idea? Anybody can help me?
     

All Replies

  • Thursday, January 17, 2013 11:28 PM
     
     Answered
    Sign In to Vote
    0

    Per http://msdn.microsoft.com/en-us/library/jj593526(v=office.12).aspx

    sync-rule-invalid-xml-attribute-flow: The synchronization rule defines an invalid or incomplete attribute flow.

    Did you modify inbound or outbound sync rules? 

    What build are you on? (This is a problem that has happened but back on ILM 2 RC0)

    It sounds like your sync rule is corrupted. 

    Search the metaverse for your sync rules. Look at the ones that were just updated. Grab the most recently changed text of the persistentFlow attribute and paste it into a response here on the forum. It will look something like this:

    <import-flow><src><attr>Status</attr></src><dest>status</dest><scoping></scoping></import-flow>,FIM MA,7/30/2012 7:43:23 AM

    If this is an outbound MA it could also be a problem on initialFlow.

    To fix the problem you need to open the sync rule in the FIM Site and try and modify the flow that seems to be amiss.

    David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

     
  • Friday, January 18, 2013 3:49 AM
     
     
    Sign In to Vote
    0

    Did you delete a metaverse attribute after you have used it in your sync rule on the portal?

    Also make sure you don't use the same attributes in the sync rule and attribute flow in the MA Config at the same time. That can be done i suppose but it is not recommended at all.

     
  • Friday, January 18, 2013 11:11 AM
     
     Answered
    Sign In to Vote
    0
    Problem solved.

    @Furqan: I double checked mv attributes and sync rules. No deleted mv attributes were present on sync rules. There are some sync rule which have some attribute flows that are also mapped into the MA configuration. This is useless but it seems to work fine. Some of these configurations have been not made by me. I will try to delete theme once all is working.

    @David: As you suggested I checked the persistenceFlow and initialFlow values of my sync rules in the mv. Values were not corrupted. To solve the problem I had to delete from the portal, the latest sync rule I created. Also I manually deleted the sync rule from the FIM cs. This because I was unable to synchronize the deletion from the FIM portal due to 5k stop limit imposed by the fim sync service. I don't know what exactly messed up the sync rule. The causes that may have contributed are two. Names of source fields with a blank inside (for eg. "User Portal"), or the fact that I had to refresh the source schema of the MA (to add some additional source fileds) after the sync rule were already created. Notice that the source of the MA is a "Delimeted Text File".