- UNIFYNow Forum
-
Questions
Event Broker workflow throws [workflow failed validation] exception
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 ...
Data Workflow has no activity.png
Customer support service by UserEcho
Matthew, can you please look at this first thing this morning.
Bob, just reminding you that it's up to our team to decide what version issues will be fixed in - with less than 8 work hours to go before release there's not going to be an awful lot we can do about most things.
Bob,
Unsure how this happened, but for some reason your auto pilot workflow is missing the changes activity.
As an aside, there was an issue in the Activity Information Configuration of the activity in that it was still referencing the old version number, although a new version of the Portal Workflow had been installed. I've changed this in the activity configuration. There is also a minor bug in the PowerShell script that I fixed yesterday that I have updated in the directory (again to do with the version number, although it doesn't look like the script was re-run so this wasn't an issue).
I suspect the above is what removed the activity from the workflow, but can't confirm that. If this is the case, can you please let me know? The error seems to just be a FIM Portal error saying that there's nothing in the workflow. Depending on how this happened, I may add a troubleshooting item to the documentation.
Assigned to Bob, see above comment
The workflow definitions had lost their activity configuration due to the upgrade. Once these were recreated the exceptions stopped being thrown and normal processing resumed. Thanks.
No more work required