none
Problem in Exchange Provisioning (2010) with FIM - "no-start-ma" RRS feed

  • Question

  • Hello,

    We are currently using MIM 2016 (I know its not exactly FIM 2010 but it's the only forum I found) and do Exchange Provisionning (Exchange 2010). Sometimes and for unknown reasons, we are getting the following errors "not-start-ma". The Management Agents refuses to launch and we have several errors in Event Viewer (see attachment). The problem is that when it's happen, we don't make major changes or big improvements... For now, we get around of this error (when happens) by reverting VM. But the we don't succeed in understanding and solving the problem.

    I try to search for this errors code or exceptions but get not much information. For example the following links : http://setspn.blogspot.fr/2010/08/fim-2010-exchange-2010-mailbox.html & http://pureidm.com/viewtopic.php?id=1. But for now we weren't able to solve this question.

    Does someone already encounter these errors and could maybe provide advices ?

    Thank you for any help

    Thibault

    Wednesday, February 17, 2016 9:23 AM

Answers

  • For records, the installation of Microsoft .NET 4.6.1 solved this problem.
    • Marked as answer by ThibaultG Wednesday, February 17, 2016 3:39 PM
    Wednesday, February 17, 2016 3:39 PM

All replies

  • For records, the installation of Microsoft .NET 4.6.1 solved this problem.
    • Marked as answer by ThibaultG Wednesday, February 17, 2016 3:39 PM
    Wednesday, February 17, 2016 3:39 PM
  • Hi ThibautG, We had this issue in past manage to fix by Installing .Net 4.6 and

    Uninstalled security update for .NET 4.6 (KB3083185)

    Last week I update .NET to 4.6.1 in MIM2016 App server since then I’m having this issue again .

    looks to me applying .NET 4.6.1 course the issue ! im going to uninstall 4.6.1 today give u update.

    Thx


    Thursday, March 17, 2016 11:41 PM
  • Hi ThibautG. i uninstall .NET 4.6.1 from MIM Server and  now i can provition account to Exchange !!!. 

    im not sure this also temporary fix..  

    Friday, March 18, 2016 12:03 AM
  • We've had this error intermittently aswell. Provisioning to Exchange 2013.

    Version: MIM2016 4.3.2064.0

    We had it Friday, but today Monday the error is gone. I guess we'll try installing .NET 4.6.1 if the error reoccurs. :)



    Did my post help? Please use "Vote As Helpful", "Mark as answer" or "Propose as answer". Thank you!

    Monday, March 21, 2016 7:35 AM
  • Hello,

    Also had this issue with and without 4.6.1 sometimes. But latest hotfix (4.3.2124.0) resolves the issue.

    Eventlog was saying on exports to AD

    Attached files:

    Faulting application name: mmsscrpt.exe, version: 4.3.2064.0, time stamp: 0x5647ffe4
    Faulting module name: mmsscrpt.exe, version: 4.3.2064.0, time stamp: 0x5647ffe4
    Exception code: 0xc0000005
    Fault offset: 0x00000000000032a1
    Faulting process id: 0x1540
    Faulting application start time: 0x01d186a329d4c3f5
    Faulting application path: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsscrpt.exe
    Faulting module path: C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsscrpt.exe
    Report Id: 67861494-f296-11e5-80c8-00155d01d728
    Faulting package full name:
    Faulting package-relative application ID:

    and latest hotfix resolves that:

    Issue 9

    MmsScrpt.exe crashes because of the binary having an invalid entry point. The most common error displayed is "Access violation."

    /Peter


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

    Friday, March 25, 2016 2:43 PM