0
Published
UNIFYNow Invalid Cast Exception
Ravneel Lal 5 years ago
•
updated by Beau Harrison (Senior Product Software Engineer) 5 years ago •
9
Getting the following error in Event Broker. Running version: 4.0.4 Rev 1
Operation AD MA - Delta Import and Delta Sync with id 72e8799b-cbf2-402b-9d2e-119957d9cfc2 failed in the operation list REDACTED Outgoing with id 21bb9f43-c07e-42db-bb21-118e7752123c for the following reason. This is retry number 0: System.InvalidCastException: The agent of type IdentityBrokerAgentAuditingDecorator was not of requested type IMIMAgent.
at Unify.Product.EventBroker.AgentExtensions.GetTypedAgent[TAgent](IAgent agent)
at Unify.Product.EventBroker.AgentEngineRepository.GetAgent[TAgent](Guid agentId)
at Unify.Product.EventBroker.RunProfilePlugInFactory.CreateComponent(IOperationFactoryInformation factoryInformation)
at Unify.Framework.ExtensibilityPlugInGenerator`4.CreateComponent(TFactoryInfo factoryInformation)
at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)
Customer support service by UserEcho
Hi Rav,
Looks like a configuration issue. Have you been manually editing the extensibility configuration at all? Try reconfiguring your agents with trivial changes to give Now the chance to correct itself. Attach your config here if that doesn't work and I'll take a look.
Also try reconfiguring all MIM operations to ensure they have the correct agent selected.
Thanks Beau, we don't have remote access to this client yet so when we do go back to the customer are there any other things you'd want to have a look at?
No, nothing else at this point. Looked into this a bit more but it definitely seems like the MIM operation has been configured with an agent of an incorrect type. This shouldn't be possible though the UI so most likely was caused from manual editing. In that case, it might be best to check all your operations, either manually or the way I described in my previous comment.
Have you had a chance to try my recommendations yet? If so, what did you find?
No I haven't had the chance yet, what sort of changes would these be? The issue is in production but not in any other environment so the changes would have to be made in production.
Hi Rav,
The config is showing that there's an Identity Broker agent configured for a MIM MA run profile operation. This isn't supported, which is why you're seeing the error that you are.
This generally wouldn't happen through the UI, which is why Beau asked above about manually editing the extensibility.
To fix this, you can follow the directions Beau has given above (try reconfiguring your agents with trivial changes) as this might give the service the chance to correct (or flag) the invalid configuration. Otherwise, manually editing the configuration with the correct agent or reconfiguring the operation in the UI will have a chance at resolving it.
Let us know whether any of these things work.
Thanks, I'll see if I can get on a call with the customer this week.
Hi Rav, moved this conversation to Voice for visibility.
You cannot configure an operation with an incompatible agent in the UI, so any of listed options are of the correct type. As to which one you should pick, that is dependent on the solution so I can't say one way or the other.