Using build 4.0.3606.2, I have an extensible MA (connection DLL) that throws errors (correctly) on export that are NOT getting passed back and displayed in the Synchronization Manager. I would expect them to appear as Export Errors. This happens for EntryExportException and UnexpectedDataException errors (haven't tested any others). UnexpectedDataException logs its errors, as expected, to the event log, whereas EntryExportException does not. Both result in FIM thinking the export has completed, so it is no longer pending and does not get re-tried (until a subsequent full import/sync regenerates it). Is this a problem with this version of the synch engine? SV

Are you using ECMA2 or XMA framework? Could you maybe show a few lines of code thats not working (throwing the exception)?Regards, Soren Granfeldt blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt