0
Answered

Unable to cast object of type 'Unify.Product.IdentityBroker.RfcBulkUpdateResponse' to type 'Unify.Product.IdentityBroker.Rfc2251.IRfcRequest

Matthew Woolnough 4 years ago updated by anonymous 4 years ago 6

Error being raised in IdB 5.1 not sure of the impact as yet.

Handling of LDAP Bulk Update request received from user mim on connection 127.0.0.1:55606 failed with error ""Unable to cast object of type 'Unify.Product.IdentityBroker.RfcBulkUpdateResponse' to type 'Unify.Product.IdentityBroker.Rfc2251.IRfcRequest'."". Duration 00:01:23.1812324.",Normal
20170630,05:43:41,UNIFY Identity Broker,LDAP Engine,Error,"An error occurred on client from 127.0.0.1:55606. More details:
Internal Server Error #11: System.InvalidCastException: Unable to cast object of type 'Unify.Product.IdentityBroker.RfcBulkUpdateResponse' to type 'Unify.Product.IdentityBroker.Rfc2251.IRfcRequest'.nformation,"Request to update entity to connector.
Request to update entities [Count:1] to connector SharePoint User Profile.",Normal
20170630,05:43:41,UNIFY Identity Broker,Connector,Information,"Update entities to connector completed.
Update entities 1 to connector SharePoint User Profile reported 1 entities saved. Duration: 00:00:00.5780823",Normal
20170630,05:43:41,UNIFY Identity Broker,Adapter,Informati
   at Unify.Framework.Auditing.AuditingExtensions.<>c__DisplayClass4_0.<TaskContinueWithExceptionPassthough>b__0(Task t)
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Unify.Product.IdentityBroker.LDAPConnection.<RespondToMessageAsync>d__33.MoveNext()",Normal
20170630,05:43:41,UNIFY Identity Broker,Adapter,Information,"Request to reflect change entities of the adapter.
Request to reflect change entities of the SharePoint Profiles (4e96758c-06c5-44dd-9f32-557b3e75d16f) adapter started.",Verbose
20170630,05:43:41,UNIFY Identity Broker,Changes register engine,Information,"Request to retrieve changes register context.
Request to retrieve changes register context started.",Verbose
Affected Versions:
Fixed by Version:

Answer

Answer
Answered

Hi Matt,

Thanks for raising this. In this case the error is legitimate, although there's a mistake in the reporting of the error which needs to be corrected. The attached Unify.IdentityBroker.LDAP.Engine.dll should correct the error reporting.

The actual error is due to the fact that Identity Broker failed to reply to an LDAP request because the connection was closed by the remote client, most likely because the remote client timed out.

Answer
Answered

Hi Matt,

Thanks for raising this. In this case the error is legitimate, although there's a mistake in the reporting of the error which needs to be corrected. The attached Unify.IdentityBroker.LDAP.Engine.dll should correct the error reporting.

The actual error is due to the fact that Identity Broker failed to reply to an LDAP request because the connection was closed by the remote client, most likely because the remote client timed out.

Thanks Curtis. Should this be deployed in the services folder?


You can deploy it to Services, yes. It should include previous patches supplied for the same DLL. As I said though, it will only correct the error reporting so it's not crucial that you deploy it.

This dll appears to break import. The service starts, but I get no-start-ma error when trying to import

Are there any errors in the Identity Broker logs, or the Windows Event Log for MIM?

The extensible extension returned an unsupported error.
 The stack trace is:
 
 "Unify.Product.IdentityBroker.LdapOperationException: Error during processing of SearchRequest targetting CN=SPOrganisations,cn=schema: Operation timed out while waiting for message queue with id of 4. ---> System.OperationCanceledException: Operation timed out while waiting for message queue with id of 4.
   at Unify.Product.IdentityBroker.LdapConnection.GetMessage(Int32 messageId)
   at Unify.Product.IdentityBroker.SearchRequest.Send(Func`2 send, Func`2 recv)
   at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
   --- End of inner exception stack trace ---
   at Unify.Product.IdentityBroker.LdapConnection.SendRequest(ILdapRequest request)
   at Unify.Product.IdentityBroker.LdapConnection.GetSchema(String schemaDn)
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.Aggregate[TSource](IEnumerable`1 source, Func`3 func)
   at Unify.Product.IdentityBroker.LdapConnectionProxy.get_LdapSchema()
   at Unify.Product.IdentityBroker.ImportProxy..ctor(KeyedCollection`2 configParameters, Schema schema)
   at Unify.Product.IdentityBroker.UnifyLdapConnectorTypeProxy.OpenImportConnection(KeyedCollection`2 configParameters, Schema types, OpenImportConnectionRunStep importRunStep)
   at Unify.Product.IdentityBroker.UnifyLdapConnector.OpenImportConnection(KeyedCollection`2 configParameters, Schema types, OpenImportConnectionRunStep importRunStep)
Forefront Identity Manager 4.4.1459.0"