MIM Event Broker Forum

Welcome to the community forum for MIM Event Broker.

Browse the knowledge base, ask questions directly to the product group, or leverage the community to get answers. Leave ideas for new features and vote for the features or bug fixes you want most.

0
Answered

EVB 4.0 Issue with IDB Changes Operation

Richard Green 8 years ago updated by anonymous 8 years ago 2

Hi Gents,

Here's a new one - i'm having issues with the IDB Changes operation between EVB 4.0 and IDB 5.2

I have the default configuration.

Initially i was getting the following error:

Operation Check for changes in the External AD Events Adapter with id 331db65e-4d4d-48a0-b09f-a7247c7d3f15 failed in the operation list MIM - External AD Events MA - Incoming with id ddde4bd5-4173-419b-9388-92df3f10d705 for the following reason. This is retry number 0: System.InvalidOperationException: Could not find endpoint element with name 'IdentityBroker' and contract 'IChangesAvailableCollector' 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.
 at System.ServiceModel.Description.ConfigLoader.LoadChannelBehaviors(ServiceEndpoint serviceEndpoint, String configurationName)
 at System.ServiceModel.ChannelFactory.ApplyConfiguration(String configurationName, Configuration configuration)
 at System.ServiceModel.ChannelFactory.InitializeEndpoint(String configurationName, EndpointAddress address)
 at System.ServiceModel.ChannelFactory`1..ctor(String endpointConfigurationName, EndpointAddress remoteAddress)
 at Unify.Product.EventBroker.IdentityBroker50ChangesCommunicator.ChangesAvailable(Guid adapterId)
 at Unify.Product.EventBroker.IdentityBroker50ChangesPlugIn.Check()
 at Unify.EventBroker.PlugIn.Audit.CheckOperationAuditingDecorator.Check()
 at Unify.Product.EventBroker.OperationListExecutorBase.RunCheck(ICheckOperationFactoryInformation checkOperation)

So I added the following endpoint config in the service.event.exe.config:

<endpoint binding="basicHttpBinding" contract="IChangesAvailableCollector" bindingconfiguration="StreamingFileTransferServicesBinding" name="IdentityBroker"></endpoint>


Now, i'm getting the following:

Operation Check for changes in the External AD Events Adapter with id 331db65e-4d4d-48a0-b09f-a7247c7d3f15 failed in the operation list MIM - External AD Events MA - Incoming with id ddde4bd5-4173-419b-9388-92df3f10d705 for the following reason. This is retry number 0: System.ServiceModel.Security.MessageSecurityException: The HTTP request is unauthorized with client authentication scheme 'Anonymous'. The authentication header received from the server was 'Negotiate'. ---> System.Net.WebException: The remote server returned an error: (401) Unauthorized.

Not something i've seen before...


Answer
anonymous 8 years ago

I thought this had come up before (there's a matching ticket in VSO), but can't find it in UserEcho...

Please change the endpoint element to this:

<endpoint binding="basicHttpBinding" contract="IChangesAvailableCollector" bindingconfiguration="IdentityBroker4Binding" name="IdentityBroker" />

It'll be in the next release, not sure how it was missed. Thanks.

0
Fixed

EVB - IDB API Issue

Richard Green 8 years ago updated by anonymous 8 years ago 6

Hi Guys,

I'm currently having an issue communicating with the IDB API from Event Broker. Not sure if this is IDB or EVB.

I'm getting the following error trying to run an API operation:

Operation Full Import - DAMS Contact Connector with id a1508248-0161-46a0-a703-a1cad6cfc8ed failed in the operation list IDB - DAMS Contact - Full Import with id bae408b8-0b38-495f-a92a-4b1a8319f15b for the following reason. This is retry number 0: Unify.Product.EventBroker.RestAPIAgentUnexpectedStatusException: Response code NotFound doesn't match expected response code NoContent.
 at Unify.Product.EventBroker.RestAPIPlugIn.Execute()
 at Unify.EventBroker.PlugIn.Audit.OperationAuditingDecorator.Execute()
 at Unify.Product.EventBroker.OperationListExecutorBase.RunNextOperations(IEnumerator`1 operationEnumerator)

I have the following agent configured (Have tried IDB Port with no change):

Image 4432


And the following API config in IDB:

Image 4433


IDB v5.2.0 R2

EVB v4.0.0 R1

IDB and EVB are on the same box, and i can hit the swagger page for the rest API.

Nothing applicable in the IDB logs or Event Logs (even enabled diagnostic logging in IDB)

Answer
anonymous 8 years ago

Richard, the patch provided by Curtis should be removed when you upgrade to v5.2.0 RTM - as the URL format was fixed to be in line with the format in v5.1.

0
Won't fix

EVB 4.0 Assembly Load Issue

Richard Green 8 years ago updated by anonymous 8 years ago 7

Hi Gents,

I'm having an issue with event broker at the moment:

Image 4419
Image 4421
Stack trace from Event Log:

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 14/07/2017 10:36:36 AM 
Event time (UTC): 14/07/2017 12:36:36 AM 
Event ID: a852df8e00cb40e4a34b31600dea2fca 
Event sequence: 2 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: b7cf9837-1-131444661896298544 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\Program Files\UNIFY Solutions\Event Broker\Web\ 
    Machine name: REDACTED
 
Process information: 
    Process ID: 5640 
    Process name: Unify.Service.Event.exe 
    Account name: REDACTED
 
Exception information: 
    Exception type: TypeInitializationException 
    Exception message: The type initializer for 'Unify.EventBroker.Web.EventServiceClientInstance' threw an exception.
   at Unify.EventBroker.Web.MvcApplication..ctor() in C:\agent\_work\23\s\Source\Unify.EventBroker.Web\Global.asax.cs:line 33
   at ASP.global_asax..ctor()
Could not load file or assembly 'Unify.Framework.Collections, Version=5.2.0.0, Culture=neutral, PublicKeyToken=84b9288cb2633de4' or one of its dependencies. The system cannot find the file specified.
   at Unify.Framework.TimingGenerator..ctor()
   at Unify.Framework.Logging.LoggingEngineClient..ctor(ILoggingEngineCollector collector) in C:\agent\_work\1\s\Source\Logging\Unify.Framework.Logging.Engine.Shared\LoggingEngineClient.cs:line 25
   at Unify.EventBroker.Web.EventServiceClientInstance.CreateComponent(EndpointAddress serviceEndpointAddress) in C:\agent\_work\23\s\Source\Unify.EventBroker.Web\Extensions\EventServiceClientInstance.cs:line 53
   at Unify.EventBroker.Web.EventServiceClientInstance..cctor() in C:\agent\_work\23\s\Source\Unify.EventBroker.Web\Extensions\EventServiceClientInstance.cs:line 32
 
 
Request information: 
    Request URL: http://localhost:8081/ 
    Request path: / 
    User host address: 127.0.0.1 
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: REDACTED
 
Thread information: 
    Thread ID: 236 
    Thread account name: REDACTED
    Is impersonating: False 
    Stack trace:    at Unify.EventBroker.Web.MvcApplication..ctor() in C:\agent\_work\23\s\Source\Unify.EventBroker.Web\Global.asax.cs:line 33
   at ASP.global_asax..ctor()
 
 
Custom event details:

Not sure what's going on here. This worked previously as i was able to apply the license, however this is the first i have used it since.

I've restarted the browser, service and server with no change.

Service account is a local admin, so there should not be any permissions issues.

Running the latest version (4.0) 

Running on windows server 2016.

I note also that Unify.Framework.Collections.dll is present in the web\bin dir, and it is version 5.2.1.0 (different from the 5.2.0.0 in the error message, although i expect that's just the display...)


Cheers

Richard

Answer
anonymous 8 years ago

It is the recommended approach and the embedded web server has been deprecated (as per http://voice.unifysolutions.net/topics/2721-configuring-mim-event-broker-for-use-with-embedded-web-server/).

We're hoping IIS fixes the issue because it means that there's no further work to be done. If, however, the issue remains, we'll have to do some analysis. This issue has come up before, but was either fixed by IIS, or just stops without explanation.

0
Answered

Configuring IIS Security in 4.0

Matthew Woolnough 8 years ago updated by anonymous 8 years ago 3

The EvB IIS security page contains the following example:

<? xml version="1.0" encoding="utf-8" ?>
<ConnectEngine>
    <roleAuthorizations>
        <roleAuthorization role="Unify.Event.Service.Read">
            <anonymous action="Allow" />
        </roleAuthorization>
        <roleAuthorization role="Unify.Event.User">
            <group action="Allow" groupName="Users"/>
        <roleAuthorization>
        <roleAuthorization role="Unify.Event.Administrator">
            <user action="Allow" userName="ExampleAdministrator_01" />
        </roleAuthorization>
        <roleAuthorization role="Unify.Event.Agents.Write">
            <user action="Deny" userName="UserWithDeniedAccess_03" />
        </roleAuthorization>
    </roleAuthorizations>
</ConnectEngine>

However, the Unify.Product.EventBroker.EventBrokerPlugInKey.extensibility.config.xml file contains:

<?xml version="1.0" encoding="utf-8" ?> <EventEngine changeId="{025F5A02-200E-4BA3-B74F-72623FAD3731}" />


Has the XML structure changed in 4.0?


Answer
anonymous 8 years ago

In the web.config, update owin:AutomaticAppStartup = true and AuthorizeSetting = OpenId

Then add the following:

  • ida:ClientId = your client id
  • ida:AADInstance = the id for you instance of AAD
  • ida:TenantId = the id for your tenant
  • ida:PostLogoutRedirectUri = the redirect on sign-out url
As Matthew mentioned, the page will be updated to reflect this.
0
Answered

Event Broker Errors (DEV)

Tomasz Zukowski 8 years ago updated by anonymous 8 years ago 6

We are experiencing the following Event Broker errors in a customers DEV environment:

EB: v3.2.1 Revision #3



Operation faulted: The HTTP service located at http://wlgmimsynprod01:59990/IdentityBroker/ChangesAvailable.svc is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later. - Please see the log viewer for more details.

 

Management Agent: Active Directory Privileged User MA - Run Profile: Delta Import and Delta Sync

Operation faulted: Operation for management agent with id ffebd54f-016c-4acd-80ac-3b0e62e8fbe5 with name Delta Import and Delta Sync failed with result call-failure:0x8023063D - Please see the log viewer for more details.


 


Operation fee47c32-7550-4f72-a7d4-918dc2aa2e4e failed in operation list with id f1e97e4c-2a12-4b37-9cf5-02a5225f1678 for the following reason. This is retry number 0: System.ServiceModel.ServerTooBusyException: The HTTP service located at http://wlgmimsynprod01:59990/IdentityBroker/ChangesAvailable.svc is unavailable. This could be because the service is too busy or because no endpoint was found listening at the specified address. Please ensure that the address is correct and try accessing the service again later. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---

Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
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.Product.EventBroker.IdentityBrokerChanges.IChangesAvailableCollector.ChangesAvailable(Guid adapterId)
at Unify.Product.EventBroker.IdentityBroker41ChangesCommunicator.ChangesAvailable(Guid adapterId)
at Unify.Product.EventBroker.IdentityBroker41ChangesPlugIn.Check()
at Unify.Product.EventBroker.OperationListExecutorBase.RunCheck(ICheckOperationFactoryInformation checkOperation)


Thank you


Answer
anonymous 8 years ago

No response from Aneesh.

0
Answered

MIM error code 0x8023063D

Tomasz Zukowski 8 years ago updated by Bob Bradley 7 years ago 11 1 duplicate

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

Answer
anonymous 8 years ago

Hi Tom,

That is the error code being returned by MIM (0x8023063D). Look at what has changed environmentally, for example any recent MIM upgrades. Test the upgrade in another environment. You may need to raise a support call with Microsoft.

Thanks.

PS. I moved this to the forum - we don't use tickets where it can be avoided.

0
Answered

MIM MA and Run Profile guids not resolving in console

Bob Bradley 8 years ago updated by anonymous 8 years ago 6

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

Answer
anonymous 8 years ago

It seems like it was a permissions error (service account was changed).

0
Not a bug

Identity Broker v5 not listed when creating the agent in EB 3.2.1 #3

Carol Wapshere 8 years ago updated by anonymous 8 years ago 9

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.

Answer
anonymous 8 years ago

Hi Carol,

Note that in your Unify.Service.Event.exe.config file, the security element of the binding element is set to

<security mode="None">
  <transport clientCredentialType="None" proxyCredentialType="None"
      realm="" />
  <message clientCredentialType="UserName" algorithmSuite="Default" />
</security>

but in your Unify.Service.Connect.exe.config file, it is set to

<security mode="TransportCredentialOnly"><transport clientCredentialType="Windows"/></security>

You will need to update one or the other to match. I would suggest changing the Event Broker configuration to match Identity Broker.

0
Not a bug

UNIFY MIM Event Broker Memory leak on IE8

Alan Schmarr 8 years ago updated by anonymous 8 years ago 5

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/

Answer
anonymous 8 years ago

No response. Minimum browser requirements also increased.

0
Published

PowerShell operation or Workflow script fails with incorrect ExecutionPolicy setting

Beau Harrison (Senior Product Software Engineer) 8 years ago updated by anonymous 8 years ago 1

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