From the looks of things it's the exact same issue at the same customer. I don't know if Jerry ever resolved it. I've attached the log entry that's showing the error. It's using Idb and Chris 21 versions 4.1.x. Their Chris21 instance is version 8.16.17.

Adam suggested running some Chris 21 query as a resolution but I'm not sure where that query should be run. Is this likely to be a misconfiguration of Chris21 or something with IdB? This is in a test environment.

Please let me know if you need any more information.

Using Broker/Microsoft Active Directory v5.3.0.0 RTM I tried changing the "Scope" configuration setting from "Base" to "Subtree" using the UI and it immediately reverted back to "Base" after saving.  Looking in the ConnectorEnginePluginKey extensibility file the scope setting appears to be missing altogether, so I can't manually set it:

Hi all,

Sorry for the slightly odd place to log this, it seemed the least incorrect.  I'm attempting to obtain the Chris21 ISOs but the links appear to have expired.  The page I am attempting to grab these from is:

https://unifysolutions.sharepoint.com/teams/CTO/Lists/Azure%20ISOs/AllItems.aspx?viewpath=%2Fteams%2FCTO%2FLists%2FAzure%20ISOs%2FAllItems.aspx

When I run exports to the Content Manager MA, I'm getting cd-errors with no further information on all pending exports. Doing a FIFS and then another export changes the number of exports so something is getting through. Looking at the logs, it looks like the ldap connection is being closed before the response is sent back to MIM. Attached logs.

Using these versions

I just created an AD Agent and then created a connector, gave it a name and set the Object Container

and as soon as the created Connector comes up, it has an error "This connector requires at least one key".

I hit request schema and get this error:

I added sAMAccountName as a the key and required and the error "This connector requires at least one key" goes away but when I request the schema I still get the above, "Value cannot be null. Parameter name: key"

I've just created a fresh VM and installed IdB 5.3 then IdB for AD then IdB Plus. When I started the service and navigated to localhost:8008 I got an asp.net error telling me to turn custom errors off. I did that and got the following. I haven't tried anything to resolve it yet, just thought this might be a bug.

Method not found: 'Void Unify.Framework.ExtensibilityPlugInDictionary`4..ctor(System.IO.DirectoryInfo, System.String, Unify.Framework.IUnifyBranding)'.

Exception Details: System.MissingMethodException: Method not found: 'Void Unify.Framework.ExtensibilityPlugInDictionary`4..ctor(System.IO.DirectoryInfo, System.String, Unify.Framework.IUnifyBranding)'.

I'm getting this error on the IdB homepage

What does this mean? There's no certificate settings in the Settings tab 

I have two dn.multi fields that I want to coalesce into a single list and also ensure it is unique. It would be something like this

$bothFields = $entity["placepositionoccupants"] + $entity["acpositionoccupants"]

$entity["occupants"] = $bothFields | select-object -unique

This doesn't work though. There's a couple things wrong with it. There's no addition operation for whatever object type the entity is and also when I do a select-object -unique it seems to longer be the type that Broker requires. Any hints on how I can achieve this is powershell? If I had the the object type that's required, I could create a new instance of that and then loop through the two lists adding as appropriate but I don't know the object type and couldn't find it any doco.

I have a customer that has modified their database schema and has had a flow on effect to IDB where it will not run as there is an extra column.  Problem being the extra column has been added in multiple places and need to be able to isolate exactly which db/table/column each attribute connects to so I can inform the customer which instance of the extra column is causing IDB to fail so they can remove.