FIM fails to run Extensible Connectivity 2.0 MA after applying KB2688078
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.
May 23rd, 2012 10:43am

Any comments???
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2012 2:59am

Thanks for the reply Bob. Still no luck. Would try updating to Rollup 2. Still looks like a lost cause.
May 28th, 2012 6:15am

Have you checked your event logs for DCOM errors or suchlike?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
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2012 6:44am

Yes I did check the logs, actually the event logs were the only stuff I had to carry forward my R&D. As there was nothing coming out of the R&D, we decided to roll-back the KB patch that we had applied. As we are working on a VM, we just restored the VM image from the time before we applied the patch. The only downside to that is, now we are back to square one where we are having stopped-server error while trying to export. :( Any help would be truly appreciated.
June 6th, 2012 11:17am

Unfortunately I've run in to this at a customer as well. We ended up doing an in-place upgrade to FIM 2010 R2 and everything began running again. Remember to keep your encryption key handy or do an export with MIISKMU before upgradering - and depending on the numbe of objects in your solution prepare for some upgrade time. Also, do an Server Export to save configuration before upgrade to be on the safe side. After upgade do Full Imports and Full Syncs to freshen the objects.Regards, Soren Granfeldt blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt
Free Windows Admin Tool Kit Click here and download it now
June 20th, 2012 3:10am

I don't know if you guys solved this already but check the version of the Microsoft.MetadirectoryServices.dll file, I'm pretty sure there is known issue with 4.0.3606.2 being upgraded to 4.0.3617.2 and this file not being updated properly. If this is true, you should be able to fix by getting correct version of the file and replacing the 3606 version. Also, did you verify the .NET 4.0/miiserver.exe.config file issue that Bob mentioned above?
August 18th, 2012 2:43am

After installing RU 2 with the new ECMA 2.0, my existing XMAs all died. Here is the error I get t from them: These are physical Sync servers so I am stuck unless I can find a way to re-install and make SQL play nice with the new structures, but I doubt it. The management agent controller encountered an unexpected error. "BAIL: MMS(6064): extensionmanager.cpp(550): 0x80230709 BAIL: MMS(6064): extensionmanager.cpp(1740): 0x80230709 BAIL: MMS(6064): export.cpp(1090): 0x80230709 BAIL: MMS(6064): export.cpp(130): 0x80230709 BAIL: MMS(6064): cntrler.cpp(3530): 0x80230709 ERR: MMS(6064): cntrler.cpp(3673): Controller Export failed with hr= 80230709. Forefront Identity Manager 4.0.3617.2" I performed the rollup to 3617 too, but it did not help. MS is working on this for me and I'll get back to you when I hear something. They are working on several of these.
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2012 11:00am

After installing RU 2 with the new ECMA 2.0, my existing XMAs all died. Here is the error I get t from them: These are physical Sync servers so I am stuck unless I can find a way to re-install and make SQL play nice with the new structures, but I doubt it. The management agent controller encountered an unexpected error. "BAIL: MMS(6064): extensionmanager.cpp(550): 0x80230709 BAIL: MMS(6064): extensionmanager.cpp(1740): 0x80230709 BAIL: MMS(6064): export.cpp(1090): 0x80230709 BAIL: MMS(6064): export.cpp(130): 0x80230709 BAIL: MMS(6064): cntrler.cpp(3530): 0x80230709 ERR: MMS(6064): cntrler.cpp(3673): Controller Export failed with hr= 80230709. Forefront Identity Manager 4.0.3617.2" I performed the rollup to 3617 too, but it did not help. MS is working on this for me and I'll get back to you when I hear something. They are working on several of these.
August 25th, 2012 11:00am

Soren ..... I have read some posts that describe failed attempts to do in-place upgrades to FIM 2010 R2. Do you have a good reference for tips on the procedure? I have solved this problem dows to a single NOTES field that is producing the problem, but I would like to have all of the data if possible. Thanks Mike W.
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2012 1:02pm

Take a look at miiserver.exe.config -- what do you have in the <startup /> block? Also examine Microsoft.MetadirectoryServicesEx.dll; is it the exact same version against which your ECMA2 was built? If not, add a bindingRedirect to miiserver.exe.config (presuming this is running in-process) or update the development copy and rebuild. In my experience almost all "ECMA + FIM update" issues stem from the two areas above. --Steve
August 25th, 2012 1:32pm

Any resolution from anyone for this one - one of my customers has just run into this issue with old Extensible MAs. Environment was running rollup update 2 and after updating to latest patch we have run into this issue with all ExMAs. Changes in miiserver.exe.config files are not helping. Doing things with DLLs is not helping. All files seems to be in correct version.
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2012 3:21pm

Any resolution from anyone for this one - one of my customers has just run into this issue with old Extensible MAs. Environment was running rollup update 2 and after updating to latest patch we have run into this issue with all ExMAs. Changes in miiserver.exe.config files are not helping. Doing things with DLLs is not helping. All files seems to be in correct version.
August 25th, 2012 3:21pm

@Tomasz: I've only run into this at one customer and they were only running Sync Service, so we did and in-place upgrade to R2 and everything was back to "normal". I did not have enough time to troubleshoot, so I can't repro the problem unfortunately. Seems like MS is working on this apparently.Regards, Soren Granfeldt blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2012 3:30pm

@Tomasz: I've only run into this at one customer and they were only running Sync Service, so we did and in-place upgrade to R2 and everything was back to "normal". I did not have enough time to troubleshoot, so I can't repro the problem unfortunately. Seems like MS is working on this apparently.Regards, Soren Granfeldt blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt
August 25th, 2012 3:30pm

I've yet to do an in-place upgrade of the FIM Service/Portal; we only did the Sync Engine. We are planning for a reinstallation (followed by re-sync) when time allows for it, as I'm not fond off in-place upgrades.Regards, Soren Granfeldt blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt
Free Windows Admin Tool Kit Click here and download it now
August 25th, 2012 3:33pm

I've yet to do an in-place upgrade of the FIM Service/Portal; we only did the Sync Engine. We are planning for a reinstallation (followed by re-sync) when time allows for it, as I'm not fond off in-place upgrades.Regards, Soren Granfeldt blog is at http://blog.goverco.com | twitter at https://twitter.com/#!/MrGranfeldt
August 25th, 2012 3:33pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics