A hotfix rollup package (build 4.1.3634.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2 SP1

Applies to: Forefront Identity Manager 2010 R2


A hotfix rollup package (build 4.1.3634.0) is available for Microsoft Forefront Identity Manager (FIM) 2010 R2 Service Pack 1 (SP1). The build number for BHOLD components that are included in this release is 5.0.2959.0. This hotfix rollup package resolves some issues and adds some features 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.

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, this issue may occur after you edit the MIIServer.exe.config file to change the default batch size for processing sync entries for the FIM Service management agent.

To avoid deleting your previous changes in this situation, the synchronization engine installer for this update does not replace the configuration file. 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 DLL files 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 as follows:

    <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
    <bindingRedirect oldVersion="" newVersion="" />

  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 SP1 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.3599.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 select the Reporting Logging Enabled check box.
  5. Click OK, and then click Submit to save the change.


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

Restart requirement

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

Replacement information

This update replaces the following updates:
3011057 A hotfix rollup (build 4.1.3613.0) is available for Forefront Identity Manager 2010 R2 SP1

2980295 A hotfix rollup (build 4.1.3599.0) is available for Forefront Identity Manager 2010 R2

2969673 A hotfix rollup (build 4.1.3559.0) is available for Forefront Identity Manager 2010 R2

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

File information

Hotfix release build numbers
Hotfix releaseBuild number
Forefront Identity Manager 4.1.3634.0
BHOLD 5.0.2959.0
Access Management Connector 5.0.2959.0

File attributes
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
AccessManagementConnector.msiNot applicable6717447-Apr-158:47Not applicable
BholdAnalytics 5.0.3016.0_Release.msiNot applicable27033607-Apr-158:36Not applicable
BholdAttestation 5.0.3016.0_Release.msiNot applicable32112647-Apr-159:22Not applicable
BholdCore 5.0.3016.0_Release.msiNot applicable50176007-Apr-158:24Not applicable
BholdFIMIntegration 5.0.3016.0_Release.msiNot applicable35307527-Apr-158:59Not applicable
BholdModelGenerator 5.0.3016.0_Release.msiNot applicable32563207-Apr-159:34Not applicable
BholdReporting 5.0.3016.0_Release.msiNot applicable19947527-Apr-159:10Not applicable
FIMAddinsExtensionsLP_x64_KB3048056.mspNot applicable39214087-Apr-154:29Not applicable
FIMAddinsExtensionsLP_x86_KB3048056.mspNot applicable15933447-Apr-154:17Not applicable
FIMAddinsExtensions_x64_KB3048056.mspNot applicable52080647-Apr-154:29Not applicable
FIMAddinsExtensions_x86_KB3048056.mspNot applicable46627847-Apr-154:17Not applicable
FIMCMBulkClient_x86_KB3048056.mspNot applicable91069447-Apr-154:17Not applicable
FIMCMClient_x64_KB3048056.mspNot applicable55700487-Apr-154:29Not applicable
FIMCMClient_x86_KB3048056.mspNot applicable52034567-Apr-154:17Not applicable
FIMCM_x64_KB3048056.mspNot applicable334965767-Apr-154:29Not applicable
FIMCM_x86_KB3048056.mspNot applicable330997767-Apr-154:17Not applicable
FIMServiceLP_x64_KB3048056.mspNot applicable122209287-Apr-154:29Not applicable
FIMService_x64_KB3048056.mspNot applicable313395207-Apr-154:29Not applicable
FIMSyncService_x64_KB3048056.mspNot applicable362096647-Apr-154:29Not applicable

More Information

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

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

Password Change Notification Service

Issue 1
Windows 2012 R2 Domain Controller Support

Supportability for Password Change Notification Service (PCNS) and Active Directory Management Agent in a Windows Server 2012 R2 domain and forest includes the following:
  • Password Change Notification Service is working correctly on Windows Server 2012 R2-based domain controllers.
  • Active Directory Management Agent for Windows 2012 R2 domain and forest correctly handles password change events.

Note In all supported cases, the FIM Synchronization Service must be installed only on a Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012 member server. It must not be installed on a Windows Server 2012 R2 member server. Only the PCNS component can be installed on a Windows Server 2012 R2 domain controller.

Synchronization Service

Issue 1
When PCNS calls into the FIMSynchronizationService, the FIMSynchronizationService makes an LsaLookupNames2 API call. This call fails because of the format of the domain.

For example, the format of the domain fails and generates the following error:

BAIL: MMS(3120): d:\bt\35150\private\source\miis\password\listener\pcnslistener.cpp(316): 0x80070534 (No mapping between account names and security IDs was done.): Win32 API failure: 1332

BAIL: MMS(3120): d:\bt\35150\private\source\miis\password\listener\pcnslistener.cpp(570): 0x80070534 (No mapping between account names and security IDs was done.)

FIM Service and Identity Management Portal

Issue 1
Custom search scope
Incorrect results are shown when multiple question mark (?) characters are found.

Issue 2
Comma-separated values (CSV) format is not supported for file upload for UocFileDownload in an FIM resource control display configuration (RCDC). After you apply this hotfix, CSV format is added to the allow list of supported formats for this control.

Certificate Management

Issue 1
When a customer search returns too many objects, the following error is generated:

'ADsDSOObject' failed without an error message available, result code: -2147016669(0x80072023)

The method that is used, SearchUsers, did not use the DirectorySearcher object. Search is now updated to use the DirectorySearcher object.


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