none
FIM Sync Service Crashing RRS feed

  • Question


  •  
     

    I’m getting intermittent sync service errors where the service seems to stop and restart in the middle of an import from FIM Service (actually it’s during the FS, not the import)

     

    Event viewer shows

     

    The program miisclient.exe version 4.0.3573.2 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

    Process ID: 13a4

    Start Time: 01ccb885f82418b4

    Termination Time: 23

    Application Path: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\UIShell\miisclient.exe

    Report Id: 7623f4bb-25eb-11e1-87d0-005056900021

     

    Faulting application name: miiserver.exe, version: 4.0.3573.2, time stamp: 0x4d39b393

    Faulting module name: miiserver.exe, version: 4.0.3573.2, time stamp: 0x4d39b393

    Exception code: 0xc0000005

    Fault offset: 0x00000000002275dc

    Faulting process id: 0x%9

    Faulting application start time: 0x%10

    Faulting application path: %11

    Faulting module path: %12

    Report Id: %13

     

    Fault bucket , type 0

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

     

    Problem signature:

    P1: miiserver.exe

    P2: 4.0.3573.2

    P3: 4d39b393

    P4: miiserver.exe

    P5: 4.0.3573.2

    P6: 4d39b393

    P7: c0000005

    P8: 00000000002275dc

    P9:

    P10:

     

    Attached files:

     

    These files may be available here:

    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_miiserver.exe_9476ed48d7cc7d15b84efd44edc2bc5ab6874240_3fd780d6

     

    Analysis symbol:

    Rechecking for solution: 0

    Report Id: cb023a72-25ef-11e1-87d0-005056900021

    Report Status: 4

     

    Version=1

    EventType=APPCRASH

    EventTime=129682983641353194

    ReportType=2

    Consent=1

    ReportIdentifier=cb023a72-25ef-11e1-87d0-005056900021

    Response.type=4

    Sig[0].Name=Application Name

    Sig[0].Value=miiserver.exe

    Sig[1].Name=Application Version

    Sig[1].Value=4.0.3573.2

    Sig[2].Name=Application Timestamp

    Sig[2].Value=4d39b393

    Sig[3].Name=Fault Module Name

    Sig[3].Value=miiserver.exe

    Sig[4].Name=Fault Module Version

    Sig[4].Value=4.0.3573.2

    Sig[5].Name=Fault Module Timestamp

    Sig[5].Value=4d39b393

    Sig[6].Name=Exception Code

    Sig[6].Value=c0000005

    Sig[7].Name=Exception Offset

    Sig[7].Value=00000000002275dc

    DynamicSig[1].Name=OS Version

    DynamicSig[1].Value=6.1.7601.2.1.0.274.10

    DynamicSig[2].Name=Locale ID

    DynamicSig[2].Value=1033

    UI[2]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exe

    LoadedModule[0]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exe

    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll

    LoadedModule[2]=C:\Windows\system32\kernel32.dll

    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll

    LoadedModule[4]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll

    LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll

    LoadedModule[6]=C:\Windows\system32\msvcrt.dll

    LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll

    LoadedModule[8]=C:\Windows\system32\RPCRT4.dll

    LoadedModule[9]=C:\Windows\system32\USER32.dll

    LoadedModule[10]=C:\Windows\system32\GDI32.dll

    LoadedModule[11]=C:\Windows\system32\LPK.dll

    LoadedModule[12]=C:\Windows\system32\USP10.dll

    LoadedModule[13]=C:\Windows\system32\ole32.dll

    LoadedModule[14]=C:\Windows\system32\VERSION.dll

    LoadedModule[15]=C:\Windows\system32\Secur32.dll

    LoadedModule[16]=C:\Windows\system32\SSPICLI.DLL

    LoadedModule[17]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsutils.dll

    LoadedModule[18]=C:\Windows\system32\OLEAUT32.dll

    LoadedModule[19]=C:\Windows\system32\WLDAP32.dll

    LoadedModule[20]=C:\Windows\system32\CRYPT32.dll

    LoadedModule[21]=C:\Windows\system32\MSASN1.dll

    LoadedModule[22]=C:\Windows\system32\NETAPI32.dll

    LoadedModule[23]=C:\Windows\system32\netutils.dll

    LoadedModule[24]=C:\Windows\system32\srvcli.dll

    LoadedModule[25]=C:\Windows\system32\wkscli.dll

    LoadedModule[26]=C:\Windows\system32\SAMCLI.DLL

    LoadedModule[27]=C:\Windows\system32\MPR.dll

    LoadedModule[28]=C:\Windows\system32\WS2_32.dll

    LoadedModule[29]=C:\Windows\system32\NSI.dll

    LoadedModule[30]=C:\Windows\system32\LOGONCLI.DLL

    LoadedModule[31]=C:\Windows\system32\NTDSAPI.dll

    LoadedModule[32]=C:\Windows\system32\SHLWAPI.dll

    LoadedModule[33]=C:\Windows\system32\SHELL32.dll

    LoadedModule[34]=C:\Windows\system32\IMM32.DLL

    LoadedModule[35]=C:\Windows\system32\MSCTF.dll

    LoadedModule[36]=C:\Windows\system32\ntmarta.dll

    LoadedModule[37]=C:\Windows\system32\CRYPTBASE.dll

    LoadedModule[38]=C:\Windows\system32\CLBCatQ.DLL

    LoadedModule[39]=C:\Windows\system32\mscoree.dll

    LoadedModule[40]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll

    LoadedModule[41]=C:\Windows\system32\sxs.dll

    LoadedModule[42]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll

    LoadedModule[43]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_88e41e092fab0294\MSVCR80.dll

    LoadedModule[44]=C:\Windows\system32\profapi.dll

    LoadedModule[45]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\1d2d3e57724bcacaea5e41063dc565c1\mscorlib.ni.dll

    LoadedModule[46]=C:\Windows\system32\CRYPTSP.dll

    LoadedModule[47]=C:\Windows\system32\rsaenh.dll

    LoadedModule[48]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll

    LoadedModule[49]=C:\Windows\system32\WINTRUST.dll

    LoadedModule[50]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_a4d6a923711520a9\COMCTL32.dll

    LoadedModule[51]=C:\Windows\system32\imagehlp.dll

    LoadedModule[52]=C:\Windows\system32\ncrypt.dll

    LoadedModule[53]=C:\Windows\system32\bcrypt.dll

    LoadedModule[54]=C:\Windows\system32\bcryptprimitives.dll

    LoadedModule[55]=C:\Windows\system32\USERENV.dll

    LoadedModule[56]=C:\Windows\system32\GPAPI.dll

    LoadedModule[57]=C:\Windows\system32\cryptnet.dll

    LoadedModule[58]=C:\Windows\system32\SensApi.dll

    LoadedModule[59]=C:\Windows\system32\Cabinet.dll

    LoadedModule[60]=C:\Windows\system32\DEVRTL.dll

    LoadedModule[61]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\Microsoft.IdentityManagement.ExternalSettingsManager.dll

    LoadedModule[62]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll

    LoadedModule[63]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\Microsoft.IdentityManagement.SettingsContract.dll

    LoadedModule[64]=C:\Windows\system32\sqlncli10.dll

    LoadedModule[65]=C:\Windows\system32\COMDLG32.dll

    LoadedModule[66]=C:\Windows\system32\1033\SQLNCLIR10.RLL

    LoadedModule[67]=C:\Windows\system32\credssp.dll

    LoadedModule[68]=C:\Windows\system32\kerberos.DLL

    LoadedModule[69]=C:\Windows\system32\cryptdll.dll

    LoadedModule[70]=C:\Windows\system32\msv1_0.DLL

    LoadedModule[71]=C:\Windows\system32\security.dll

    LoadedModule[72]=C:\Windows\system32\schannel.DLL

    LoadedModule[73]=C:\Program Files\Microsoft SQL Server\90\Shared\instapi.dll

    LoadedModule[74]=C:\Windows\system32\mswsock.dll

    LoadedModule[75]=C:\Windows\System32\wshtcpip.dll

    LoadedModule[76]=C:\Windows\System32\wship6.dll

    LoadedModule[77]=C:\Windows\system32\DNSAPI.dll

    LoadedModule[78]=C:\Windows\system32\IPHLPAPI.DLL

    LoadedModule[79]=C:\Windows\system32\WINNSI.DLL

    LoadedModule[80]=C:\Windows\system32\rasadhlp.dll

    LoadedModule[81]=C:\Windows\System32\fwpuclnt.dll

    LoadedModule[82]=C:\Windows\system32\msiltcfg.dll

    LoadedModule[83]=C:\Windows\system32\msi.dll

    LoadedModule[84]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsmaext.dll

    LoadedModule[85]=C:\Windows\system32\RpcRtRemote.dll

    LoadedModule[86]=C:\Windows\system32\SFC.DLL

    LoadedModule[87]=C:\Windows\system32\sfc_os.DLL

    LoadedModule[88]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\fusion.dll

    LoadedModule[89]=C:\Program Files\Common Files\Microsoft Shared\Forefront Identity Manager\mmsps.dll

    LoadedModule[90]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmscntrl.dll

    LoadedModule[91]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mahostn.dll

    LoadedModule[92]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mahostm.dll

    LoadedModule[93]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\msvcm90.dll

    LoadedModule[94]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsmafim.dll

    LoadedModule[95]=C:\Windows\assembly\GAC_MSIL\Microsoft.ResourceManagement\4.0.3573.2__31bf3856ad364e35\Microsoft.ResourceManagement.dll

    LoadedModule[96]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\8c862eb9bcba031e1479974a7d62aa0b\System.ni.dll

    LoadedModule[97]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\fe860189c078d45125ca6366495fd414\System.Configuration.ni.dll

    LoadedModule[98]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.ServiceModel\4ae2cc43ea27f162942af679bf0eaaf8\System.ServiceModel.ni.dll

    LoadedModule[99]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.DirectorySer#\3623e2ad193bcccf00ac1107d4f62236\System.DirectoryServices.ni.dll

    LoadedModule[100]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\372dfe1a5b9ed9217b0f491ba07745d2\System.Xml.ni.dll

    LoadedModule[101]=C:\Program Files (x86)\IBM\Client Access\Shared\Cwbnetnt.dll

    LoadedModule[102]=C:\Windows\assembly\NativeImages_v2.0.50727_64\SMDiagnostics\d912b15f4aaac2455b690f6e477a67b1\SMDiagnostics.ni.dll

    LoadedModule[103]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.IdentityModel\4b0d5f66812e9eba4c647e5441016675\System.IdentityModel.ni.dll

    LoadedModule[104]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Runtime.Seri#\1377c29b871c7eb768769b5f4bdbb15d\System.Runtime.Serialization.ni.dll

    LoadedModule[105]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Data\4cfb4616eb3af7f91c1ea7113465860b\System.Data.ni.dll

    LoadedModule[106]=C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll

    LoadedModule[107]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Transactions\f15a8af412d84b1fd14fc735fb5834f5\System.Transactions.ni.dll

    LoadedModule[108]=C:\Windows\assembly\GAC_64\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll

    LoadedModule[109]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.EnterpriseSe#\4b0fd98f11e1e243efcfb810c170decf\System.EnterpriseServices.ni.dll

    LoadedModule[110]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Core\eed0dd8cdc46206a76e8c23872fc0787\System.Core.ni.dll

    LoadedModule[111]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Data.SqlXml\32cf78868a7f90ad05525253a2540e1f\System.Data.SqlXml.ni.dll

    LoadedModule[112]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsscpth.dll

    LoadedModule[113]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\bin\Microsoft.MetadirectoryServices.Impl.dll

    LoadedModule[114]=C:\Windows\assembly\GAC_MSIL\Microsoft.MetadirectoryServicesEx\4.0.0.0__31bf3856ad364e35\Microsoft.MetadirectoryServicesEx.dll

    LoadedModule[115]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\ExtensionsCache\MV Rules Domain\assembly\dl3\346e7bf7\15a0476f_d6a8cc01\MVExtension.DLL

    LoadedModule[116]=C:\Windows\assembly\GAC_MSIL\Microsoft.VisualBasic\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualBasic.dll

    LoadedModule[117]=C:\Windows\system32\apphelp.dll

    LoadedModule[118]=C:\Windows\system32\shfolder.dll

    LoadedModule[119]=C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll

    LoadedModule[120]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\ExtensionsCache\Sync Rule Callout{7427E432-B4B2-4701-8D2E-1DCDEB60B3EF}\assembly\dl3\2f6a8a33\00c49559_84b9cb01\FunctionLibrary.DLL

    LoadedModule[121]=C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll

    LoadedModule[122]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\ExtensionsCache\ADMA\assembly\dl3\e78fa341\46f869d7_03b9cc01\ADMA Extension.DLL

    LoadedModule[123]=C:\Windows\assembly\GAC_MSIL\System.Management.Automation\1.0.0.0__31bf3856ad364e35\System.Management.Automation.dll

    LoadedModule[124]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\ExtensionsCache\iSeries MAGIC\assembly\dl3\a7571ff7\4c524b09_a6a8cc01\iSeries MAGICExtension.DLL

    LoadedModule[125]=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\ExtensionsCache\iSeries LAWSON\assembly\dl3\f385c95d\3e4f6216_a7a8cc01\iSeries LAWSONExtension.DLL

    LoadedModule[126]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\diasymreader.dll

    FriendlyEventName=APPCRASH

    ConsentKey=APPCRASH

    AppName=Forefront Identity Manager Synchronization Service

    AppPath=C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\miiserver.exe

    ReportDescription=Stopped working

     

     

     

    Anyone seen anything similar?


    Wednesday, December 14, 2011 4:18 AM

Answers

  • Bob/Dave,

    Are either of you using equal precedence for any attribute that is being synced. We have seen similar problems in some scenarios on older builds(we have several new hotfixes since 3576) that often involve using equal precedence with reference attribute such as 'member' for groups. This is often in combination with unexpected state of objects; this can happen if there are pending exports and you don't actually export, for example.

    I would verify if equal precedence is being used. If so, newer builds fix at least some issues related to this. If not using equal precedence, perhaps try to figure out which object is causing this, you should be able to do this via a Sql profiler trace.

    Friday, March 30, 2012 4:33 AM

All replies

  • Call PSS? They're going to be best equipped to troubleshoot. You could try bumping to teh latest hotfix drop and see if that fixes it first, though.
    My Book - Active Directory, 4th Edition
    My Blog - www.briandesmond.com
    Wednesday, December 14, 2011 8:49 PM
    Moderator
  • Something similar has happened in my FIM (version 4.0.3576.2) environment, where the crash count is now up to 59:


    Log Name:      Application
    Source:        Application Error
    Date:          30/03/2012 9:52:39
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      **********************
    Description:
    Faulting application name: miiserver.exe, version: 4.0.3576.2, time stamp: 0x4d6f1cef
    Faulting module name: miiserver.exe, version: 4.0.3576.2, time stamp: 0x4d6f1cef
    Exception code: 0xc0000005
    Fault offset: 0x0000000000254836
    Faulting process id: 0x%9
    Faulting application start time: 0x%10
    Faulting application path: %11
    Faulting module path: %12
    Report Id: %13
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-03-29T22:52:39.000000000Z" />
        <EventRecordID>185255</EventRecordID>
        <Channel>Application</Channel>
        <Computer>**********************</Computer>
        <Security />
      </System>
      <EventData>
        <Data>miiserver.exe</Data>
        <Data>4.0.3576.2</Data>
        <Data>4d6f1cef</Data>
        <Data>miiserver.exe</Data>
        <Data>4.0.3576.2</Data>
        <Data>4d6f1cef</Data>
        <Data>c0000005</Data>
        <Data>0000000000254836</Data>
      </EventData>
    </Event>


    We are in the process of applying the latest hotfix rollup, but I thought I'd post this suggestion from a SharePoint blog (where the relevance is the instance of miiserver.exe which is bundled with SharePoint 2010 as part of the "BDC"):


    http://mrvsharepoint.blogspot.com.au/2010/11/fim-service-stops-after-import-and-user.html


    The suggestion (from Microsoft support) is to add the following line to the miiserver.exe.config file immediately under the <runtime> node:


    <disableStackOverflowProbing enabled="true"/>


    About to try this myself, but thought I'd post here and let you know if it fixes the problem.


    However, what I have observed so far is that the above fault occurs usually after a delta import (so I figure it needs a full import) with the following System event log entry:


    Log Name:      System
    Source:        Service Control Manager
    Date:          30/03/2012 9:52:39
    Event ID:      7034
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      ********************
    Description:
    The Forefront Identity Manager Synchronization Service service terminated unexpectedly.  It has done this 59 time(s).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
        <EventID Qualifiers="49152">7034</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2012-03-29T22:52:39.584072000Z" />
        <EventRecordID>50345</EventRecordID>
        <Correlation />
        <Execution ProcessID="552" ThreadID="13484" />
        <Channel>System</Channel>
        <Computer>********************</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">Forefront Identity Manager Synchronization Service</Data>
        <Data Name="param2">59</Data>
      </EventData>
    </Event>


    Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

    Friday, March 30, 2012 12:11 AM
  • Bob/Dave,

    Are either of you using equal precedence for any attribute that is being synced. We have seen similar problems in some scenarios on older builds(we have several new hotfixes since 3576) that often involve using equal precedence with reference attribute such as 'member' for groups. This is often in combination with unexpected state of objects; this can happen if there are pending exports and you don't actually export, for example.

    I would verify if equal precedence is being used. If so, newer builds fix at least some issues related to this. If not using equal precedence, perhaps try to figure out which object is causing this, you should be able to do this via a Sql profiler trace.

    Friday, March 30, 2012 4:33 AM
  • Thanks for getting back Glenn.

    In my environment we are about to apply hotfix rollup #2, but before we do we wanted to have half an idea as to what was causing the problems here.  In my case if I leave the sync engine alone for a couple of hours of regular activity (we are running regular run profiles on detection of changes).  In the latest case the failure was on an export of a single record to an ECMA, whereby the export started 2 seconds before a FIM MA DI/DS had fully completed.  I am wondering if the detection of the pending export occurred fractionally prematurely?  In any case when the sync server restarted and the pending export was detected it fired again, and this time it succeeded.

    We are indeed using equal precedence in the solution (I wouldn't if I had a choice) but not for this particular object that is being synchronised (contributing values come only from the FIM MA and are written out to the ECMA).


    Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

    Friday, March 30, 2012 4:49 AM