none
MIM 2016: no-start-ma on AD MA export with Provision for Exchange 2010 RRS feed

  • Question

  • I'm currently testing my upgraded MIM infrastructure. This infrastructure is a lab that had FIM 2010 in it and is now running MIM 2016. I've got most of my customizations working again with little to no issues. The MIM Sync service was installed according to these steps: http://setspn.blogspot.be/2015/08/fim-2010-not-r2-upgrade-to-mim-2016.html Perhaps there's an issue in that process...

    The AD MA refuses to export when "Provision for" "Exchange 2010" is on... When I choose "No Provisioning", the AD MA exports without issues. I tried starting a remote powershell sessions from the Sync server to the Exchange RPS URI and that succeeds...

    Errors in the event log:

    The management agent controller encountered an unexpected error.

    "ERR_: MMS(8228): ..\libutils.cpp(10186): Failed to start run because of undiagnosed MA error

    Forefront Identity Manager 4.3.1935.0"

    And

    The management agent "AD_LAB" failed on run profile "E." because of an unspecified management agent error.

    Additional Information

    %3

    Any Thoughts?

    UPDATE: there's also an appcrash for mmsscrpt.exe

    Event Name: APPCRASH

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: mmsscrpt.exe

    P2: 4.3.1935.0


    http://setspn.blogspot.com


    Wednesday, September 2, 2015 12:39 PM

Answers

All replies

  • After some digging I found a solution by installing .NET 4.6

    For some more information: http://setspn.blogspot.be/2015/09/mim-2016-no-start-ma-when-exporting-to.html


    http://setspn.blogspot.com

    Wednesday, September 2, 2015 4:02 PM
  • Hello Thomas,

    also ran into that issue today in a classroom lab of my first MIM Workshop.

    Will give that a try tomorrow and hope my students are happy with that fast resolving ;-)

    Thx for reporting that.

    /Peter


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

    Wednesday, September 2, 2015 6:14 PM
  • Thanks for the feedback! Always happy to help.

    http://setspn.blogspot.com

    Wednesday, September 2, 2015 6:23 PM
  • Hi Thomas. thanks for ur post . I had this problem in past, manage to fix it by Installing .NET 4.6 as for the blog you mention.

    we didn't had this issue for couple of months but Now it's BACK !!!! . 

    recently I update .Net to 4.6.1. to fix  portal  sync rule editing issue. Is it possible this issue cause  by installing  .Net 4.6.1 ?

    Thursday, March 17, 2016 9:51 PM
  • this really frustrating !!!  i uninstall .NET 4.6.1 from MIM Server and i can provition account to Exchange !!!. 

    im not sure this also temporary fix..  :( :(  

    update 

    .NET Framework 4.6.1 and Exchange compatibility

    http://blogs.technet.com/b/exchange/archive/2016/02/10/on-net-framework-4-6-1-and-exchange-compatibility.aspx




    • Edited by TechCJ Friday, March 18, 2016 12:10 AM Update
    Thursday, March 17, 2016 11:56 PM
  • Hi,

    did you install one of the hotfixes for MIM ?

    I have no issues with Exchange Provisioning and .Net 4.6.1 with build 4.3.2064.0 and 4.3.2124.0

    /Peter


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

    Friday, March 18, 2016 8:35 AM
  • Hi Peter, thanks for your reply . NO didn't apply any HOTFIXES.

    Current Version details. 

    

    i download 

    Hotfix rollup package (build 4.3.2124.0) extract .ZIP  .there are like 19 .EXE files. do i have to follow any order in  install this updated ? 

    • Edited by TechCJ Monday, March 21, 2016 12:11 AM update1
    Sunday, March 20, 2016 11:00 PM
  • We have installed hotfixes, and still have this problem intermittently (MIM2016). Provisioning to Exchange 2013.

    Monday, March 21, 2016 7:41 AM
  • Build 4.3.2195 (KB3134725) now out. Installed the rollup and problem seems to have vanished. Maybe the problem had something to do with Issue 9 under the MIM Synchronization Service that the hotfix rollup package fixes.
    Tuesday, May 31, 2016 11:44 AM