I'm upgrading Identity Broker to UnifyBroker for a customer and the service isn't starting. No errors show up in Event Viewer and after attempting to start the service, the service status sits at "Starting" and nothing else can be done with it until a restart. There's nothing in the Identity Broker logs folder. Any clues as to where to look next?

I'm getting this error when I try to create an MA connecting to UNIFYBroker. I'm using MIM SP1 v4.4.1237.0.

I've just installed UnifyBroker v5.3.1 and then Identity Broker for FIM v5.0.4. I created SQL connectors and an adapter and created the LDAP User. I changed the port it uses to 8888. I copied the .dll into the FIM Extensions directory, selected extensible connectivity 2.0 and selected the .dll and the refresh interfaces works but on the next page, trying to auth with IdB I get the above error. There's nothing in event viewer. I get the same error if I enter the wrong credentials but a different error if I enter the wrong port. I also tried 127.0.0.1 instead of localhost and got the same error. I also tried port 59991 in case I should be connecting to the web service and got the same error.

We are currently working with a datasource (via Broker to MIM) which only shows active users - there is no end-date field for us to trigger events on termination.

Is there a way to capture the record delete event in Broker and create an action based on that (i.e., write some field about the record to a log file, etc..)?

Thanks.

In a lab I ran an in-place upgrade from IdB4 to Broker5. The first time I ran the installer, it failed saying that it couldn't find the web.config xml file. I checked and the file wasn't there at that point in time. The installer rolled back, removing the v4 installation but leaving the configuration. I ran the installer again and it ran successfully but when I navigated to the identity broker page, I got the standard custom errors warning so I changed it to remote only and got the following error page. I haven't done anything since. What would you recommend I do next? Try a re-install or mess around with .dlls or what? (I changed the port to 8888 when it was v4 and that persisted into 5)

Hi Is there documentation for version 4 somewhere? I'm trying to create an MA that connects to Identity Broker v4.1.4. I've installed installed Identity Broker for FIM  v4 and put the .dll it copies into the extensions folder of FIM but I don't know what to do next since the v5 doco using an ecma 2 connector. I thought that in v4, going to the adapter settings you could generate an xMA from there but the option doesn't appear to be there. How do I create an Identity Broker MA?

Hi,

Can I get the installation for broker 4.1.1. I want it for two things, first is to lab an upgrade if I get a chance, the second thing is because the PS process for an IdB upgrade is to run 4 and 5 in parallel so that we can compare an old and new MA. To run in parallel, I'll need to install 4 on another server while the original server is upgraded. The v4 instance will then be decommissioned once the testing has been done.

Is this a custom connector? I can't see it in the KB. What's the situation if it is a custom connector? It's installed with a v4IdB currently but I don't have the connector installation. Would further development be required for the connector to work with 5?

I have a couple of questions around an upgrade from idb4 to UnifyNow

• How long should it take?
• It's not in-place is it?
• What would be the step-by-step for migrating config? ie. I can't look at the config if I've already uninstalled 4
• What's the process for migrating between environments? Do I just copy the extensibility folder and then update connection strings/credentials in the browser?
• Why is SQL server 2014 recommended?

Hi Guys,

When clicking on the entity count to do an entity search (Both Connector and Adapter). I can't seem to perform an entity search. I get the following error: 

Error

System.AggregateException: One or more errors occurred. ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Unify.Connect.Web.IdentityBrokerEntitySearchController.CurrentEntities(EntityRetrievalInformation`1 information)
at Unify.Connect.Web.IdentityBrokerEntitySearchController.<EntityData>d__35.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at lambda_method(Closure , Task )
at System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass34.<BeginInvokeAsynchronousActionMethod>b__33(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3c()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass45.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3e()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass30.<BeginInvokeActionMethodWithFilters>b__2f(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass1e.<>c__DisplayClass28.<BeginInvokeAction>b__19()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass1e.<BeginInvokeAction>b__1b(IAsyncResult asyncResult)
---> (Inner Exception #0) System.Threading.Tasks.TaskCanceledException: A task was canceled.<---

 DataTables Error

This error hasn't always occurred, however recently the error is appearing for connectors/adapters with high entity counts (lower entity count connectors/adapters seem to be fine).

Current IDB version: v5.3.1

Troubleshooting so far:

* Restart the UNIFYBroker Service

* Rebuilt all indexes on the UNIFYBroker Database

Let me know if you need more information.

Thank

HSF are upgrading their C21 instance over the weekend so I just wanted to check if there's any known issues with upgrades and the broker c21 connector. They say it's an Engine update, going to version 8.16.5. They're using Identity Broker version 4. Any known issues?