0
Fixed

LDAP Directory Changes operation exception

Tony Sheehy 5 years ago • updated by anonymous 3 years ago 5

The LDAP Directory Changes operation fails with the following exception on execution:

Operation 7b4a99fd-d4f5-42e0-9349-b672b0a83882 failed in operation list with id a0daf801-7960-4946-80c2-1234c7f5672e for the following reason. This is retry number 0: System.ArgumentNullException: Value cannot be null.
Parameter name: sourceElement
at Unify.Framework.XElementExtensions.AttributeValueModify(XElement sourceElement, XName attributeName, Action`1 modifyAttribute)
at Unify.Product.EventBroker.LDAPAgentConfigurationFactory.CreateComponent(XElement factoryInformation)
at Unify.Product.EventBroker.OpenLDAPAgentFactory.CreateComponent(IAgentInformation factoryInformation)
at Unify.Product.EventBroker.AgentEngineRepository.<>c__DisplayClass13.<GetAgent>b__12()
at Unify.Product.EventBroker.ExtensionMethods.WaitOnMutex(Mutex mutex, Action work)
at Unify.Product.EventBroker.AgentEngineRepository.GetAgent[TAgent](Guid agentId)
at Unify.Product.EventBroker.OpenLDAPChangesPlugInFactory.CreateComponent(ICheckOperationFactoryInformation factoryInformation)
at Unify.Framework.ExtensibilityPlugInGenerator`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Product.EventBroker.OperationListExecutorBase.RunCheck(ICheckOperationFactoryInformation checkOperation)

This is happening for the LDAP Listen operation too.

Tony, could you please attach the agent configuration file?

From the message it appears that the OpenLDAPAgent element is missing.

Thanks.

<Agent id="87104856-cc19-4853-a7d3-d1ac4145581e" name="LOCAL LDAP" type="Unify.EventBroker.Agent.OpenLDAP">
 <Extended xmlns="">
  <OpenLDAPAgent server="localhost" authtype="Basic" domain="prdgrp-test" username="Administrator" serverPassword="HqollTYAmyazGTJXZpgatB93nAIC0UI7jG6sv0iUVxY=" /> 
  </Extended>
  </Agent>

Other than server and authtype all the other attributes have defaults. Might have to debug this one.

Work in EB-517 broke this; the LDAP Agent Factory implemented its own way of retrieving XML, this changeset introduced usage of the AgentConfiguration Factory but provided the wrong element (OpenLDAPAgent element was provided, not the Extended element). Fixed and confirmed locally, when testing keep in mind that both the LDAP Changes and LDAP Listen were affected by this.

Confirmed complete in latest build.