Forefront Identity Manager (FIM), Connected Data Source Extensions and stopped-extension-dll-load

I was trying to develop a new Connected Data Source Extensions for FIM using Visual Studio 2010, but FIM wouldn’t accept it. It kept giving me the error message “stopped-extension-dll-load” – without any further error details.

Turns out the error details are located in the windows application event log, there it said;

The management agent "Test MA" failed on run profile "Full Export". The run step stopped because a configured extension for this management agent could not be loaded.

User Action
Verify that the extension is located in the Extensions directory.

Well, the file is located in the correct directory, so that isn’t the problem… after some head scratching, tinkering and asking around it turns out that I should be using .NET Framework 3.5 instead of .NET Framework 4.0 – which Visual Studio 2010 defaults to. A soon as I switched over, I was able to connect to the MA without issue! Thanks Henrik for suggesting sticking to 3.5.

Claiming that the file couldn’t be found was extremely un-helpful, that alone cost me a lot of wasted time.

About mfagerlund
Writes code in my sleep - and sometimes it even compiles!

2 Responses to Forefront Identity Manager (FIM), Connected Data Source Extensions and stopped-extension-dll-load

  1. colin b says:

    Thanks for posting this. Potentially saved me a lot of time.

    Colin

  2. Indy_Jimbo says:

    You just saved me a boatload of time!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: