7.3

Table Of Contents
n
Troubleshooting vRealize Orchestrator Workows That Do Not Start on page 42
You congure a workow subscription to run a custom workow when the event message is received,
but the workow does not run.
n
Troubleshooting Provisioning Requests That Take Too Much Time on page 42
An IaaS machine take ten or more hours to provision.
n
Troubleshooting a vRealize Orchestrator Workow That Does Not Run for an Approval Request on
page 43
You congured a pre-approval or post-approval workow subscription to run a vRealize Orchestrator
workow. The workow does not run when a machine that matches the dened criteria is requested
in the service catalog.
n
Troubleshooting a Rejected Approval Request That Should Be Approved on page 43
You congure a pre-approval or post-approval workow subscription that runs the specied
vRealize Orchestrator workow, but the request is rejected when you know that it was approved.
n
Troubleshooting a Rejected Approval Request on page 43
You congure a pre-approval or post-approval workow subscription that runs the specied
vRealize Orchestrator workow, but the request is unexpectedly rejected.
Troubleshooting vRealize Orchestrator Workflows That Do Not Start
You congure a workow subscription to run a custom workow when the event message is received, but
the workow does not run.
Solution
1 Verify that you published the workow subscription.
2 Verify that the workow subscription conditions are congured correctly.
3 Verify that the vRealize Orchestrator server has the specied workow.
Troubleshooting Provisioning Requests That Take Too Much Time
An IaaS machine take ten or more hours to provision.
Cause
If you congured a workow subscription to trigger on a provisioning state, you might have two instances
of the manager service running in your environment.
Solution
u
Verify that you have only one instance of the manager services is active. If both are on you will also see
errors like this in the logs.
If you have more than one, an error similar to the following error message appears in the manager
services logs.
[EventBrokerService] Failed resuming workflow b6e9276a-f20f-40f1-99ad-6d9524560cc2 on queue
3679fa71-ac2a-42d5-8626-f98ea096f0d3.
System.Workflow.Runtime.QueueException: Event Queue operation failed with
MessageQueueErrorCode QueueNotFound for queue '3679fa71-ac2a-42d5-8626-f98ea096f0d3'.
at System.Workflow.Runtime.WorkflowQueuingService.EnqueueEvent(IComparable queueName,
Object item)
at System.Workflow.Runtime.WorkflowExecutor.EnqueueItem(IComparable queueName, Object
item, IPendingWork pendingWork, Object workItem)
at System.Workflow.Runtime.WorkflowInstance.EnqueueItem(IComparable queueName, Object
item, IPendingWork pendingWork, Object workItem)
Life Cycle Extensibility
42 VMware, Inc.