XenApp 7.9 MCS Failing to create machine Catalog in AWS

[Lee Murphy]

Hi Everyone

 

I have been trying to set up an environment in AWS and I am getting this error when trying to create Machine Catalogue

 

No facility available for disk upload. No facility available for disk upload. Unable to create any functioning volume service VMs.

 

References in google from these forums indicate it might be permissions but I have been testing using the permissions suggested by Citrix here: http://support.citrix.com/article/CTX140429

 

The only thing I can see that is possibly related is that during the build process I see in Cloudtrail that it creates a VM named XenDesktop Temp in the Default VPC. The Default VPC is not routed in the internal network for the environment and its not a VPC to be used. Could this be causing the creation to break? I dont see any failures in the AWS Logs (It creates buckets and instances OK but then nothing until it starts destroying them to undo its work).

 

Below is the XenDesktop Output from Studio (Sanitised to remove private domain information)

 

Any advice?

 

-----

 

 

Error Id: XDDS:2367399E

 

Exception:

    Citrix.Console.Models.Exceptions.ProvisioningTaskException 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)

       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 : ProvisioningTaskError

    ErrorCategory : NotSpecified

    ErrorID : NoDiskContentTransferService

    TaskErrorInformation : Terminated

    InternalErrorMessage : No facility available for disk upload. No facility available for disk upload. Unable to create any functioning volume service VMs.

    DesktopStudio_PowerShellHistory : Create Machine Catalog 'Test 2B'

    9/1/2016 12:53:17 PM

    

    Get-LogSite  -AdminAddress "ddc01.xxxxx.local:80"

    Start-LogHighLevelOperation  -AdminAddress "ddc01.xxxxx.local:80" -Source "Studio" -StartTime "9/1/2016 2:21:36 AM" -Text "Create Machine Catalog `'Test 2B`'"

    New-BrokerCatalog  -AdminAddress "ddc01.xxxxx.local:80" -AllocationType "Random" -IsRemotePC $False -LoggingId "09827737-a75a-4075-afb2-ec4ad77dccb7" -MinimumFunctionalLevel "L7_9" -Name "Test 2B" -PersistUserChanges "Discard" -ProvisioningType "MCS" -Scope @() -SessionSupport "MultiSession" -ZoneUid "cad2d3dd-196f-4dcc-8af9-62992737b99c"

    New-AcctIdentityPool  -AdminAddress "ddc01.xxxxx.local:80" -AllowUnicode -Domain "xxxxx.local" -IdentityPoolName "Test 2B" -LoggingId "09827737-a75a-4075-afb2-ec4ad77dccb7" -NamingScheme "CTXPSH0##" -NamingSchemeType "Numeric" -OU "OU=Production,OU=Citrix Workers,OU=Citrix XenDesktop7,DC=xxxxx,DC=local" -Scope @()

    Set-BrokerCatalogMetadata  -AdminAddress "ddc01.xxxxx.local:80" -CatalogId 5 -LoggingId "09827737-a75a-4075-afb2-ec4ad77dccb7" -Name "Citrix_DesktopStudio_IdentityPoolUid" -Value "16ee0f2f-8fc7-41d0-bf14-5215b331b4a4"

    Test-ProvSchemeNameAvailable  -AdminAddress "ddc02.xxxxx.local:80" -ProvisioningSchemeName @("Test 2B")

    New-ProvScheme  -AdminAddress "ddc02.xxxxx.local:80" -CleanOnBoot -HostingUnitName "Citrix-AP-Southeast-2c" -IdentityPoolName "Test 2B" -LoggingId "09827737-a75a-4075-afb2-ec4ad77dccb7" -MasterImageVM "XDHyp:\HostingUnits\Citrix-AP-Southeast-2c\CitrixWorker_v1 (ami-25f3c546).template" -NetworkMapping @{"0"="XDHyp:\HostingUnits\Citrix-AP-Southeast-2c\\ap-southeast-2c.availabilityzone\10.168.144.0``/24 (vpc-6f53510a).network"} -ProvisioningSchemeName "Test 2B" -RunAsynchronously -Scope @() -SecurityGroup @("XDHyp:\HostingUnits\Citrix-AP-Southeast-2c\RefactorCitrixVPC-DomainMemberSG-1609UHE1B97XR.securitygroup","XDHyp:\HostingUnits\Citrix-AP-Southeast-2c\RefactorCitrixVPC-WorkerSG-I4UCTRENLGGT.securitygroup","XDHyp:\HostingUnits\Citrix-AP-Southeast-2c\SG-PRTG-Monitoring-Core-Prod-Citrix.securitygroup") -ServiceOffering "XDHyp:\HostingUnits\Citrix-AP-Southeast-2c\M4 Extra Large Instance.serviceoffering"

    Stop-LogHighLevelOperation  -AdminAddress "ddc01.xxxxx.local:80" -EndTime "9/1/2016 2:53:17 AM" -HighLevelOperationId "09827737-a75a-4075-afb2-ec4ad77dccb7" -IsSuccessful $False

    

    

 

 

[Paul Howard]

Hello, Lee.

 

You are correct that the default VPC will be used for the "XenDesktop Temp" instance. This is because this instance needs to download a Citrix software package from S3, and the default VPC is pre-configured by Amazon with a default subnet and security group that will allow straightforward access to the S3 service, which is why it is briefly used. The fact that it doesn't route to any of your other infrastructure should not matter, provided that it still has its default subnet and can see S3. Has there been any manual reconfiguration within the default VPC, or is it still in the original state as pre-configured by Amazon?

 

What are you observing with the "XenDesktop Temp" instance? It should run for a few minutes and then stop, after which a new AMI should be created, followed by a further instance with a name such as "Citrix.VolumeWorker.xxxxx". Are you observing any of this, or is the process failing before that? If the "XenDesktop Temp" instance runs for a very long period (eg. around 30 minutes) followed by a failure, then it suggests that it is not able to reach the S3 URL that it needs to download the software package. The simplest solution in this case would be to request AWS support to re-create your default VPC for you.

 

Thanks,

Paul.

[Michael Quicho1709156825]

Hello, Lee.

 

You are correct that the default VPC will be used for the "XenDesktop Temp" instance. This is because this instance needs to download a Citrix software package from S3, and the default VPC is pre-configured by Amazon with a default subnet and security group that will allow straightforward access to the S3 service, which is why it is briefly used. The fact that it doesn't route to any of your other infrastructure should not matter, provided that it still has its default subnet and can see S3. Has there been any manual reconfiguration within the default VPC, or is it still in the original state as pre-configured by Amazon?

 

What are you observing with the "XenDesktop Temp" instance? It should run for a few minutes and then stop, after which a new AMI should be created, followed by a further instance with a name such as "Citrix.VolumeWorker.xxxxx". Are you observing any of this, or is the process failing before that? If the "XenDesktop Temp" instance runs for a very long period (eg. around 30 minutes) followed by a failure, then it suggests that it is not able to reach the S3 URL that it needs to download the software package. The simplest solution in this case would be to request AWS support to re-create your default VPC for you.

 

Thanks,

Paul.

Hey Paul - 

Would you happen to know why when I click on "Test Resources" or Test Connection" or even "Test Delivery Group" from the actions pane the test tries to launch but just hangs at "Discovering Objects" forever - never discovering anything.

[Kevin Patrick1709160902]

My client will not allow a default VPC to be specified, there is no other option?  This seems like an easy fix via code change.