none
MIM ECMA2 Export fails with Event 6401 when dropping an Audit File RRS feed

  • Question

  • Back in the ECMA1 world since ILM2007 we have always had (and possibly still have) this old error.  I was expecting it to have gone by now, but alas with ECMA2 we now get this:

    BAIL: MMS(9980): export.cpp(2810): 0x8023030d (There is no primary object class on this image.)
    BAIL: MMS(9980): export.cpp(2046): 0x8023030d (There is no primary object class on this image.)
    BAIL: MMS(9980): export.cpp(521): 0x8023030d (There is no primary object class on this image.)
    BAIL: MMS(9980): ..\cntrler.cpp(9848): 0x80230808 (The management agent run was terminated as there were unspecified management agent errors.)
    BAIL: MMS(9980): ..\cntrler.cpp(8569): 0x80230808 (The management agent run was terminated as there were unspecified management agent errors.)
    Forefront Identity Manager 4.3.2195.0

    When removing the setting to drop an audit file the export runs OK.

    While I am not on the latest MIM SP1 hotfix (4.4.1459.0), item #6 for the sync service lists this problem with the generic LDAP MA.

    Is anyone else able to confirm this issue with their own ECMA2, and if so how do I add this to the bug list for the PG please?


    Bob Bradley (FIMBob @ TheMIMTeam.com) ... always using MIM Event Broker for just-in-time delivery of MIM 2016 policy via the sync engine, and continuous compliance for MIM/FIM.


    • Edited by UNIFYBobMVP Monday, June 19, 2017 3:25 AM Further clarification
    Monday, June 19, 2017 3:16 AM

Answers

  • Update we tested with the latest HF,  with 2 ECMA2 connectors and export with Audit works so the change we did in the latest update will address all ECMA2. 

    Kind regards, David David Steadman - MIM Engineering Lead

    Monday, June 19, 2017 3:05 PM
    Moderator

All replies

  • Bob We are checking if this was a global change or just specific to GLDAP 


    Kind regards, David David Steadman - MIM Engineering Lead

    Monday, June 19, 2017 12:54 PM
    Moderator
  • Update we tested with the latest HF,  with 2 ECMA2 connectors and export with Audit works so the change we did in the latest update will address all ECMA2. 

    Kind regards, David David Steadman - MIM Engineering Lead

    Monday, June 19, 2017 3:05 PM
    Moderator
  • Thanks David - the MIM SP1 hotfix doco was definitely specific to GLDAP, so I'm glad it was addressed globally.  Is there any doco link that backs up your discovery?

    Bob Bradley (FIMBob @ TheMIMTeam.com) ... always using MIM Event Broker for just-in-time delivery of MIM 2016 policy via the sync engine, and continuous compliance for MIM/FIM.

    Tuesday, June 20, 2017 12:47 AM