none
MIM error on manual Join RRS feed

All replies

  • Not sure if this helps but I get the same error when I try to disconnect a deleted AD Connector in the MetaVerse Search (in the Object Properties box)
    MIM Version is 4.3.2195.0

    

    Tuesday, June 28, 2016 8:23 PM
  • I bet you both tried with disabled provisioning? And with "neutral" deletion rule (not coded)?

    Moreover please try in elevated PowerShell:

    cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    .\installUtil.exe 'C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\UIShell\Microsoft.DirectoryServices.MetadirectoryServices.Config.dll'

    It would install one of the assemblies that is not properly installed by MIM installer. It enables MIIS.MA.Config snap-in - maybe it would help here as well.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

    Wednesday, June 29, 2016 5:51 AM
  • Dominik;

    Thank you for your reply! 

    I have a deletion rule in the metaverse designer that has been there since FIM 2010 (pre R2)

    I closed out of the MIISClient.exe and ran the commands and retried to disconnect (no reboot).

    I still get the same error when I try to dis-connect.

    Just for grins and giggles I rebooted the Sync Server. 

    Went back into the client and tried the disconnect - still did not work.

    I'm open to other ideas.

    -Jon

    I bet you both tried with disabled provisioning? And with "neutral" deletion rule (not coded)?

    Moreover please try in elevated PowerShell:

    cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319

    .\installUtil.exe 'C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\UIShell\Microsoft.DirectoryServices.MetadirectoryServices.Config.dll'

    It would install one of the assemblies that is not properly installed by MIM installer. It enables MIIS.MA.Config snap-in - maybe it would help here as well.


    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.



    Wednesday, June 29, 2016 12:44 PM
  • I'm getting the same error when I attempt to manually disconnect an AD record from a MV object. Just upgraded to MIM 2016 SP1. Has anyone made any progress on this issue?

    Thanks, Dave

    Tuesday, October 11, 2016 7:22 PM
  • Hey Carol -

    In my case, the CS object I was joining up was failing it's sync rules.  Once I cleaned up the source data and the rules were OK, I was able to join the objects manually.

    Hope it helps (if it's even still an issue for you).



    Keith

    Wednesday, October 12, 2016 5:00 AM
  • Carol Is this easy to reproduce what is your setup consist of ? trying to see if we can reproduce as it appear we are evaluating provisioning / deprovision logic on the join to include sync rule

    Wednesday, October 12, 2016 12:49 PM
    Moderator
  • Carol I have been able to reproduce this adding to my list of items to understand why
    Thursday, November 10, 2016 1:21 AM
    Moderator
  • Carol

    I have been able to reproduce your issue using any Build of MIM (Not SP1).

    Next I did 2 test from build 4.3.2266 -  (1)upgraded to 4.4.1237.0 Next test (2)patched to the SP1 build 4.4.1302

    So it appears the solution is here to upgrade to SP1 to resolve this specific behavior on manual Join.

    Thursday, November 10, 2016 1:08 PM
    Moderator
  • David;

    I'm confused, I thought SP1 was build 4.4.1237 ? I still have the issue with build 4.4.1237

    https://blogs.technet.microsoft.com/iamsupport/idmbuildversions/

    I don't see build 4.4.1302? Is that a public release yet?

    Thanks for your help.

    Jon

    Thursday, November 10, 2016 3:53 PM
  • Jmanley 1302 is a inplace upgrade patch  so you don't have to uninstall MIM to get to SP1 https://blogs.technet.microsoft.com/iamsupport/2016/11/08/microsoft-identity-manager-2016-service-pack-1-update-package/
    Thursday, November 10, 2016 4:13 PM
    Moderator
  • Carol

    I have been able to reproduce your issue using any Build of MIM (Not SP1).

    xt I did 2 test from build 4.3.2266 -  (1)upgraded to 4.4.1237.0 Next test (2)patched to the SP1 build 4.4.1302


    So it appears the solution is here to upgrade to SP1 to resolve this specific behavior on manual Join.


    So did it work once you upgraded to 4.4.1302? currently on 4.4 1237 and have the same issue
    Tuesday, December 6, 2016 5:09 AM
  • Have the same problem with manual join Carol initially reported on MIM RTM

    Upgraded to V4.4.1302.0 but problem still exists, so not sure that SP1 or 1302 is necessarily the fix

    Wednesday, December 14, 2016 3:19 PM
  • SP1 is not fixed , I am working on finding the issue at this point
    Wednesday, December 14, 2016 5:49 PM
    Moderator
  • Hi All

    We are running version 4.4.1302.0 and are experiencing the same issue when disconnecting objects from the MetaVerse.  We have upgraded from FIM 2010 R2 to MIM 2016 to MIM SP1. 

    Keith's post about checking the Sync Rules was the solution to fixing our issue.  We had an export rule extension on a different management agent that was using one of the attributes that was being recalled.  

    We added a filter rule for the account name of the object we wanted to disconnect from the Management Agent, so we could run a preview and see what the error message was.  Ideally, this is the error message that should be getting displayed, instead of the current one. 

    Thanks,

    Ian


    • Edited by Ian Bassi Thursday, February 2, 2017 4:08 PM Workaround to issue found.
    Thursday, February 2, 2017 2:40 PM
  • David - This is still an issue in 4.4.1642.

    Can you please give us a status update for this issue.

    Below is the dump from when I attempted a manual Join.

    Thanks;

    Jon

    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.ArgumentNullException: Value cannot be null.
    Parameter name: value
       at System.String.IndexOf(String value, Int32 startIndex, Int32 count, StringComparison comparisonType)
       at Microsoft.DirectoryServices.MetadirectoryServices.UI.WebServices.MMSErrors.AdjustErrorTextForExtensionException(String& sErrorString)
       at Microsoft.DirectoryServices.MetadirectoryServices.UI.AccountJoiner.AccountJoinerControl.Join()
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
    ----------------------------------------
    miisclient
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/miisclient.exe
    ----------------------------------------
    PropertySheetBase
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/PropertySheetBase.DLL
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1099.0 built by: NETFXREL4STAGE
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    UiUtils
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/UiUtils.DLL
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1087.0 built by: NETFXREL4STAGE
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    MmsServerRCW
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/MmsServerRCW.DLL
    ----------------------------------------
    System.ServiceProcess
        Assembly Version: 4.0.0.0
        Win32 Version: 4.6.1087.0 built by: NETFXREL4STAGE
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
    ----------------------------------------
    Operations
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/Operations.DLL
    ----------------------------------------
    GroupListView
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/GroupListView.DLL
    ----------------------------------------
    MaExecution
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/MaExecution.DLL
    ----------------------------------------
    AccountJoiner
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/AccountJoiner.DLL
    ----------------------------------------
    mmsuihlp
        Assembly Version: 0.0.0.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/mmsuihlp.DLL
    ----------------------------------------
    ObjectLauncher
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/ObjectLauncher.DLL
    ----------------------------------------
    ObjectViewers
        Assembly Version: 4.4.1642.0
        Win32 Version: 4.4.1642.0
        CodeBase: file:///C:/Program%20Files/Microsoft%20Forefront%20Identity%20Manager/2010/Synchronization%20Service/UIShell/ObjectViewers.DLL
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

    Tuesday, September 26, 2017 2:22 AM
  • @David Steadman - Any news on this? We're still seeing this in 4.4.1749.0.

    SV

    Tuesday, August 28, 2018 9:10 AM
  • Hi everyone,

    Any news on that issue? I'm running into it in the 4.4.1749.0 version.

    Thursday, September 20, 2018 12:53 PM
  • The "Could not find any resources appropriate for the specified culture or neutral culture" is still an issue even at patch level 4.5.26.0.  Would recommend you open up a Microsoft Premier case, if you have such support, and see if the fix will be in the next update.

    Best,

    Jeff Ingalls

    Friday, September 21, 2018 12:01 AM
  • Hi guys,

    I’ve upgraded FIM 2010 in place to MIM 2016 SP1, and I’m having the same error here. First of all, I’m not sure why MIM 2016 is unable to join to the Connector automatically, as it used to work well in FIM 2010 R2.

    So, I started troubleshooting the issue by myself. I’ve looked for the connector space on MA “SQL – CAIXA POSTAL ID” and run a “Full Sync Preview”.

    Then, I found out the rule that provisions the object in OpenLDAP MA (which was having problem, since the DN already exists in MA):

    In my case, the problem was the OpenLDAP connector space “liebr08” was already connected to a different Metaverse object.

    And, the reason for it is, the environment’s rules does not actually support the renaming of this specific kind of object. (This is not relevant by now, so I will have to work on it someday).

    Therefore, I needed to run a “Manual Join” twice. First time using the “liebr08” object from OpenLDAP, and the second time with the “Caixa Postal ID” object from Metaverse.

    It worked fine after that:

    So, I assume the the problem with the “manual join” error on “miisclient” is just an issue for displaying the error message, rather than a problem with the client itself.

    Tuesday, October 30, 2018 3:47 PM