none
no-start-ma on AD Export for Group Membership Updates (.NET 4.6 already applied) RRS feed

  • Question

  • I'm building a MIM 2016 Solution for a customer.

    When I enabled Exchange Mailbox provisioning I got no-start-ma on Mbox creation that was solved by updating to .NET 4.6 on the MIM Sync server.

    I'm now doing Criteria based groups into AD and no-start-ma is back on Export when trying to update group membership. 

    Anyone else encountered this and have a fix ? 


    Wednesday, December 16, 2015 1:24 AM

Answers

  • Well, I have no idea what the underlying root cause was, but the MIM 2016 hotfix that became available this week has fixed my problem (even though it isn't listed in the bugfix list).

    https://support.microsoft.com/en-us/kb/3092179

    Cheers,
    DR

    • Marked as answer by DoctaMVP Thursday, December 17, 2015 11:16 PM
    Thursday, December 17, 2015 11:16 PM

All replies

  • I would not expect the .NET version to impact this. Have you verified that you can make a remote PowerShell connection to the URL in the MA properties using a normal PowerShell window on the server? That would be my starting point to test connectivity.

    Thanks,
    Brian

    Consulting | Blog | AD Book

    Wednesday, December 16, 2015 5:05 PM
    Moderator
  • Hey Brian, Thx for the reply. Yes I checked that RPS was working and the right permissions were there for the AD MA account. Deleted the AD MA and then re-imported it. Updated the Portal for the new GUID and references. Got everything joined back up and in check. Tryed to export group membership for just a security group (non-mailenabled) and same issue. no-start-ma. Very weird. Still digging but running out of ideas on this one. DR
    Thursday, December 17, 2015 1:25 AM
  • Have you checked the Windows Event Log to get more info on the error?

    no-start-ma usually produced a log in the Event Log which can tell you more.


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

    Thursday, December 17, 2015 12:26 PM
  • That's the problem with no-start-ma errors. 

    The information in Console and Event Logs is useless.

    Thursday, December 17, 2015 9:15 PM
  • Well, I have no idea what the underlying root cause was, but the MIM 2016 hotfix that became available this week has fixed my problem (even though it isn't listed in the bugfix list).

    https://support.microsoft.com/en-us/kb/3092179

    Cheers,
    DR

    • Marked as answer by DoctaMVP Thursday, December 17, 2015 11:16 PM
    Thursday, December 17, 2015 11:16 PM
  • Hi DR

    Did this error ever return? I had exactly the same issue, patched it and it worked fine for a couple of successful syncs however the error has re-occurred again. The error even occurs now after an export is run with 0 pending exports so shouldn't be due to any particular object in AD. All other exports are fine (have another 7 connectors) and when I remove Exchange provisioning off the ADMA the issue goes away

    I'm on the latest hotfix (4.3.2064.0) and .Net 4.6.00081 as you are. All the Rule Extensions have been pointed to the new MS.MetadirServicesEX.dll file as well.

    Its only a dev environment but I'm concerned if we install the production environment as MIM (as opposed to FIM R2SP1) we'll see it. It could be a red herring due to upgrading dev from FIM to MIM I suppose

    Cheers

    Goose

    Thursday, January 28, 2016 3:37 PM
  • installing .Net 4.6.01055 instead looks to have sorted itso thanks for the .Net lead!

    https://www.microsoft.com/en-us/download/confirmation.aspx?id=49982

    Goose

    Thursday, January 28, 2016 4:51 PM
  • hi , I'm having same issue !! I had this problem in past and manage to fix it by doing below. <o:p></o:p>

    http://setspn.blogspot.com.au/2015/09/mim-2016-no-start-ma-when-exporting-to.html)<o:p></o:p>

    Now it's BACK !!!!<o:p></o:p>

    recently I update .Net to 4.6.1. to fix  portal  sync rule editing issue. <o:p></o:p>

    Is it possible this issue cause  by installing  .Net 4.6.1? 

    <o:p></o:p>



    Thursday, March 17, 2016 10:23 AM
  • 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.. 

    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

    appreciate your help :(

    • Edited by TechCJ Friday, March 18, 2016 12:08 AM update
    Thursday, March 17, 2016 11:51 PM