I have created a new XenDesktop 7.6 site in a new VPC and am trying to stand up new catalogs. The process is failing. It never spins up the Citrix.Volumeworker Instance.
It creates the Preparation VM and the XenDesktop Temp Instance. It also creates a VolumeWorker AMI. But never creates the VolumeWorker Instance in the New VPC.
If I create a Catalog in the old site in the previous VPC it works. I have compared the VolumeWorker AMI and they appear the same. The both have the tag
and have the same owner etc.
I have edited the AWS security group rules to allow All traffic between the DDC Security Group and the VDI security group.
The error I am receiving in Studio on the failed catalog creation is
any ideas? I am getting ready to capture scout logs as the next step.
Start Date: Thursday, October 22, 2015
Start Time: 9:12 AM
Finish Date: Thursday, October 22, 2015
Finish Time: 9:25 AM
Master image: XDHyp:\HostingUnits\XXXXXXX.template
Requested machine count: 10
AD account action: Create accounts
Successful accounts: 0
Successful machines: 0
A volume service instance could not be launched in your cloud connection. In Studio, select Hosting in the left pane and then select the cloud connection. Click Test Connection in the Actions pane. The test results should provide additional information.
at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.CheckForTerminatingError(SdkProvisioningSchemeAction sdkProvisioningSchemeAction)
at Citrix.Console.PowerShellSdk.ProvisioningSchemeService.BackgroundTasks.ProvisioningSchemeTask.WaitForProvisioningSchemeActionCompletion(Guid taskId, Action`1 actionResultsObtained)
DesktopStudio_ErrorId : UnknownError
ErrorCategory : NotSpecified
ErrorID : NoDiskContentTransferService
TaskErrorInformation : Terminated
InternalErrorMessage : No facility available for disk upload.
This e-mail and its attachments are confidential and solely for the intended addressee(s). Do not share or use them without Common Securitization Solutions’ approval. If received in error, contact the sender and delete them.