none
FIM To MIM upgradation RRS feed

  • Question

  • After installing MIM on fresh server(2012 r2) using old FIM Sync DB i'm getting following error at the time of synchronization :

    CS to MV to CS synchronization failed 0x80230716

    Error 3/28/2016 12:01:39 PM Application Error 1000 (100)

    Log Name:      Application
    Source:        Application Error
    Date:          3/28/2016 12:01:39 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     --
    Description:
    Faulting application name: mmsscrpt.exe, version: 4.3.1935.0, time stamp: 0x559060a9
    Faulting module name: mmsscrpt.exe, version: 4.3.1935.0, time stamp: 0x559060a9
    Exception code: 0xc0000005
    Fault offset: 0x00000000000032a1
    Faulting process id: 0x1634
    Faulting application start time: 0x01d188e995ca0133
    Faulting application path: E:\APPS\Microsoft Identity Manager\2016\Synchronization Service\Bin\mmsscrpt.exe
    Faulting module path: E:\APPS\Microsoft Identity Manager\2016\Synchronization Service\Bin\mmsscrpt.exe
    Report Id: d38c00b8-f4dc-11e5-80fa-0ae236639831
    Faulting package full name: 
    Faulting package-relative application ID: 
    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="2016-03-28T12:01:39.000000000Z" />
        <EventRecordID>6554</EventRecordID>
        <Channel>Application</Channel>
        <Computer>--</Computer>
        <Security />
      </System>
      <EventData>
        <Data>mmsscrpt.exe</Data>
        <Data>4.3.1935.0</Data>
        <Data>559060a9</Data>
        <Data>mmsscrpt.exe</Data>
        <Data>4.3.1935.0</Data>
        <Data>559060a9</Data>
        <Data>c0000005</Data>
        <Data>00000000000032a1</Data>
        <Data>1634</Data>
        <Data>01d188e995ca0133</Data>
        <Data>E:\APPS\Microsoft Identity Manager\2016\Synchronization Service\Bin\mmsscrpt.exe</Data>
        <Data>E:\APPS\Microsoft Identity Manager\2016\Synchronization Service\Bin\mmsscrpt.exe</Data>
        <Data>d38c00b8-f4dc-11e5-80fa-0ae236639831</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

    I encountered the same error earlier but installing latest version of .net framework resolved the issue.

    Monday, March 28, 2016 12:06 PM

All replies

  • Hi,

    in the latest hotfix 4.3.2124.0 there is an issue fixed with the mmscript.exe, but I'm not 100% sure if it is related to your issue. Never saw this error before.

    /Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Monday, March 28, 2016 4:42 PM
  • it didn't worked still getting same error after installing  hotfix 
    Tuesday, March 29, 2016 12:59 PM
  • Hi,

    this error is normally related to .Net issues.

    Can you check the following parts of your miiserver.exe.config file in SynchEngine's \bin folder ?

    I should look like this:

      <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0"></supportedRuntime>
        <supportedRuntime version="v2.0.50727"></supportedRuntime>
      </startup>
    
      <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
          <dependentAssembly>
            <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
            <bindingRedirect oldVersion="3.3.0.0-4.1.3.0" newVersion="4.1.4.0" />
          </dependentAssembly>
          <probing privatePath="Assemblies" />
        </assemblyBinding>
      </runtime>
    

    Note that Net 4.0 is the first entry in the above part, also the runtime versions should be correct.

    /Peter


    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Tuesday, March 29, 2016 1:07 PM
  • file is exactly same with both the version available in C:\Windows\Microsoft.NET\Framework64 folder.

    thanks in advance.

    Wednesday, March 30, 2016 1:10 PM
  • I think I'm running out of options, if no one else has an idea you maybe need to contact support for that.

    Peter Stapf - ExpertCircle GmbH - My blog: JustIDM.wordpress.com

    Wednesday, March 30, 2016 7:53 PM