Problem with exceptions in an (old-style) extensible management agent RRS feed

  • Question

  • Hi all,

    I'm working on an "old-style" call-based extensible management agent, which implements the IMAExtensibleFileImport and IMAExtensibleCallExport interfaces.

    If I raise an ExtensibleExtensionException exception from the ExportEntry method, the run terminates with code "success", and displays no error.

    If I check the event log, I see an event log entry saying "The extensible extension returned an unsupported error."

    Both these behaviors are not coherent with what is stated here: IMAExtensibleCallExport::ExportEntry Method.

    I'm using FIM R2, version 4.1.3510.0.

    Are old-style XMAs still fully supported in FIM R2?

    Should I throw another exception type instead?


    Paolo Tedesco -

    Tuesday, July 29, 2014 1:27 PM

All replies

  • Can you mix IMAExtensibleFileImport and IMAExtensibleCallExport? I tried to do that recently with ECMA 2 and was told off by the MA when I tried to build it.
    Wednesday, July 30, 2014 8:10 AM
  • I don't know about ECMA2, but with ECMA1 I don't think it was possible to do otherwise if you wanted to created a call-based MA.

    Paolo Tedesco -

    Wednesday, July 30, 2014 8:13 AM