Failing exports report success.

Tony Sheehy 7 years ago in UNIFYBroker/Microsoft Identity Manager • updated by anonymous 3 years ago 11

Failing exports aren't being picked up as failures in FIM.
To easily reproduce, try exporting to a disabled adapter.

Affected Versions:
Fixed by Version:

Matthew, Tony mentioned that you knew something about this. Why is this happening? I thought we followed the information on http://msdn.microsoft.com/en-us/library/ms696504.aspx?


From when I had observed it, I have seen strange cases of export errors not being logged. The above one of exporting to a disabled adapter is not one I have seen succeed. I'll need to confirm this in a few different environments potentially.

A difference between imports and exports is that exports only directly handle and rethrow exceptions wrapped in fault exceptions. The export should also have generic exception handling.

Matthew, can this be fixed please? Seems like it could get the solution into a bad state.


Looks like another Update 2 issue:

Neither EntryExportException nor ExtensibleExtensionException were resulting in the anticipated behaviour seen here: http://msdn.microsoft.com/en-us/library/windows/desktop/ms696504.aspx with regards to FIM success results.

To note, FatalEntryExportException did.

When the same Adapter was tested on a local machine running FIM v4.0.2592.0, it worked as expected.

Reassigned for confirmation of completion.

At the very least, this should be posted to http://social.technet.microsoft.com/Forums/en-US/ilm2/threads, if not a more formal channel (if existing, the FIM Connect site does not take bug reports). The FIM Product Group do frequent the forums and do mention to people when things will be fixed in future hotfixes.

Perhaps we should also confirm it is in an issue in 4.0.3617.2.

This is due to the "Enable merging of "Pending Export" and "Export In Progress"" setting introduced in Update 2 and later (also FIM R2). Disabling this setting causes errors to appear appropriately.

Our documentation should be updated via IDB-721. Closed.