A hotfix rollup package (build 4.1.3508.0) is available for Forefront Identity Manager 2010 R2

Applies to: Microsoft Forefront Identity Manager 2010 R2 Service Pack 1

Introduction


A hotfix rollup package (build 4.1.3508.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2. This hotfix rollup package resolves some issues that are described in the "More Information" section.

Update information

A supported update is available from Microsoft Support. We recommend that all customers apply this update to their production systems.

Microsoft Support

If this update is available for download from Microsoft Support, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Additionally, you can obtain the update from Microsoft Update or from Microsoft Update Catalog.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Component update packages

The following table contains the component update packages that are included in the download from Microsoft Support.

ComponentFile name
FIM 2010 R2 Add-ins and ExtensionsFIMAddinsExtensions_xnn_KB2913228.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.
FIM 2010 R2 Add-ins and Extensions Language PackFIMAddinsExtensionsLP_xnn_KB2913228.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.


FIM 2010 R2 Certificate Management
FIMCM_xnn_KB2913228.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.
FIM 2010 R2 Certificate Management Bulk Issuance ClientFIMCMBulkClient_x86_KB2913228.msp
FIM 2010 R2 Certificate Management ClientFIMCMClient_xnn_KB2913228.msp

Note Versions of this file are available for x86-based and x64-based versions of FIM 2010.
FIM 2010 R2 Service and PortalFIMService_x64_KB2913228.msp
FIM 2010 R2 Service Portal Language PackFIMServiceLP_x64_KB2913228.msp
FIM 2010 R2 Synchronization Service FIMSyncService_x64_KB2913228.msp

Known issues in this update

Synchronization 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:
  • MIIServer.exe
  • Mmsscrpt.exe
  • Dllhost.exe
For example, you edited the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service MA.

In this case, the synchronization engine installer for this update intentionally does not replace the configuration file to avoid deleting your previous changes. Because the configuration file is not replaced, entries that are required by this update will not be present 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:
  1. Make a backup copy of the MIIServer.exe.config file.
  2. Open the MIIServer.exe.config file in a text editor or in Microsoft Visual Studio.
  3. Find the <runtime> section in the MIIServer.exe.config file, and then replace the content of the <dependentAssembly> section with the following:

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

  4. Save the changes to the file.
  5. 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.
  6. Restart the Forefront Identity Manager Synchronization Service (FIMSynchronizationService).
  7. Verify that the rules extensions and custom management agents now work as expected.

FIM Reporting

If you install FIM Reporting on a new server that has Microsoft System Center 2012 Service Manager Service Pack 1 installed, follow these steps:
  1. Install the FIM 2010 R2 SP1 FIMService component. To do this, click to clear the Reporting check box.
  2. Install this hotfix rollup to upgrade the FIM Service to build 4.1.xxxx.0.
  3. Run the change-mode installation for the FIM Service, and then add Reporting.


If reporting is enabled and the change-mode installation is run for FIM Service and Portal, you must be re-enable reporting. To do this in the FIM Identity Management Portal, follow these steps:
  1. On the Administration menu, click All Resources.
  2. Under All Resources, click System Configuration Settings.
  3. Click the System Configuration Settings object, and then open the Properties of this object.
  4. Click Extended Attributes, and then click to select the Reporting Logging Enabled check box.
  5. Click OK, and then click Submit to save the change.

Prerequisites

To apply this update, you must have Forefront Identity Manager 2010 R2 (build 4.1.2273.0 or a later build) installed.

Restart requirement

You must restart the computer after you apply the Add-ins and Extensions (Fimaddinsextensions_xnn_kb2913228.msp) package. Additionally, you may have to restart the server components.

Replacement information

This update replaces the following updates:
2906832 A hotfix rollup package (build 4.1.3496.0) is available for Forefront Identity Manager 2010 R2

2889529 A hotfix rollup package (build 4.1.3479.0) is available for Forefront Identity Manager 2010 R2

2877254 A hotfix rollup package (build 4.1.3469.0) is available for Forefront Identity Manager 2010 R2

2870703 A hotfix rollup package (build 4.1.3461.0) is available for Forefront Identity Manager 2010 R2

2849119 A hotfix rollup package (build 4.1.3451.0) is available for Forefront Identity Manager 2010 R2

2832389 A hotfix rollup package (build 4.1.3441.0) is available for Forefront Identity Manager 2010 R2

2814853 A hotfix rollup package (build 4.1.3419.0) is available for Forefront Identity Manager 2010 R2

2772429 Service Pack 1 (build 4.1.3114.0) is available for Forefront Identity Manager 2010 R2

2750671 A hotfix rollup package (build 4.1.2548.0) is available for Forefront Identity Manager 2010 R2

2734159 A hotfix rollup package (build 4.1.2515.0) is available for Forefront Identity Manager 2010 R2

File information

The 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 nameFile versionFile sizeDateTimePlatform
Fimaddinsextensionslp_x64_kb2913228.mspNot applicable3,928,06423-Jan-201407:30Not applicable
Fimaddinsextensionslp_x86_kb2913228.mspNot applicable1,594,88023-Jan-201407:08Not applicable
Fimaddinsextensions_x64_kb2913228.mspNot applicable5,206,52823-Jan-201407:30Not applicable
Fimaddinsextensions_x86_kb2913228.mspNot applicable4,664,32023-Jan-201407:08Not applicable
Fimcmbulkclient_x86_kb2913228.mspNot applicable9,094,65623-Jan-201407:08Not applicable
Fimcmclient_x64_kb2913228.mspNot applicable5,573,63216-Jan-201407:30Not applicable
Fimcmclient_x86_kb2913228.mspNot applicable5,195,77623-Jan-201407:08Not applicable
Fimcm_x64_kb2913228.mspNot applicable31,791,61623-Jan-201407:30Not applicable
Fimcm_x86_kb2913228.mspNot applicable31,387,64823-Jan-201407:08Not applicable
Fimservicelp_x64_kb2913228.mspNot applicable12,197,88823-Jan-201407:30Not applicable
Fimservice_x64_kb2913228.mspNot applicable31,207,42423-Jan-201407:30Not applicable
Fimsyncservice_x64_kb2913228.mspNot applicable36,194,30423-Jan-201407:30Not applicable

More Information


Issues that are fixed or features that are added in this update

This update fixes the following issues that were not previously documented in the Microsoft Knowledge Base.

FIM Service and Portal

Issue 1
If a FIMService instance loses connection to the FIMService database, the FIMService instance may stop processing FIM Service MA export requests. This results in failed FIM Service MA exports that have a run status of stopped-server. Additionally, the following exception is logged in the Forefront Identity Manager event log:

System.Data: System.InvalidOperationException: The requested operation cannot be completed because the connection has been broken.


Issue 2
If a Transition Out management policy rule uses a dynamic set that includes a multivalued attribute, and two or more elements are removed from the attribute in a single request (one of which triggers the Transition-Out MPR), the request fails. Additionally, you receive the following exception:

Microsoft.ResourceManagement.WebServices.Exceptions.UnwillingToPerformException: Other ---> System.Data.SqlClient.SqlException: Reraised Error 2627, Level 14, State 1, Procedure DoEvaluateRequestInner, Line 1073, Message: Violation of PRIMARY KEY constraint 'PK__#1B54B73__5330D0771D3CFFB1'. Cannot insert duplicate key in object 'dbo.@transitionOutapplicableRuleBuffer'.


Issue 3
When an export that is run in the FIM Service MA includes updates to the Filter attribute of multiple dynamic groups, a failed-modification-via-web-services exception may be returned. When you review the details of the exception, you find that an SQL deadlock occurred.

FIM Synchronization Service

Issue 1
If a multivalued attribute is exported and then changed directly in the target system, the change is not evaluated during delta synchronization. For example, this issue occurs in the following scenario when the Active Directory Management Agent is used:
  1. A change to proxyAddresses is exported to the Active Directory for User1.
  2. A second change is made to proxyAddresses directly in Active Directory outside the synchronization service.
  3. A Delta Import run profile is run to confirm the exported changes.
In this scenario, the next delta sync will not process the change.
Issue 2
If an exception is thrown by the Connector’s password extension during password synchronization, the Connector will be unloaded from memory. This behavior may cause high processor usage on the computer that is hosting the FIM Synchronization Service when that computer processes password synchronization if it is under load or is synchronizing passwords to multiple Connectors.

After this update is installed, exceptions of type PasswordPolicyException and PasswordIllFormedException no longer discard the password interface and unload the Connector. This lets the interface to be reused for another password operation to the connected data source. The password operation will not be retried and is removed from the queue. Any other exception will still unload the Connector and reload it at the next password operation.

References


Learn about the terminology that Microsoft uses to describe software updates.