Solved

Citrix XD 7.13 / vCenter / Prism - MCS fails to create catalog.


Badge +3
Hi guys,

Deploying full clone VDI on XD 7.13 with Studio linked to the vCenter appliance (5.5 u3e). Prism (5.02) sits behind that on Dell boxes with vSphere environment on top of that. New environment. All storage containers/nodes/etc have unique names.

We don't have an issue deploying targets in vCenter manually. We have all the XD infrastructure components running without issue. If we create a new MCS catalog, the VMDKs get copied during the , but right after the copy of the base disk to the data store, the MCS wizard fails.

Error Id: XDDS:0DAA3833
Exception:Citrix.Console.Models.Exceptions.ProvisioningTaskException An error occurred while preparing the image.at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.StartProvisioningAction()at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeCreationTask.RunTask()at Citrix.Console.PowerShellSdk.BackgroundTaskService.BackgroundTask.Task.Run()DesktopStudio_ErrorId : ProvisioningTaskErrorErrorCategory : NotSpecifiedErrorID : FailedToCreateImagePreparationVmTaskErrorInformation : TerminatedInternalErrorMessage : No permission to upload disk, check role permissions


Now "No permission to upload disk, check role permissions" would point to the vCenter service account right? Well, the service account has full admin rights...cannot give the account any additional rights. Again, we're connecting to vCenter sits on top of Prism...but we're kind of scratching our heads here. Any ideas?
icon

Best answer by cdoran 12 May 2017, 19:25

Appeared the permissions for the svc acct needed to be higher than at the cluster level...had to do apply them at the data center level in vCenter to get MCS to work.

View original

3 replies

Badge +3
Appeared the permissions for the svc acct needed to be higher than at the cluster level...had to do apply them at the data center level in vCenter to get MCS to work.
Badge +4
This issue usually happens in hyper-v where the solution is to delete the machine catalog and recreate the machine catalog.
Userlevel 7
Badge +35
Thanks for tagging the 'Accept as Solution' - and good to hear that got it working!

Reply