0
Answered

Creating IdB 5 ECMA2 receive error: "Could not load file or assembly 'Microsoft.MetadirectoryServicesEx, Version=4.1.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

André van der Westhuizen 4 years ago in UNIFYBroker/Microsoft Identity Manager • updated by anonymous 3 years ago 5

I have installed the UNIFY Identity Broker for Microsoft FIM v5.0.2 RTM x64.msi and have copy the Unify.IdentityBroker.FIMAdapter.dll to the extension directory.

I'm creating the ECMA 2 MA to be used with Unify.IdentityBroker.FIMAdapter.dll, as per https://unifysolutions.jira.com/wiki/display/IDBFIM50/Management+Agent I receive the following error:

I receive the following error in the event viewer:

Log Name:      Application
Source:        FIMSynchronizationService
Date:          8/25/2015 4:00:04 PM
Event ID:      6300
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SVR-FIM.FIMTest.local
Description:
The server encountered an unexpected error:
 
 "Could not load file or assembly 'Microsoft.MetadirectoryServicesEx, Version=4.1.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

   at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
   at System.Reflection.RuntimeAssembly.GetExportedTypes()
   at Microsoft.MetadirectoryServices.Impl.ScriptHost.InitializeWorker(InitializeArguments pArgs)


InnerException=>
none
"
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="FIMSynchronizationService" />
    <EventID Qualifiers="49152">6300</EventID>
    <Level>2</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-25T06:00:04.000000000Z" />
    <EventRecordID>14368</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SVR-FIM.FIMTest.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Could not load file or assembly 'Microsoft.MetadirectoryServicesEx, Version=4.1.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

   at System.Reflection.RuntimeAssembly.GetExportedTypes(RuntimeAssembly assembly, ObjectHandleOnStack retTypes)
   at System.Reflection.RuntimeAssembly.GetExportedTypes()
   at Microsoft.MetadirectoryServices.Impl.ScriptHost.InitializeWorker(InitializeArguments pArgs)


InnerException=&gt;
none
</Data>
  </EventData>
</Event>

image.png
image1.PNG
miiserver.exe.config
Affected Versions:
Fixed by Version:

Hi André van der Westhuizen,

What version of FIM are you on? I haven't seen this issue since Microsoft did a run of really bad updates that broke compatibility for a while. Can you check what content is in miiserver.exe.config, if it mentions this dll is may be out of date. If there are binding redirects, it should look something like the one on here, but using the current version of the dll, whatever that might be.

Thanks.

I'm using FIM 4.1.3646.0 and have change the miiserver.exe.config (attached):

<dependentAssembly>
<assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="3.3.0.0-4.1.2.0" newVersion="4.1.3.0" />
</dependentAssembly>

I could recreate the MA, but when I create the Run Profiles I receive the same error in FIMSync:

I receive the same error in the Event Viewer as well.

Got it working after I view the mmsscrpt.exe.config file:

      <dependentAssembly>
        <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="3.3.0.0-4.1.3.0" newVersion="4.1.4.0" />
      </dependentAssembly>

Update the miiserver.exe.config file to be the same, restart the FIMSync service and could create the run profiles

Looks like they're updated the reference but didn't properly update the config file.

Nice work.

Issue can be closed as the issue has been resolved