Hi, We have FIM 2010 v4.0.3617.2 Recently we created an Extensible Connectivity 2.0 Call-Based MA. We began simply, by first enabling IMPORT capabilities of MA. This worked fine. Later we added the EXPORT capability to this MA. The Export profile used to fail with an Event ID 6401. We did some troubleshooting and a technet article led us to try installing KB2688078 to resolve this issue. After the installation of this KB, the MA would fail to launch even the IMPORT profile. Simply even going to the Properties sheet of this MA and trying to hit Refresh Interface results in an Error "The extension operation aborted due to an internal error in FIM Synchronization Service" This message pops-up 4 times before the MA list of capabilities is shown on screen. Progressing to the other steps in Properties page lead to same result. Trying to run the MA, either Import or Export profile, shows the status as no-start-ma Digging into Event Viewer shows this: <Provider Name="FIMSynchronizationService" /> <EventID Qualifiers="49152">6401</EventID> <Level>2</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <EventRecordID>19044</EventRecordID> <Channel>Application</Channel> <Data>ERR: MMS(4380): libutils.cpp(9939): Failed to start run because of undiagnosed MA error Forefront Identity Manager 4.0.3617.2</Data> In the last 2 days of our troubleshooting, we have tried to recycle the services, restarted the server a few times, and followed other general suggestions as posted by users on technet. The only last option that the forums talk about is reinstalling the FIM. We want to avoid re-installation and troubleshoot the issue to find a fix. Still, if there is no other way out, we would like to know the impact of re-installation and how it can be avoided in the future? Would like to clarify that DB based MA's, AD based MA's and LDAP based MA's are still working fine. Only the Extensible MA's are failing. Any help will be appreciated. Thanks, -Sanket.

Sounds like you've hit another bug to me, but have you tried running your MA in a separate process, and have you got FIM Update 2 rollup installed (I can't remember all the version numbers) and not taken this into account (not the issue, but the .Net 4 issue resolution) Long shot ... but suspect a bug. Bob Bradley (FIMBob @ http://thefimteam.com) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com for just-in-time delivery of FIM 2010 policy via the sync engine