0
Answered

FIM Event Broker System.DirectoryServices.Protocols.DirectoryOperationException

Rizwan Ahmed 9 years ago updated by anonymous 7 years ago 2

I have noticed following exception on incoming and outgoing tasks of admintribunal.internal ADMA management agent. EvB is able to trigger run profiles however following exception may cause operations to be interrupted. Log file attached with the ticket.

{{
20150712,00:00:36,FIM Event Broker,Operation List Executor,Information,Operation list FIM Agent admintribunal.internal ADMA Outgoing finished,Normal
20150712,00:00:38,FIM Event Broker,OpenLDAPTriggerPlugIn.ResultsCallback,Error,"System.DirectoryServices.Protocols:
System.DirectoryServices.Protocols.DirectoryOperationException: The server cannot handle directory requests.
at System.DirectoryServices.Protocols.LdapPartialResultsProcessor.GetPartialResults(LdapPartialAsyncResult asyncResult)
at Unify.Product.EventBroker.OpenLDAPListenPlugIn.ResultsCallback(IAsyncResult result)",Normal
20150712,00:00:38,FIM Event Broker,OpenLDAPTriggerPlugIn.ResultsCallback,Error,"System.DirectoryServices.Protocols:
System.DirectoryServices.Protocols.DirectoryOperationException: The server cannot handle directory requests.
at System.DirectoryServices.Protocols.LdapPartialResultsProcessor.GetPartialResults(LdapPartialAsyncResult asyncResult)}}


UnifyLog20150712.zip

Do the other operations against the same AD instance function correctly? If so, there may be a incorrect setting on the LDAP listen operation or a setting on AD preventing it from working. Can you see any settings that are not correct? What are the non-functional requirements? If the solution doesn't require immediate notification of changes, then it might not be worth diagnosing, otherwise you'll need to trace the failure (e.g. Wireshark).