MCS catalog update failure - Error - Machine <MasterImageVM> is not found
Terminating Error:
An error occurred while publishing the image.
Stack Trace:
at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.ThrowOnTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)
at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)
at Citrix.Orchestration.Base.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.PublishProvisioningSchemeImageTask.RunTask()
at Citrix.Orchestration.Base.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()
DesktopStudio_ErrorId : ProvisioningTaskError
ErrorCategory : NotSpecified
ErrorID : Finished
TaskErrorInformation : Terminated
InternalErrorMessage : Machine <MasterImageVM> is not found
Restart “Citrix Machine Creation Service” on all DDCs to trigger the Machine Creation Service(MCS) inventory tree rebuilding.
VM info is not in Machine Creation Service(MCS) inventory tree with unexpected reason.
When the hypervisor connection is created for the first time, MCS requests to populate the inventory tree.
It does so by getting all the VM details in virtual center and storing it in the Tree-Info node. MCS also spins up another lifecycle thread which listens for updates from VMWare.
This thread keeps tracks of the events received from VMWare about any VM getting added or deleted on the virtual center. After receiving the event, MCS updates its inventory tree to the latest accordingly.