As part of our ongoing FIM development, we've recently created a connector/XMA using ECMA 2.0. The Management Agent installs and works fine in our development environment, but during migration to our test environment, an error is being thrown which prevents us from configuring the XMA. Under Create Management Agent, we select the ECMA2 MA type, click next, select the DLL and then click refresh interfaces. The error presents as below (note, dll name cleared intentionally from screenshot): If we click ok a few times, the interfaces appear to refresh properly, but when we click next, the following error comes up: Both environments are running the latest FIM hotfix (build 4.0.3617.2), seem to be running the same versions of .NET, the miiserver.exe service accounts seem to have the same permissions, etc. The only differences I can see between the environments are: - - - Visual Studio is not installed in our test environment - - FIM Portal is installed on a separate server in our test environment I have also tried deploying the XMA to a VM I have running FIM 2010 R2 RC2 with Visual Studio 2010 installed and the XMA creates fine. Our XMA developer put some logging into the XMA and was able to determine that the error occurs without the GetConfigParameters method ever being called (which would be why the error in the second screenshot presents, I imagine). So, were a bit stumped on this end and hoping someone could point us in the right direction.

While I haven't seen this exact error case, I'd suggest a 'diff' between your test miiserver.exe.config and one known to work, paying particular attention to the .NET runtime bits. Also make sure that anything your extension might be expecting in the GAC / other dependencies are present. You could turn on the .NET Fusion debug logging after that if still no joy. There's no truly legitimate reason to install Visual Studio on any FIM box, and ECMA2 definitely does not care about the portal. --Steve

There's no truly legitimate reason to install Visual Studio on any FIM box, and ECMA2 definitely does not care about the portal. --Steve Completely agree with that. Did a diff on the miiserver.exe.config and it's all the same. Our developer has been using the .NET fusion debug logging and still hasn't had much joy. He's basically gone through and matched each dll/dependency in both environments and they all seem the same. Apparently the error is coming from the core process so there's limited debugging we can perform. To me, it would seem like there's an issue with the FIM Sync version. So, one thought at this stage is that I've noticed my user account doesn't seem to have access to the FIM Sync database... which makes me wonder if it was able to update the SQL database properly during the 4.0.3617.2 installation, even though no error/warning was thrown. I'm just in the process of getting those rights sorted and will then attempt to reinstall the hotfix, to see if that resolves the issue.