MIM 2016 Miisactivate error on hot standby RRS feed

  • Question

  • I'm trying to set up a hot standby sync server for an existing MIM 2016 v4.4.1749.0 server. I ran through the installation steps without any issue, but when I tried to the miisactivate command with syntax like:

    miisactivate c:\temp\miiskeys.bin CONTOSO\service-mimsync *

    It popped up a usage error for MIIS key management utility, usage MIISKMU

    with arguments of:  /e filename [/u:username {password | *}] [/q].

    I tried rerunning miisactivate with the adjusted arguments, and that gives me an MIIS warm standby activation tool syntax error that tells me my first syntax attempt should be fine. So it looks like miisactivate calls a sub process and passes arguments in an incorrect way. Anyone run into this problem and have any work around suggestions?

    • Edited by Nathan Linley Wednesday, June 6, 2018 2:38 AM spelling
    Wednesday, June 6, 2018 2:37 AM

All replies

  • It's been a long time since I've used it - you may have to report that to MS.

    Again it's been a long time since I've done it - but re-running the setup in Repair mode used to be an alternative way to activate a standby.

    Friday, June 8, 2018 9:54 PM
  • Thanks for the reply.  I'm asking our DSE to see if they are able to come up with any answers and share any solutions here.

    From procmon, I see the miisactivate process launching miiskmu with "/i keyfilepath {0E19E162-827E-4077-82D4-E6ABD531636E} /u:domain\username *".  The /i and the guid value aren't in the listed syntax for the command, so who knows which part it isn't liking.  The guid shows up as a string in the miiskmu.exe file, but I couldn't find it anywhere else.

    If I take that same command and remove the guid value, it runs and asks for a password this time, but then it throws an error saying the key set is not what it expects for the db. 

    Tuesday, June 12, 2018 6:27 AM
  • I was told by MS that this is a bug that started after MIM 2016 SP1 and will be addressed in an upcoming hotfix.


    Wednesday, June 20, 2018 11:39 PM