We are experiencing the following EB errors in a Production environment, and require some support please.

EB v3.2.1 Revision #3

Operation ae749ebf-6f17-4caa-aa75-9e8aa29c04ac failed in operation list with id 14ddd771-c48e-4918-86e7-bc1e2f9639c5 for the following reason. This is retry number 0: System.Runtime.Remoting.ServerException: Operation for management agent with id ffebd54f-016c-4acd-80ac-3b0e62e8fbe5 with name Delta Import and Delta Sync failed with result call-failure:0x8023063D
at Unify.Product.EventBroker.FIMAgent.ExecuteRunProfile(IStoredValueCollection storedValuesCollection, Guid agentId, Guid managementAgentId, Guid runProfileId)
at Unify.Product.EventBroker.RunProfilePlugIn.Execute()
at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)

Operation 13a319a2-7701-474b-8812-0efdd1966fac failed in operation list with id deccbd3b-01c1-42eb-a261-b534ed72c0af for the following reason. This is retry number 0: System.Runtime.Remoting.ServerException: Operation for management agent with id 3d412c31-a02e-42e7-a2a0-e6fc06d68efe with name Delta Import and Delta Sync failed with result app-store-import-exception
at Unify.Product.EventBroker.FIMAgent.ExecuteRunProfile(IStoredValueCollection storedValuesCollection, Guid agentId, Guid managementAgentId, Guid runProfileId)
at Unify.Product.EventBroker.RunProfilePlugIn.Execute()
at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)

Operation ae749ebf-6f17-4caa-aa75-9e8aa29c04ac failed in operation list with id 14ddd771-c48e-4918-86e7-bc1e2f9639c5 for the following reason. This is retry number 0: System.Runtime.Remoting.ServerException: Operation for management agent with id ffebd54f-016c-4acd-80ac-3b0e62e8fbe5 with name Delta Import and Delta Sync failed with result call-failure:0x8023063D
at Unify.Product.EventBroker.FIMAgent.ExecuteRunProfile(IStoredValueCollection storedValuesCollection, Guid agentId, Guid managementAgentId, Guid runProfileId)
at Unify.Product.EventBroker.RunProfilePlugIn.Execute()
at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)

What other information do you require?

Thank you

When performing a side-by-side upgrade for 2 environments concurrently, I am experiencing a UI problem in DEV only whereby the MA and Run Profile GUIDs are not translated to the correct names on the console - even though these guids are actually correct.  This means that the run profiles do not work and ALL of them have to be edited.

Rather than go through the tedious process of editing each one of them through the UI ... they all seem to work fine after this (next/next/next seems to focus the picklists on the right entry) ... but I can't work out what is happening here exactly.

Please can I have some interactive assistance in working out what has happened - I don't want this to happen in the PROD deployment and not know what to do.

TIA

Only choices are 3.0, 4.0 and 4.1. I tried 4.1 but it fails because it needs a username and password to be specified.

Saw the following call is set to resolved, please see my comment to this call still seeing this issue

http://voice.unifysolutions.net/topics/1960-massive-memory-leak-in-ie/

Overview

PowerShell executes under a series of ExecutionPolicies that enable different access to different actors in an implementation.

Affected Software

• MIM Event Broker
• PowerShell
• MIM Portal

Symptom

Either individual PowerShell check/standard operations fail with an incorrect ExecutionPolicy message, or a similar exception is thrown when the Portal Workflow script is run.

Resolution

The Execution Policy of PowerShell will need to be updated according to the following prerequisites:

• PowerShell integration that executes within Event Broker executes under a Process Execution Policy Scope.
• The workflow script is not signed as it it generated on request, as such for this script neither the AllSigned or RemoteSigned willl work.

For more information about how to configure your ExecutionPolicy, refer to: http://technet.microsoft.com/library/hh847748.aspx

Overview

PowerShell standard or check operations fail with a message similar to:

Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.        

Affected Software

• MIM Event Broker
• PowerShell

Symptom

Either standard or check PowerShell operations fail with a Mixed Mode exception listed above.

Resolution

The application configuration of the Event Broker service will need to be updated with the following configuration, under the configuration element:

<startup useLegacyV2RuntimeActivationPolicy="true">
  <supportedRuntime version="v4.0" />
</startup>        

This configuration file can be found by default at:

C:\Program Files\UNIFY Solutions\Event Broker\Services\Unify.Service.Event.exe.config        

Description

During MIM Event Broker operation, the run profiles and management agent names presented on the interface are not consistent with those present in MIM. Run profiles may also fail to fire, and seem to be referencing old run profile names. This can occur as a result of a change to the MIM Synchronization Service configuration.

Affected Software

• MIM Event Broker
• Microsoft Identity Manager

Symptom

Run profile and management agent names are not displayed consistently with those that are present in the MIM instance. MIM Event Broker also displays alerts referencing errors that have occurred whilst attempting to execute a specific run profile, where the specified name does not exist. The following error may appear in the logs:

Operation ec28464f-e34b-448f-9d54-d9d577874500 failed in operation list with id 20a2aa29-aa98-4770-9db5-e8e2cd3fcc61 for the following reason.
This is retry number 0: System.Runtime.Remoting.ServerException: Operation for management agent with id 9f6ef9ad-ae71-4d9f-a351-d9e0734c0909 with name Full Import Full Sync failed with result no-start-unknown-profile-name
		

Solution

The behaviour mentioned in the Symptoms can occur when management agents and run profiles are either renamed or removed in MIM.

If management agents and run profiles have been renamed:

• Navigate to the Agents page, and click on the Refresh icon located next to the appropriate FIM agent.

If MAs and run profiles have been readded or removed:

• Edit the configuration for problematic run profile operations so that they reference an existing run profile.

Description

After configuring the MIM Event Broker Changes Activity to run an operation list, and adding it to a relevant MPR, the workflow fails due to a PostProcessingError, with a missing endpoint element listed as the reason.

Affected Software

• MIM Event Broker
• MIM Event Broker Changes Activity
• MIM Service and Portal

Symptom

The following error message is returned by the MIM Event Broker Changes Activity when an attempt is made to run an operation list:

Error connecting to MIM Event Broker, please review the inner exception: Could not find endpoint element with name 'ServerNotifications' and contract 'EventBrokerService.IEventServiceCollector' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this name could be found in the client element.        

Solution

This error usually means there has been an error trying to match the configuration present in the Microsoft.ResourceManagement.Service.exe.config of the MIM Service. Please confirm the steps listed here have been followed correctly, and ensure that the MIM Service is restarted following any changes.

Description

Particular operations begin failing following the deletion of an agent, and the logs suggest that the operation needs to be updated with a new agent.

Affected Software

• MIM Event Broker

Symptom

When an operation list attempts to run, the following error appears in the logs:

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)
...Operations dependent on agents may also not display correctly, such as run profile operations:

Resolution

This is caused by deleting an agent that has dependant operations configured to use it. For this reason, deleting agents is generally not recommended.

Each dependant operation must be updated to use a new agent of the appropriate type. Once the new agent is correctly configured, simply go through the configurations of each of the affected operations and select this new agent. If there have been no changes in the target system to any of the unique identifiers stored by MIM Event Broker (run profile identifiers from FIM, for instance), the operation will be able to use the original configuration for the new agent.

Description

When attempting to run the ConfigureEventBrokerChangesActivity.ps1 script when installing the MIM Event Broker Changes Activity, the script fails. The Requests section of the MIM Portal reveals a Denied error has occurred.

Affected Software

• MIM Event Broker
• MIM Event Broker Changes Activity
• MIM Portal

Symptom

When attempting to run the PowerShell script, the following error appears in the script window:

Import-FIMConfig : Failure when making web service call.
SourceObjectID = dc42094d-0f86-4035-8a98-38b3520669c9
Error = Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Policy prohibits the request from co
mpleting. ---> Microsoft.ResourceManagement.WebServices.Faults.ServiceFaultException: Policy prohibits the request from
 completing.
   at Microsoft.ResourceManagement.WebServices.ResourceFactoryClient.Create(Message request)
   at Microsoft.ResourceManagement.WebServices.ResourceFactoryClient.Create(Create createBody)
   at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.CreateResource()
   --- End of inner exception stack trace ---
   at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.CreateResource()
   at Microsoft.ResourceManagement.WebServices.ResourceManager.CreateResource()
   at Microsoft.ResourceManagement.Automation.ImportConfig.Create(String objectType, List`1 changeList)
   at Microsoft.ResourceManagement.Automation.ImportConfig.EndProcessing()
At C:\Program Files\UNIFY Solutions\Event Broker\Portal Workflow\ConfigureEventBrokerChangesActivity.ps1:67 char:27
+ $fimAIC | Import-FIMConfig <<<<
    + CategoryInfo          : InvalidOperation: (:) [Import-FIMConfig], InvalidOperationException
    + FullyQualifiedErrorId : ImportConfig,Microsoft.ResourceManagement.Automation.ImportConfig
        

A similar error message appears in the MIM Portal itself under the Requests section.

Resolution

This error is due to the MPR configuration of the Portal preventing the addition of a new Activity Information Configuration. Refer to information on configuring the Activity Information Configuration (AIC) here, or consult your MIM Portal administrator.