Event Broker run profile operation failed after change detected

Now I am encountering the same problem with another Operation List, this one for AD Incoming, which was working fine earlier today when debugging issue EB-340.

The error in the log

5/17/2011 6:57:30 PM Information
 UNIFY Event Broker Operation List Executor Operation list Test Op List - AD MA - Incoming started 
5/17/2011 6:57:30 PM Information
 UNIFY Event Broker Operation List Executor Running check operation Active Directory Changes for operation list Test Op List - AD MA - Incoming 
5/17/2011 6:57:30 PM Information
 UNIFY Event Broker Operation List Executor Check operation Active Directory Changes for operation list Test Op List - AD MA - Incoming returned True 
5/17/2011 6:57:30 PM Error
 UNIFY Event Broker Operations Operation bcbc6bfe-b134-4f53-9567-88e84532a221 failed in operation list with id 9852408e-0606-44a7-81a2-8766d08e28ce for the following reason. This is retry number 0: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Unify.Product.EventBroker.RunProfilePlugInFactory.CreateComponent(IOperationFactoryInformation factoryInformation)
at Unify.Framework.ExtensibilityPlugInGenerator`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Product.EventBroker.StandardOperationListExecutor.RunNextOperations(IEnumerator`1 operationEnumerator) 

The Operation List for AD details now contains the GUID in the operation name instead of plain text. See image AD-OpList-op-name-in-GUID.jpg

Here is the image of one of the Operation being updated and restored to it plain-text name while the other, not yet updated still retained the GUID name. See image AD-OpList-op-name-in-GUID-one-being-update.jpg

Repeat the process of updating all the Operations in the AD Op List and re-enabled the Operation List now run successfull - without error.

5/17/2011 7:30:33 PM Information
 UNIFY Event Broker Operation Engine An existing Unify.EventBroker.PlugIn.RunProfile operation has been successfully updated in the operation list with the id 9852408e-0606-44a7-81a2-8766d08e28ce. 
5/17/2011 7:32:47 PM Information
 UNIFY Event Broker Operation Engine An existing Unify.EventBroker.PlugIn.RunProfile operation has been successfully updated in the operation list with the id 9852408e-0606-44a7-81a2-8766d08e28ce. 
5/17/2011 7:34:30 PM Information
 UNIFY Event Broker Operation List Executor Operation list Test Op List - AD MA - Incoming started 
5/17/2011 7:34:30 PM Information
 UNIFY Event Broker Operation List Executor Running check operation Active Directory Changes for operation list Test Op List - AD MA - Incoming 
5/17/2011 7:34:30 PM Information
 UNIFY Event Broker Operation List Executor Check operation Active Directory Changes for operation list Test Op List - AD MA - Incoming returned True 
5/17/2011 7:34:30 PM Information
 UNIFY Event Broker Operation List Executor Completed Run Profile operation with id bf7891f5-c995-48cf-b745-3a07230338b5 in operation list Test Op List - AD MA - Incoming 
5/17/2011 7:34:31 PM Information
 UNIFY Event Broker Operation List Executor Completed Run Profile operation with id bcbc6bfe-b134-4f53-9567-88e84532a221 in operation list Test Op List - AD MA - Incoming 
5/17/2011 7:34:31 PM Information
 UNIFY Event Broker Operation List Executor Completed Active Directory Commit operation with id fbe41308-354e-416a-90a8-ad88541d24fe in operation list Test Op List - AD MA - Incoming 
5/17/2011 7:34:31 PM Information
 UNIFY Event Broker Operation List Executor Operation list Test Op List - AD MA - Incoming finished 

I am not sure what the cause or the problem is, but the work-around I used does work.

Thus this issue is more for the Product team to investigate or analyse and to decide whether to resolve this issue or not.

Matthew, as you were involved in both the run profile, and the display names for run profiles... could you please take a look at this issue, unless of course Patrick has you working on other more important stuff.

Thanks.

And, if there does appear to be an issue, could you please edit the issue to make it a defect.

Thanks.

Shane, this item is detailed in the troubleshooting section here. This is a result of your Event Broker instance not being able to retrieve run profile and management names from the FIM instance after your upgrade. Refreshing the agent forces this refresh to occur.

Reopening, I will update the item with your message and case also, as I just noticed the page does not mention this can also occur if FIM is uncontactable

I've investigated this issue further, as it seems that your error message isn't about the run profile names at all, but rather the agent configuration (with management agent names and run profiles not displaying merely an artefact of this). I've added a new error message in cases where this occurs suggesting users update their operations appropriately, but I would like to know if you removed and re-added your FIM agent at some stage prior to this?

Hi Matthew,
Yes I did removed and re-add the FIM Agent.

Thanks Shane, that's what would have done it. The operations all point to their referenced FIM agent, and if that disappears, they do not know what to do.

Assigned to Adam to see if this is proper handling of agent deletion. In the interim, I am updating the documentation to this effect.

Assigned to Patrick for comment.

Patrick, would the above comment be a case for raising an alert immediately after removal of an agent?

There is a TODO in code that I may have mentioned. A matching remove alert would have to be added when an agent is assigned to the operation list.

Please note that the compare would have to check both the operation list id and the agent name (key in the agent dictionary on the operation list), as the operation list can contain multiple agents.

Thanks.

Changed issue to a defect as the error message and documentation were not informative enough - this has since been corrected

Shane, can you please confirm if the new error message and description on the following pages does enough to assist users in this scenario?

• EB300:Agents
• EB300:Operations dependent on agents fail because the agent configuration is incorrect or missing

New error message:

Operation ccdb05f0-a7aa-4764-b7ff-0f88d748c293 failed in operation list with id 76809adb-cbef-4bdd-8f06-808e33b2af13 for the following reason. This is retry number 0: 
Unify.Product.EventBroker.UnifyConfigurationException: Incorrect or missing agent configuration. Please update the operation with a new agent. ---> System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Unify.Product.EventBroker.IdentityBrokerChangesPlugInFactory.CreateComponent(ICheckOperationFactoryInformation factoryInformation)

Hi Matthew,

I confirmed that the two documents referenced do provide information regarding this issue.

For the EB300:Operations dependent on agents fail because the agent configuration is incorrect or missing, another sign that this issue occurring is the Operation's name in the Operation List now containing GUID, while normally this would not.

Whether this is something you may want to consider adding to the page or not is your decision.

Thank you.

HI Patrick,

This issue is currently assigned to you, by mistake. Could you please help to assign it to Matthew for my feedback.

Thank you.

Matthew or Patrick, would it be of benefit to standardise the same exception handling in all of the operations?

(Patrick, please also read my previous comment).

Thanks.

Shane,

If you had looked at the history of the item, you would have seen the reason for it being assigned to Patrick.

Thanks.

All good Shane, I've made myself a watcher to keep across this.

That is a very good point, so I have updated the page accordingly (even using one of your screenshots as an example)

Adam, sounds like a big task if we're now heading in to release (and may be hard to test conclusively given the different conditions for each error). Yours or Patrick's call.

Hi Matthew,

Clicking on the image you of the screenshot of the incorrect display of the operation name leave the IE Window in greyout mode, with the error message at the bottom left of IE saying "Error on page".

Hi All,

If "Refreshing" or "Delete" or "Rename" of an Agent or FIM Agent will cause this issue, may I suggest that a warning or informing message box is provided to ensure they understand or remind them of the requirement to update all the relevant Operations. Perhaps the choice of to continue or cancel would be appropriate.

Just two cents.

Regards.

Shane, there is a popup, see the attached screenshot. Can you confirm if you see this or not?

Not sure why this is on me, and the last comment appears to be directed at you Shane.

Hi Matthew,

As we had discussed last week, the image added for the run profile on page EB300:Operations dependent on agents fail because the agent configuration is incorrect or missing, when clicked it left the page greyed out and no image is shown.

Shane,

Are you referring to the image in Jira not loading for you correctly? If so, it is not something Matt did.

What browser are you using?

Thanks.

Hi Adam,

I am using IE 8.0.76 on Windows 7.

I believe you are correct, because I can't click and view the large images on this page as well, https://unifysolutions.jira.com/wiki/display/EB300/Installing+the+Event+Broker+Portal+Workflow.

This is strange because I used to be able to do that before. Perhaps some Windows Updates is causing this.

If you do not require this issue to be open anymore please resolve it and assign it back to me so that I can close it. The reason I mentioned this because of your comment on "18/May/11 9:52 AM".

Thank you.

Hi Shane,

I don't believe there are any issues with IE 8. If you have javascript disabled, please enable it, otherwise I cannot help you.

Thanks.

Resolved.

Please close the issue if you feel it has been resolved.

Thanks.

Instruction is documented on how to resolve this issue, particularly when an Agent is being deleted and recreated. See

EB300:Agents
EB300:Operations dependent on agents fail because the agent configuration is incorrect or missing