none
Problem: "no default anchor construction specified" on staging after Update 2 RRS feed

  • Question

  • Hi

    After update 2 in customer environment problem occurred with extensible ma which uses DSML file as import source. On a staging when import file is generated MA is failing with stop-ma error and following BAIL error message. 

    (...)

    "ERR: MMS(3380): ma.cpp(2322): no default anchor construction specified
    BAIL: MMS(3380): ma.cpp(5204): 0x8000ffff (Catastrophic failure)
    BAIL: MMS(3380): ma.cpp(5705): 0x8000ffff (Catastrophic failure)
    BAIL: MMS(3380): ma.cpp(5503): 0x8000ffff (Catastrophic failure)
    BAIL: MMS(3380): ma.cpp(1014): 0x8000ffff (Catastrophic failure)
    BAIL: MMS(3380): import.cpp(780): 0x80230808 (The management agent run was terminated as there were unspecified management agent errors.)

    (...)

    For anchor definition this MA is configured with "Use distinguished name as anchor attribute" option in MA configuration. All entries in import file has DN attribute set. Any idea what might cause this problem? Anyone has similar problems in a past? 

    Monday, June 18, 2012 8:27 AM

Answers

  • So just to close this thread with through self-service ;) ... apparently it is a problem with existing MAs which were imported during the upgrade from ILM to FIM. Until Update 2 for FIM Synch service this has worked flawlessly so probably Update 2 together with introducing ECMA has changed something in MA interface \format. 

    In both cases these MAs were configured at "Configure attributes" -> "Set anchor" to "Use distinguished name as anchor attribute". What was required in order to fix these MAs was to go to each and every object class defined in "Define object types" section and select same option as above but for each individual object class.

     Un-checking this for any of object classes bring the issue back again. 

    Self-service case closed ;)

    Monday, June 18, 2012 9:32 PM

All replies

  • Actually it looks like it might be a more general problem - I have second case of Extensible MA with same or similar kind of issue. Common pattern is that both of these MAs are using DSML as a file format and are using DN as anchor. In second case it throws a both different message but similar in its meaning:

    (...)

    The server encountered an unexpected error while performing an operation for a management agent.
     
     "BAIL: MMS(5708): ma.cpp(750): 0x8023080e (The management agent could not be started as the management agent was configured improperly.): anchor construction must be configured for this file format
    BAIL: MMS(5708): cntrler.cpp(543): 0x8023080e (The management agent could not be started as the management agent was configured improperly.)
    BAIL: MMS(5708): ma.cpp(3668): 0x8023080e (The management agent could not be started as the management agent was configured improperly.)
    Forefront Identity Manager 4.0.3606.2"

    (...)

    Anyone with DSML file based MA out there to check if it is working properly after Update 2? 

    Monday, June 18, 2012 1:41 PM
  • So just to close this thread with through self-service ;) ... apparently it is a problem with existing MAs which were imported during the upgrade from ILM to FIM. Until Update 2 for FIM Synch service this has worked flawlessly so probably Update 2 together with introducing ECMA has changed something in MA interface \format. 

    In both cases these MAs were configured at "Configure attributes" -> "Set anchor" to "Use distinguished name as anchor attribute". What was required in order to fix these MAs was to go to each and every object class defined in "Define object types" section and select same option as above but for each individual object class.

     Un-checking this for any of object classes bring the issue back again. 

    Self-service case closed ;)

    Monday, June 18, 2012 9:32 PM
  • Hi Tomasz

    I got the same errors using an LDIF Agent but with a slighty later version for FIM:

    The server encountered an unexpected error while performing an operation for a management agent.
     
     "BAIL: MMS(2160): ma.cpp(750): 0x8023080e (The management agent could not be started as the management agent was configured improperly.): anchor construction must be configured for this file format
    BAIL: MMS(2160): cntrler.cpp(543): 0x8023080e (The management agent could not be started as the management agent was configured improperly.)
    BAIL: MMS(2160): ma.cpp(3668): 0x8023080e (The management agent could not be started as the management agent was configured improperly.)
    Forefront Identity Manager 4.0.3617.2"

    and could be solved in the same way as explained by Tomasz
    • Edited by BuEd Friday, July 13, 2012 1:36 PM
    Friday, July 13, 2012 12:48 PM
  • Can You please take 1 minute and provide feedback on this on connect - http://connect.microsoft.com/site433/feedback/details/749735/dsml-based-extensible-ma-fails-with-problems-with-dn-generation - vote is enough ;), but also clicking on "I can too" will be even beter
    Friday, July 13, 2012 2:41 PM
  • Seems that the discussion on the Connect site is closed
    Monday, July 16, 2012 5:40 AM