I am not sure of the current status of the parent issue, but the Event Broker workflows are now failing with the following exception despite the target operation being active and the scheduler being in a running state:

Log Name: Forefront Identity Manager
Source: Microsoft.ResourceManagement
Date: 28/06/2011 11:09:42 PM
Event ID: 3
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WIN-K10OFJJP0T8.chris21demo.unifysolutions.local
Description:
Microsoft.ResourceManagement: Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException: Unable to create new WorkflowInstance for WorkflowDefinition 'f359b107-8fbd-4dd2-a506-1c9210f96dd5'. ---> System.Workflow.ComponentModel.Compiler.WorkflowValidationFailedException: The workflow failed validation.
at System.Workflow.Runtime.Hosting.DefaultWorkflowLoaderService.CreateInstance(XmlReader workflowDefinitionReader, XmlReader rulesReader)
at System.Workflow.Runtime.WorkflowDefinitionDispenser.LoadRootActivity(String xomlText, String rulesText, Byte[] xomlHashCode, Boolean createDefinition, Boolean initForRuntime)
at System.Workflow.Runtime.WorkflowDefinitionDispenser.MruCache.GetOrGenerateDefinition(Type type, String xomlText, String rulesText, Byte[] md5Codes, Boolean initForRuntime, Boolean& exist)
at System.Workflow.Runtime.WorkflowDefinitionDispenser.GetRootActivity(String xomlText, String rulesText, Boolean createNew, Boolean initForRuntime)
at System.Workflow.Runtime.WorkflowRuntime.InitializeExecutor(Guid instanceId, CreationContext context, WorkflowExecutor executor, WorkflowInstance workflowInstance)
at System.Workflow.Runtime.WorkflowRuntime.Load(Guid key, CreationContext context, WorkflowInstance workflowInstance)
at System.Workflow.Runtime.WorkflowRuntime.GetWorkflowExecutor(Guid instanceId, CreationContext context)
at System.Workflow.Runtime.WorkflowRuntime.InternalCreateWorkflow(CreationContext context, Guid instanceId)
at System.Workflow.Runtime.WorkflowRuntime.CreateWorkflow(XmlReader workflowDefinitionReader, XmlReader rulesReader, Dictionary`2 namedArgumentValues, Guid instanceId)
at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters)
— End of inner exception stack trace —
at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception)
at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft.ResourceManagement" />
<EventID Qualifiers="0">3</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-06-28T13:09:42.000000000Z" />
<EventRecordID>31774</EventRecordID>
<Channel>Forefront Identity Manager</Channel>
<Computer>WIN-K10OFJJP0T8.chris21demo.unifysolutions.local</Computer>
<Security />
</System>
<EventData>
<Data>Microsoft.ResourceManagement: Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManagerException: Unable to create new WorkflowInstance for WorkflowDefinition 'f359b107-8fbd-4dd2-a506-1c9210f96dd5'. ---> System.Workflow.ComponentModel.Compiler.WorkflowValidationFailedException: The workflow failed validation.
at System.Workflow.Runtime.Hosting.DefaultWorkflowLoaderService.CreateInstance(XmlReader workflowDefinitionReader, XmlReader rulesReader)
at System.Workflow.Runtime.WorkflowDefinitionDispenser.LoadRootActivity(String xomlText, String rulesText, Byte[] xomlHashCode, Boolean createDefinition, Boolean initForRuntime)
at System.Workflow.Runtime.WorkflowDefinitionDispenser.MruCache.GetOrGenerateDefinition(Type type, String xomlText, String rulesText, Byte[] md5Codes, Boolean initForRuntime, Boolean& exist)
at System.Workflow.Runtime.WorkflowDefinitionDispenser.GetRootActivity(String xomlText, String rulesText, Boolean createNew, Boolean initForRuntime)
at System.Workflow.Runtime.WorkflowRuntime.InitializeExecutor(Guid instanceId, CreationContext context, WorkflowExecutor executor, WorkflowInstance workflowInstance)
at System.Workflow.Runtime.WorkflowRuntime.Load(Guid key, CreationContext context, WorkflowInstance workflowInstance)
at System.Workflow.Runtime.WorkflowRuntime.GetWorkflowExecutor(Guid instanceId, CreationContext context)
at System.Workflow.Runtime.WorkflowRuntime.InternalCreateWorkflow(CreationContext context, Guid instanceId)
at System.Workflow.Runtime.WorkflowRuntime.CreateWorkflow(XmlReader workflowDefinitionReader, XmlReader rulesReader, Dictionary`2 namedArgumentValues, Guid instanceId)
at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters)
— End of inner exception stack trace —
at Microsoft.ResourceManagement.Utilities.ExceptionManager.ThrowException(Exception exception)
at Microsoft.ResourceManagement.Workflow.Hosting.WorkflowManager.StartWorkflowInstance(Guid workflowInstanceIdentifier, KeyValuePair`2[] additionalParameters)</Data>
</EventData>
</Event>

Note that there are pending exports to both FIM and AD, but there are no corresponding outgoing operations executing the necessary FIM run profiles.

I have logged in tonight trying to complete some aspects of workflow development for the demo, but I've encountered what appears to be an unstable state. Consequently I'm calling it quits on tonights development window ...

See IDB-206

We should examine whether it's worth implementing attribute-based routing.

As required but missed in IDB-437, the terminology for "Queue On Missed" should be updated to "Queue On Blocked", as well as reflecting this in the documentation.

It may be worth revisiting the Outgoing Pending operation terminology, for whether the term "Export" should be included.

The autoconfigure for FIM job should be run on a separate thread so as to not block the rest of EventBroker.

The copyright for v3.0.2 is out of date and should read 2012.

Hi Guys,

We're having issues with EVB onsite at APRA today.

It's installed in the self hosted configuration, with the following current config:

applicationPath="..\Web"
hostname="sydprdfim02evb"
port="8081"

Despite multiple attempts at different hostnames, the interface remains hosted at http://localhost:8081

Am i missing something?

Time Stamp in log is showing 01:00 also for 13:00. How can I change that? I would like to have 1PM displayed as 13:00.

The About page has a link to PUBEB, and is the most likely landing point on our site for a client (or PS staff!) looking for the latest downloads for EvB. A link on the About page to the SUBEB site and/or a link from PUBEB to SUBEB would be very helpful indeed. It all makes sense when explained to you or you work it out yourself, but navigation is still less than intuitive for the unfamilliar.

For the next minor version, the installer package names should be revisited to ensure that they are in line with the branding objectives of UNIFY and the trademarked names for the product.