A hotfix rollup package (build 4.1.3559.0) is available for Microsoft Forefront Identity Manager 2010 R2 (FIM 2012 R2). This hotfix rollup package resolves some issues and adds some features that are described in the article below.
For all the details as well as download instructions, please see the following:
KB2969673 - A hotfix rollup (build 4.1.3559.0) is available for Forefront Identity Manager 2010 R2 (http://support.microsoft.com/kb/2969673)
J.C. Hornbeck | Solution Asset PM | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
It seems there may be a bug with this build that causes the Sync Engine Client application to crash upon closing.
In this particular case, it seems to happen if the Sync Engine Client is closed following the cancellation of MA creation. If another tab is browsed to, F5 is hit to refresh, or user waits varied amount of time without clicking, then the crash does not happen. I've tested this in 2 different environments and it is very consistent.
Problem Event Name: CLR20r3
Problem Signature 01: miisclient.exe
Problem Signature 02: 4.1.3559.0
Problem Signature 03: 5398bccb
Problem Signature 04: mmsuihlp
Problem Signature 05: 0.0.0.0
Problem Signature 06: 5398bc91
Problem Signature 07: 171
Problem Signature 08: 18
Problem Signature 09: System.AccessViolationException
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033