I am trying to build an ECMA2 call-based management agent for connecting an appliance holding its own userdatabase. So far so good, I can import the schema, import Persons, export adds, deletions, etc. What I do not understand is how to do error handling within the ECMA2 Extensible Management Agent 2.0. None of the examples posted on the Internet contain error handling. My MA performs WebSvcs calls to the connected system. Based on the results I get back (e.g. success, bad username/password, unable to delete, etc) I would like to return an error code back to FIM, indicating a success or failure for each exported CSEntry. In all examples, the PutExportEntries procedure simply ends with: exportEntriesResults = newPutExportEntriesResults(); returnexportEntriesResults; If I run in debug mode, I see the exportEntriesResults is always null. Can someone please post an example on how to return errors to FIM? Kind regards, Erik Cheizoo eXcellence & Difference http://www.XenD.nl eXcellence & Difference - We keep your business running

Hi! I'm doing it in my ECMA - http://fimfileconnector.codeplex.com/ (check the RemoteFile class that throws it all the way up to FIM) but I must say I found it strange that errors wasn't returned completely correct to FIM even though I followed this: Return values, Errors, and Exceptions As an example I throw BadServerCredentialsException and ServerDownException but FIM returns stopped-extensible-extension-error (ExtensibleExtensionException) anyway instead of stopped-bad-server-credentials and stopped-server-down. //HenrikHenrik Nilsson, Forefront Identity Manager MVP Blog Twitter My employer - Cortego