We have a AD DIDS operation in event broker

On dashboard it says there is an error

But in verbose log there is no error

20150729,00:09:16,UNIFY FIM Event Broker,Operation List Executor,Information,Operation list MonashAD - DIDS started,Verbose
20150729,00:09:17,UNIFY FIM Event Broker,Operation List Executor,Information,Completed Management Agent: MonashAD - Run Profile: DIDS operation with id f0986d76-16df-4996-93e7-cc1dc8ba0326 in operation list MonashAD - DIDS,Verbose
20150729,00:09:17,UNIFY FIM Event Broker,Operation List Executor,Information,Completed Active Directory Commit operation with id 4f484b80-25ca-453c-9940-541a6b84d376 in operation list MonashAD - DIDS,Verbose
20150729,00:09:17,UNIFY FIM Event Broker,Operation List Executor,Information,Operation list MonashAD - DIDS finished,Verbose

Looks like a commit error

My question is

1) For the account being used for AD Listener, what rights does it need? (https://unifysolutions.jira.com/wiki/display/EB32/Active+Directory)

2) What could be failing for AD Commit - Log says successful.

I am experiencing the following error if I click the 'Select Management Agent' link in the breadcrumb while editing an existing Operation in an operation list.

Server Error in '/' Application.
--------------------------------------------------------------------------------

The resource cannot be found. 
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly. 

Requested URL: /Operation/CreateRunProfileOperationSelectManagementAgent


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272 

Reproduction steps are:
1 Navigate to the Operations Page
2 Open an existing Operation List with at least one configured Operation
3 If required, stop the Operation List
4 Select an operation of type 'Run Profile' (Runs a FIM MA) and choose 'Edit Operation'
5 On the 'Select Management Agent' page do not change the Management Agent. Hit 'Update'.
6 On the second 'Select Maangement Agent' page (where run profile information can be supplied), at the breadcrumb near the top of the page click 'Select Management Agent'. See attached screnshot

Expected Outcome: A page loads

Actual Outcome: 404 Error

Not: I havent tested this when creating a new management agent operation from scratch. Since a similar/identical page loads, the error may or may not occur there also.

In Event Broker 2.x, connections to outside systems were handled in two ways:

• The details of a single FIM database instance were saved in configuration, and Event Broker had to be installed on the same machine due to no WMI configuration flexibility.
• The details to other systems (IDB, AD, SQL Server, etc) were stored separately in operation configurations. Details were often duplicated across many operations, configured differently for each of them and sensitive information (eg passwords) stored in plain text.

Event Broker v3.0 should solve this problem by using "Agents". An agent should contain all the information required to connect to a particular type of system in a secure manner. PlugIns can then request instances of an agent and use this information to connect to the target system. For example:

• A FIM Agent should contain the database and WMI details necessary to connect to an instance of FIM.
• An Identity Broker Agent should contain the location of the WCF endpoints and any credentials necessary to access them.

A bonus of this approach is that the Event Broker service can now be installed on any machine and even multi-target FIM instances.

In the logs for an outgoing export in Event Broker(version 2.2) to Active Directory there are some errors appearing as in the attached screenshot. There are exports being run so I'm not sure if this is a problem but I can't find any further information on the error, in event viewer or in Jira. I'm doing a health check on the Virgin solution so just investigating if this could be an issue.

It would be great for it to be able to schedule in T-SQL scripts when nothing else is running & delay run profiles when the T-SQL scripts are running. As a stretch target, recognising when various FIM & UNIFY dbs require reindexing & run appropriate scripts would be awesome.

Presently operation lists appear to be ordered according to the time they were created. This should be changed to alphabetical order to provide a more intuitive interface for the administrator.

I'm migrating an EvB2 config to EvB3. In EvB2 there's a command shell wrapper that calls the doconvert.exe plugin. I know I have access to powershell scripting from EvB3 but I'm not quite sure what doconvert.exe does. Converts xml to w7 logging or something? Is there an equivalent version of this for EvB3 and/or how else should I go about replicating the actions it took?

From ENVIRON-26, try and find a more descriptive hint for the Server field.

The current hint says "The full name of the server being connected to". It may have to mention that the non-standard port number should be included. If possible mention that a test tool can help diagnose the correct settings (eg ADSI Edit or LDP.exe).

Where is EventBrokerService.exe.config referred to for creating Identity Broker Agent, https://unifysolutions.jira.com/wiki/display/EB300/Identity+Broker.

The document does not state that I need to create on and file search could not find "EventBrokerService.exe.config" under either "<Program Files>\UNIFY Solutions" or "<Program Files (x86)>\UNIFY Solutions"

The MIIS Toolkit's Clear Run History feature does not seem to be compatible with FIM 2010. As such, the MIIS Clear Run History plugin will not work if it uses this mechanism. There is a version of this tool that comes with the plugin, however, and this should be tested for compatibility with FIM, or should be updated to perform correctly.

In the event that the feature is not compatible, a new mechanism should be instated to clear the run history. Estimate includes this work.