0
Answered

Operation List for Identity Broker for chris21 failed

Shane Lim 8 years ago • updated by anonymous 3 years ago 8

I have a composite Adapter for chris21 with the AdapterId=

{D5251D7D-05CC-4d35-916E-E99E06B9FFD3}

I can perform various Run Profile operation from FIM on chris21 MA without issue.

I can also scheduled am Operation
List without the Check Operation to perform the Run Profile operation - Full Import and Full Sync through Event Broker successfully.

In Event Broker v3.0.0.1 I created a chris21 Agent with the following settings:
Name: chris21-pdt_MA-AHG
Endpoint Address: http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc
Endpoint Configuration: IdentityBroker

Note: For the Endpoint Address, the tip provided as the possible parameter does not include the ending /mex as documented in Identity Broker Changes

Thus one of the above source of information is out of date.

- Create an Operation List, name: OpList - chris21 IdB - Incoming
- Added a Schedule: Runs every 00:00:30 from 5/2/2011 12:00:00 PM
- Added a Check Operation with the following settings:
** Retries: 2
** Retry wait time: 00:02:00
** Select Agent: chris21-pdt_MA-AHG
** AdapterId: {D5251D7D-05CC-4d35-916E-E99E06B9FFD3}

(but being automatically replaced to D5251D7D-05CC-4d35-916E-E99E06B9FFD3)

  • Added two Standard Operations for Run Profile operations.

When this Operation List is enabled and the following error occurred:

/3/2011 12:50:07 PM Warning
 UNIFY Event Broker Agent Engine The test of Agent ADDS MA-AHG (32c0ad55-b955-42c0-9194-fd73e2752fb7) failed with message:
System.Runtime.InteropServices.COMException (0x80005000): Unknown error (0x80005000)
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()
at Unify.Product.EventBroker.ADAgent.TestConnection()
at Unify.Product.EventBroker.AgentEngine.Notify(ITestAgentConnectionMessage message) 
5/3/2011 12:50:31 PM Error
 UNIFY Event Broker Operations Operation 019455c9-1baa-4b00-8060-7c162fe50af6 failed in operation list with id 9ac60794-67eb-493d-9463-d73d94b02776 for the following reason. This is retry number 0: System.Runtime.Remoting.ServerException: Operation for management agent with id f0fada76-9b8d-42ab-aee2-5de0b22b576a with name Delta import and delta synchronization failed with result call-failure:0x800706BE
at Unify.Product.EventBroker.FIMAgent.ExecuteRunProfile(IStoredValueCollection storedValuesCollection, Guid agentId, Guid managementAgentId, Guid runProfileId)
at Unify.Product.EventBroker.RunProfilePlugIn.Execute()
at Unify.Product.EventBroker.StandardOperationListExecutor.RunNextOperations(IEnumerator`1 operationEnumerator) 
5/3/2011 1:05:07 PM Warning
 UNIFY Event Broker Agent Engine The test of Agent ADDS MA-AHG (32c0ad55-b955-42c0-9194-fd73e2752fb7) failed with message:
System.Runtime.InteropServices.COMException (0x80005000): Unknown error (0x80005000)
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()
at Unify.Product.EventBroker.ADAgent.TestConnection()
at Unify.Product.EventBroker.AgentEngine.Notify(ITestAgentConnectionMessage message) 

The Operation List status has a "Running" icon next to it and reporting that it is performing the operation 1 of 3.



When change the Agent setting to include the /mex to the Endpoint Address as below

In Event Broker v3.0.0.1 I created a chris21 Agent with the following settings:
Name: chris21-pdt_MA-AHG
Endpoint Address: http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc/mex
Endpoint Configuration: IdentityBroker

I got the following error instead.

3/2011 12:45:30 PM Error
 UNIFY Event Broker Operations Operation 65ac34b8-2148-4650-90b8-7369f76a27c4 failed in operation list with id 9ac60794-67eb-493d-9463-d73d94b02776 for the following reason. This is retry number 1: System.ServiceModel.EndpointNotFoundException: The message with To 'http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc/mex' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree.

Server stack trace: 
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Unify.Framework.IChangesAvailableAdapter.ChangesAvailable(Guid adapterId)
at Unify.Product.EventBroker.IdentityBrokerChangesPlugIn.Check()
at Unify.Product.EventBroker.StandardOperationListExecutor.RunCheck(ICheckOperationFactoryInformation checkOperation) 
5/3/2011 12:47:30 PM Error
 UNIFY Event Broker Operations Operation 65ac34b8-2148-4650-90b8-7369f76a27c4 failed in operation list with id 9ac60794-67eb-493d-9463-d73d94b02776 for the following reason. This is retry number 2: System.ServiceModel.EndpointNotFoundException: The message with To 'http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc/mex' cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher. Check that the sender and receiver's EndpointAddresses agree.

Server stack trace: 
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Unify.Framework.IChangesAvailableAdapter.ChangesAvailable(Guid adapterId)
at Unify.Product.EventBroker.IdentityBrokerChangesPlugIn.Check()
at Unify.Product.EventBroker.StandardOperationListExecutor.RunCheck(ICheckOperationFactoryInformation checkOperation) 

Moreover, I have changed the service .exe.config file suitably, so it should not require additional configuration the next time around.

Shane,

Thank you for bringing this to our attention. The documentation was not very clear or consistent on this point.

Your first error is not an issue with the Identity Broker changes operation, but rather a failure in attempting to run the FIM operation. I am unsure what the issue you had there is, but it would signify the IdB Changes operation succeeded and reported a change.

On the second issue, the Identity Broker Changes operation actually works without you even needing to specify the endpoint address in the .exe.config file - I have updated the documentation suitably. However, this operation is now in a state pending completion of some work relating to EB-250. The endpoint address will also no longer require service names, but will rather require the service location, eg. "http://localhost:59990".

Marked as resolved, but the fix is still pending work on EB-250, and will be available in the next release.

Hi Matthew,

You correct in regarding to the following:
1 - The Identity Broker Changes operation is working correcly.
2 - The error reported is due to Event Broker performing the FIM Run Profile for "Delta import and delta synchronization" failed. Not sure why this happended.

However, I cannot seem to be able to locate the relevant log for the successful operations for Run Profile.

I will look further at the Logging, Log filter and Severity Log Filter

I have not come across information in regarding to the default Severity Log Filter used if it is not specified. But it seems to be set to "Information" based on my current log file.

Ok I have retested this Identity Broker Changes operation and the run profile Delta import and delta synchronization. It ran successfully.

However, I cannot locate the relevant log for the run profile in the log file. I have modified the Unify.Product.EventBroker.LoggingEnginePlugInKey.extensibility.config.xml as below:

<?xml version="1.0" encoding="utf-8" ?>

<LoggingEngine changeId="{916DF3E6-7752-409F-9C21-7B4D855EE744}" logDaysKeep="5" filePrefix="UnifyLog">
	<LogWriter name="AsyncLogWriterComposite">
		<logFilter name="Severity" severity="All" />
		<LogWriter name="Console" />
	</LogWriter>
</LoggingEngine>

In the FIM Sync Manager there are corresponding of FIM Operation log with status as success.

Did I missed something here or is this by design?

PS: If this required creating another issue please advice.

For clarification,

The functional Identity Broker Agent configuration is
Name: chris21-pdt_MA-AHG
Endpoint Address: http://localhost:59990/IdentityBroker/ChangesAvailableAdapter.svc
Endpoint Configuration: IdentityBroker

That is without the "/mex" at the end of the url.
Also I did not have to configure the EventBrokerService.exe.config file. It seems that the document in Jira is out of date, see EB-274 for details.

Re-open and assign to Matthew to pass the info back in regarding to possible oselete info. Once satisfied please resolved this issue so I can close it.

The documentation has been updated. Resolved with EB-274