Share via

FIM Troubleshooting: Event ID 6152 – stopped-extension-dll-load

  • Article

 

 

Issue

A Full or a Delta Synchronization stops running rather quickly. You notice that the status on the Operations Tab (Run History) is "stopped-extension-dll-load". Investigating the issue, you notice the following error in the Application Event Log.

Application Event Log

Event ID: 6152

Event Source: FIMSynchronizationService

The management agent 'MyADMA' failed on run profile 'DI-DS'. The run step stopped because a required rules extension 'MyADMAExtension.dll' could not be loaded.    User Action  Verify that the rules extension is located in the Extensions directory. If the extension is present, confirm that the version of the .NET framework  that can run the extension is installed on the server and that a supportedRuntimes  entry in the configuration files specifies that version. The synchronization  engine will not be able to load an extension that is built with a newer version  of the .NET framework than the version of the .NET runtime it is hosting.

 

Troubleshooting Steps

We were not able to fully diagnose the cause of this specific issue, but here are some troubleshooting steps that will help guide you in the correct direction.

  • Ensure that the Management Agent Extension in question is in the Extensions folder.
  • Ensure that the Management Agent Extension Project is referencing the correct Microsoft.MetadirectoryServicesEx.DLL file ( %programfiles%\Microsoft Forefront Identity Manager\2010\Synchronization Service\bin\Assemblies )
  • Ensure that the latest version of the Microsoft .NET Framework is installed.
  • Ensure that the supportedRunTime section in the MIISERVER.EXE.CONFIG file is correct.
  • If the build is 4.0.3644, ensure that the MIISERVER.EXE.CONFIG and the MMSSCRPT.EXE.CONFIG files have been updated with the correct bindings. You can find this information in the Known Issues in this update section of the following Microsoft Knowledge Base Article.
  • Utilize FUZLOGVW.EXE to help locate and see if there is any binding issues
  • Utilize a Process Monitor Log to help isolate the issue.
  • Rebuild the Management Agent Extension

 

Resolution

In this particular issue, we rebuilt the Management Agent Extension and things started working fine.

See also