NoDiskContentTransferService Error when creating Machine Catalog

[David Nidoh]

When I go to create a Machine Catalog and spin up a VDA i get the following error, I have also tried everything I could from other forumns... using magnetic storage instead of SSD's, syncing up the times, using different Instance types, rebuilding the default VPC, rebuilding the DDC, rebuilding the VDA.... all with no luck. I have sat on the phone with Amazon AWS tech support for hours as they watch the instances try and spin up and the "XenDesktop Temp" instance always crashes because it cant find the script its trying to execute, and AWS support is unsure where this script is located. Any and all help would be much appreciated!

 

Thanks!

 

 

Error Id: XDDS:07E48AB2

Exception:
    Citrix.Console.Models.Exceptions.ScriptException 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.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 : UnknownError
    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 'CCM Agent At Home'
    10/11/2014 2:07:22 PM
    
    Get-ConfigServiceStatus  -AdminAddress 'xd7ddc.xencloud.net:80'
    Get-LogSite  -AdminAddress 'xd7ddc.xencloud.net:80'
    Start-LogHighLevelOperation  -AdminAddress 'xd7ddc.xencloud.net:80' -Source 'Studio' -StartTime 10/11/2014 6:07:22 PM -Text 'Create Machine Catalog `'CCM Agent At Home`''
    New-BrokerCatalog  -AdminAddress 'xd7ddc.xencloud.net:80' -AllocationType 'Random' -Description 'CCM Agent At Home - Win Serv 2008R2' -IsRemotePC $False -LoggingId ba2bbfc9-74e5-4064-97c7-f769e57aa89d -MinimumFunctionalLevel 'L7' -Name 'CCM Agent At Home' -PersistUserChanges 'Discard' -ProvisioningType 'MCS' -Scope @() -SessionSupport 'MultiSession'
    New-AcctIdentityPool  -AdminAddress 'xd7ddc.xencloud.net:80' -AllowUnicode -Domain 'xencloud.net' -IdentityPoolName 'CCM Agent At Home' -LoggingId ba2bbfc9-74e5-4064-97c7-f769e57aa89d -NamingScheme 'CCMAOH###' -NamingSchemeType 'Numeric' -OU 'CN=Computers,DC=xencloud,DC=net' -Scope @()
    Set-BrokerCatalogMetadata  -AdminAddress 'xd7ddc.xencloud.net:80' -CatalogId 1006 -LoggingId ba2bbfc9-74e5-4064-97c7-f769e57aa89d -Name 'Citrix_DesktopStudio_IdentityPoolUid' -Value 'aa4ef773-2de4-4d48-be14-3b415686f6e6'
    Test-ProvSchemeNameAvailable  -AdminAddress 'xd7ddc.xencloud.net:80' -ProvisioningSchemeName @('CCM Agent At Home')
    New-ProvScheme  -AdminAddress 'xd7ddc.xencloud.net:80' -CleanOnBoot -HostingUnitName 'AOH Xencloud US-East-1a' -IdentityPoolName 'CCM Agent At Home' -LoggingId ba2bbfc9-74e5-4064-97c7-f769e57aa89d -MasterImageVM 'XDHyp:\HostingUnits\AOH Xencloud US-East-1a\CCM_Master_beta1 (ami-f0308f98).template' -NetworkMapping @{'0'='XDHyp:\HostingUnits\AOH Xencloud US-East-1a\\us-east-1a.availabilityzone\10.0.1.0``/24 (vpc-31dd7054).network'} -ProvisioningSchemeName 'CCM Agent At Home' -RunAsynchronously -Scope @() -SecurityGroup @('XDHyp:\HostingUnits\AOH Xencloud US-East-1a\XEN75-DomainControllerSG-5920IAKZ9YZ5.securitygroup','XDHyp:\HostingUnits\AOH Xencloud US-East-1a\XEN75-PrivateSecurityGroup-4ZLJ9C01N8G8.securitygroup') -ServiceOffering 'XDHyp:\HostingUnits\AOH Xencloud US-East-1a\High-CPU Extra Large Instance.serviceoffering'
    
    
 

 

[Paul Howard]

Hi, David.

 

This is an error that can have a number of causes. I would like, if possible, to gather some logging data from your site.

 

Could you please run the Citrix Scout utility in your site, and press the "Start CDF Trace" button to begin collecting diagnostic traces from your delivery controller? Run the trace for the complete attempt to provision the catalog, up to the point where you observe the error report in Studio. If you then choose "Collect & Upload" from within Scout, you will be given the opportunity to save a ZIP file to disk. Could you email that ZIP file privately to me? I am paul dot howard at citrix dot com. I'll happily take a look over that for you.

 

Thanks,

Paul.

[Richard Todd1709152533]

Hi David and Paul -

I'm seeing this exact same issue.  I've logged a case with Citrix but no-one seems to be able to get to the bottom of it.

 

My XenDesktop 7.5 on AWS has been working well for the last couple of months, then this occurs out of the blue.  Any help to get this sorted quickly will be greatly appreciated.

 

I've uploaded CTF / Scout captures to TAAS for my case (64245853). 

 

Cheers,

 

Richard.

[Matt Hinchy1709153672]

I am also seeing the same issue - running XenApp 7.6. Has there been any movement on getting this sorted?

[Matt Hinchy1709153672]

To clarify - I have a clean master image, and have followed all of the suggestions - but cannot create a catalogue and am very tempted to just spin up the machines I need and avoid the MCS integration for the time being. My services are in AWS and I have checked and rechecked the configuration of all of the components, scout says everything is ok

[Omied Willis]

I've been struggling with this same issue for several weeks now. What was the final resolution?

[sheshadri srinivasaiah1709156365]

if anyone still having issue then follow below steps.

 

We need to make sure that we are able to reach external from the private network where the master image belongs to. One is to add Ingress rule to security group( which will take care of outbound rules as well) and second if its in private network add a nat gateway to reach external network.