Hello community
After a hasty cluster migration from old to new vCenter server, I was able to get our vCAC 5.2 setup stabilized enough to provide virtual machines again.
However, when the VMs (pre-existing as well as newly created) reach expiration date, the stacktrace below fills the logs.
Apparently, something deep down in vCACs integration logic with Windows Workflow Foundation broke.
? Is there a DB table mapping endpoints or resources to WWF queues?
? How do I debug vCAC issues related to WWF?
Message:
Error processing lease changes Event Queue operation failed with MessageQueueErrorCode QueueNotFound for queue 'ForceExpire'.
Stacktrace:
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) at DynamicOps.VMPS.Service.VirtualMachineService.FireVirtualMachineEvent(Guid virtualMachineID, String eventName, Object data, Boolean synchronous) at DynamicOps.VMPS.Service.VirtualMachineService.FireVirtualMachineEvent(Guid virtualMachineID, String eventName, Object data) at DynamicOps.VMPS.Service.VirtualMachineObserver.ProcessLeaseCallback(Object state)