There needs to be a gap between Delete Entities and Save Entities. While there are gaps between the other sections this one constantly causes me to think the delete count is actually the save count. A gap, and possibly positioning of Save above Delete, will help avoid this unnecessary confusion.

When I create a new Join and try to delete attributes I receive the following error:

HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

When the join is saved it does not saved it with the selecting criteria I used. I have to update the xml document to get the correct values.

Unify.Communicators.AurionHRMIS9302.dll - 4.1.0

Unify.Service.Connect.exe - 4.1.0

I'm trying to write a PowerShell adapter transformation. A couple of points about this:

- I want to be able to use a variable field name,

- I want to be able to search for another entity.

The use case is flattening Org Units. The feed is a classic parent-child feed and what I want is to add attributes OrgUnit1 .. OrgUnit9 to each Org Unit object in the adapter. This means I have to be able to loop through looking for parent Org Units in the $entities collection.

The following script does not work in IdB - but gives an idea about what I'm trying to do. It does work outside IdB simulating the $entity as a hashtable. If you could share some more info about what exactly $entity is I may be able to do better at getting this working outside of IdB in such as way as it will work inside too.

DOESN'T WORK:

foreach ($entity in $entities){
  $id = $entity["OrganisationUnitNumber"]
  $level = $entity["OrganisationUnitLevel"]
  $fieldname = "OrgUnit" + $level
  $entity[$fieldname]=$id
  $entity2 = $entity
  while ($level -ne "1")
  {
    $id = $entity2["SuperiorOrgUnitNumber"]
    $entity2 = $entities | where {$_["OrganisationUnitNumber"] -eq $id}
    $level = $entity2["OrganisationUnitLevel"]
    $fieldname = "OrgUnit" + $level
    $entity[$fieldname]=$id
  }
}

Using

• IdB v5.0.5 Revision #0
  Plugins
• Microsoft Active Directory 5.0.1.2
• Microsoft Azure AD Connector 5.0.1.5

The following was written this morning to the PROD IdB logs (verbose mode):

20161213,03:00:14,UNIFY Identity Broker,Service Engine,Warning,"An error occurred whilst coordinating the plug-in engine.  The error was:

System.BadImageFormatException: Could not load file or assembly 'file:///E:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect32.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'file:///E:\Program Files\UNIFY Solutions\Identity Broker\Services\Unify.Service.Connect32.exe'
   at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
   at System.Reflection.Assembly.LoadFrom(String assemblyFile)
   at Unify.Framework.ExtensibilityPlugInDictionary`4.InitializeAssemblyAttributeDefinition(String assemblyLocation)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
",Verbose

Multiple occurrences of this issue in the 24 hour period just completed (log file just rolled over).

See corresponding JIRA issue QBE-65 for log file attachment.

When viewing the VERBOSE logs today via the console, and clicking NEXT, the following exception was raised:

The logs are also attached from the time of the error here: Log file archive

It does not look like the Check operation is working, I know there are changes currently pending but Event broker does not think so.

Log below from Event Broker

20161031,05:54:34,UNIFY FIM Event Broker,Operation List Executor,Information,Operation list FIM Agent Callista Delta Import Sync started,Verbose
20161031,05:54:34,UNIFY FIM Event Broker,Operation List Executor,Information,Running check operation Identity Broker Changes for operation list FIM Agent Callista Delta Import Sync,Verbose
20161031,05:54:34,UNIFY FIM Event Broker,Operation List Executor,Information,Check operation Identity Broker Changes for operation list FIM Agent Callista Delta Import Sync returned False,Verbose
20161031,05:54:34,UNIFY FIM Event Broker,Operation List Executor,Information,Operation list FIM Agent Callista Delta Import Sync finished,Verbose

A full import ran overnight on an MA in MIM from Identity Broker returned 66 duplicate objects, on spot checking a number of the objects they only exist once in the Adapter and Connector. The EMPLID attribute (used as the CN attribute in the DN) is set as the Key on the Connector.

A subsequent full import (currently running) is exhibiting the same behaviour.

Detect The maximum array length quota <xxxx> has been exceeded while reading XML data, ignore the current limit and increase the limit dynamically, but display a warning/error message to help the client to adjust the defaults in the Web.config

I wanted to try out browsing an IdB 5.1 adapter through LDAP. I can connect to port 389 with both ADSIEdit and Softerra, and I can see a list of available containers. In ADSIEdit I also managed to see a list of object DNs in one of the containers, but couldn't get any of their properties. Softerra won't even show me the list of objects - it just sits there with a wait symbol on getting the selected container. (MA imports into MIM do work however.)

In the IdB logs I see this error:

An error occurred on client from 127.0.0.1:52790. More details:Internal Server Error #11: System.NotSupportedException: Cannot write to a BufferedStream while the read buffer is not empty if the underlying stream is not seekable. Ensure that the stream underlying this BufferedStream can seek or avoid interleaving read and write operations on this BufferedStream.
at System.IO.BufferedStream.ClearReadBufferBeforeWrite()
at System.IO.BufferedStream.Write(Byte[] array, Int32 offset, Int32 count)
at Unify.Product.IdentityBroker.LDAPConnection.PostResponse(IRfcLdapMessage message, Boolean forceFlush)
at Unify.Product.IdentityBroker.RequestHandlerAuditingDecorator.<>c__DisplayClass7_1.<HandleRequest>b__0(IRfcLdapMessage response)
at Unify.Product.IdentityBroker.SearchRequestHandlerBase.HandleRequest(IRfcLdapMessage message, CancellationToken token, Action`1 postAction)
at Unify.Product.IdentityBroker.RequestHandlerAuditingDecorator.HandleRequest(IRfcLdapMessage message, CancellationToken token, Action`1 postAction)
at Unify.Product.IdentityBroker.LDAPRequestHandlerSecurityDecorator.HandleRequest(IRfcLdapMessage message, CancellationToken token, Action`1 postAction)
at Unify.Product.IdentityBroker.LDAPConnection.<RespondToMessageAsync>d__35.MoveNext()

Unify Logs Start at 00:00:01, which is local time, but all other log entries occur at UTC time.