Update informationA supported update is available from Microsoft Support. We recommend that all customers apply this update to their production systems.
Microsoft SupportA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Known issues in this updateSynchronization Service
After this update is installed, rules extensions and custom management agents (MAs) that are based on Extensible MA (ECMA1 or ECMA 2.0) may not run and may produce a run status of "stopped-extension-dll-load." This issue occurs when you run such rules extensions or custom MAs after you change the configuration file (.config) for one of the following processes:
In this case, the synchronization engine installer for this update intentionally does not replace the configuration file in order to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update will not be in the files, and the synchronization engine will not load any rules extension DLLs when the engine runs a Full Import or Delta Sync run profile.
To resolve this issue, follow these steps:
- Make a backup copy of the MIIServer.exe.config file.
- Open the MIIServer.exe.config file in a text editor or in Microsoft Visual Studio.
- Find the <runtime> section in the MIIServer.exe.config file, and then replace the content of the <dependentAssembly> section with the following:
<assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="18.104.22.168-22.214.171.124" newVersion="126.96.36.199" />
- Save the changes to the file.
- Find the Mmsscrpt.exe.config file in the same directory and the Dllhost.exe.config in the parent directory. Repeat steps 1 through 4 for these two files.
- Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
- Verify that the rules extensions and custom management agents now work as expected.
PrerequisitesTo apply this update, you must have Microsoft Identity Manager 2016 build 4.3.1935.0 or a later build installed.
Restart requirementYou must restart the computer after you apply the Add-ins and Extensions (Fimaddinsextensions_xnn_kb3145585.msp) package. Additionally, you may have to restart the server components.
Replacement informationThis update replaces update 3134725 (build 4.3.2124.0) for Microsoft Identity Manager 2016.
File informationThe global version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
|Fimsyncservice_x64.msp||Not Applicable||14,888,960||21-Feb-2016||04:26||Not Applicable|
Issues that are fixed or features that are added in this updateThis update fixes the following issues or adds the following features that were not previously documented in the Microsoft Knowledge Base.
Issue 1When you have characters in the SMTP address that are unsupported by Exchange Server, a GALSync Export operation stops, and you receive a ma-extension error. This triggers a provisioning loop that causes object duplication and parsing errors (System.ArgumentException: parsing).
Article ID: 3145585 - Last Review: 4 May 2017 - Revision: 2