Unable to create machine catalogue in AWS Error: “You do not have a host with a matching configuration and sufficient capacity”

You may see following error when you attempt to create machine catalog in AWS:

“You do not have a host with a matching configuration and sufficient capacity” “Timed out waiting for: Creating machine ‘Preparation – ABC-TEST-VDI-XY – XXxxxxxxxxxxxxxxxxxxxxx’ with pre-existing ENIs: eni-XXXXXXXXXXXXXXXXX”

The above error is seen while using Dedicated VPC and Dedicated Host on AWS

Later, you may see following error on allocating a Dedicated Host in AWS

Name: MC_CreateMachineCatalogInitialzation

An error occurred. Contact Citrix Technical Support, and provide the transaction ID above.

Exception: DesktopStudio_ErrorId : ProvisioningTaskError ErrorCategory : NotSpecified ErrorID : NoDiskContentTransferService TaskErrorInformation : Terminated InternalErrorMessage : No facility available for disk upload. Unable to create any functioning volume service VMs. Timed out waiting for: Creating machine ‘XenDesktop Temp’ with pre-existing ENIs: eni-xxxxxxxxxxxxxxxxx No facility available for disk upload. Unable to create any functioning volume service VMs. Timed out waiting for: Creating machine ‘XenDesktop Temp’ with pre-existing ENIs: eni-xxxxxxxxxxxxxxxx

Related:

  • No Related Posts

Citrix Cloud: Unable to create/update machine catalog with the error “No facility available for disk upload. Unable to create any functioning volume service VMs. The given key was not present in the dictionary”

In rare conditions, you may be unable to create or update a machine catalog hosted on AWS. On analyzing the CDF traces, you may find an snippet similar to the one below.

73564371 0 12:41.4 53848 3220 1 RemoteHCLServerLog 1 Error [AWS]: VolumeServiceManager.ClaimSlot: No volume workers created after signalling unmet demand. Assuming dead volume service.

73564372 0 12:41.4 53848 3220 1 RemoteHCLServerLog 1 Error “[AWS]: PluginMachineManager.CreateDiskWithContent: There is no available service for populating the disk ‘prepare-identity’. Details: PluginUtilities.Exceptions.NoDiskContentTransferServiceException: No facility available for disk upload. Unable to create any functioning volume service VMs. The given key was not present in the dictionary. —> PluginUtilities.Exceptions.WrappedPluginException: Unable to create any functioning volume service VMs. The given key was not present in the dictionary. —> PluginUtilities.Exceptions.WrappedPluginException: The given key was not present in the dictionary.

— End of inner exception stack trace —

— End of inner exception stack trace —

at CloudCommon.VolumeService.VolumeServiceManager.WriteDiskDataToVolume(String availabilityZoneId, String targetVmId, String volumeId, IStreamVirtualDisk diskData)

at CloudCommon.CloudPluginBase.PluginMachineManager.CreateDiskWithContent(String vmId, String diskName, Int32 diskIndex, IStreamVirtualDisk diskData, IHypAvailabilityZone zone, IVolumeServiceState volumeServiceState)”

73564374 2 12:41.5 53848 3220 1 RemoteHCLServerLog 1 Error “[AWS]: PluginMachineManager.CreateCompleteVM: Error while attempting to create VM (name=’Preparation – TESTING0MULTISESSION-29THAPRIL – 7qRw1h7ZUEGuD6qljZE47g’, id=’i-05481da2de3c21cd0′). Exception: ‘PluginUtilities.Exceptions.NoDiskContentTransferServiceException: No facility available for disk upload. Unable to create any functioning volume service VMs. The given key was not present in the dictionary. —> PluginUtilities.Exceptions.WrappedPluginException: Unable to create any functioning volume service VMs. The given key was not present in the dictionary. —> PluginUtilities.Exceptions.WrappedPluginException: The given key was not present in the dictionary.

— End of inner exception stack trace —

— End of inner exception stack trace —

at CloudCommon.VolumeService.VolumeServiceManager.WriteDiskDataToVolume(String availabilityZoneId, String targetVmId, String volumeId, IStreamVirtualDisk diskData)

at CloudCommon.CloudPluginBase.PluginMachineManager.CreateDiskWithContent(String vmId, String diskName, Int32 diskIndex, IStreamVirtualDisk diskData, IHypAvailabilityZone zone, IVolumeServiceState volumeServiceState)

at CloudCommon.CloudPluginBase.PluginMachineManager.ProcessDisks(String vmId, Dictionary`2 disks, IHypAvailabilityZone zone, IVolumeServiceState volumeServiceState)

at CloudCommon.CloudPluginBase.PluginMachineManager.CreateCompleteVM(String name, IVMMetadata metadata, String serviceOffering, IList`1 securityGroups, IList`1 disks, IVolumeServiceState volumeServiceState, Boolean enableNetwork, INetworkInterfaceDetails networkInterfaceDetails, IHypAvailabilityZone zone, Boolean dedicatedTenancy, CloudTenancy tenancyType, Boolean tagVms, String customProperties)'”

73564471 0 12:48.3 53848 3220 1 RemoteHCLServerLog 1 Error “CloudRunQueue-4 – caught exception PluginUtilities.Exceptions.NoDiskContentTransferServiceException: No facility available for disk upload. Unable to create any functioning volume service VMs. The given key was not present in the dictionary. —> PluginUtilities.Exceptions.WrappedPluginException: Unable to create any functioning volume service VMs. The given key was not present in the dictionary. —> PluginUtilities.Exceptions.WrappedPluginException: The given key was not present in the dictionary.

— End of inner exception stack trace —

— End of inner exception stack trace —

at CloudCommon.VolumeService.VolumeServiceManager.WriteDiskDataToVolume(String availabilityZoneId, String targetVmId, String volumeId, IStreamVirtualDisk diskData)

at CloudCommon.CloudPluginBase.PluginMachineManager.CreateDiskWithContent(String vmId, String diskName, Int32 diskIndex, IStreamVirtualDisk diskData, IHypAvailabilityZone zone, IVolumeServiceState volumeServiceState)

at CloudCommon.CloudPluginBase.PluginMachineManager.ProcessDisks(String vmId, Dictionary`2 disks, IHypAvailabilityZone zone, IVolumeServiceState volumeServiceState)

at CloudCommon.CloudPluginBase.PluginMachineManager.CreateCompleteVM(String name, IVMMetadata metadata, String serviceOffering, IList`1 securityGroups, IList`1 disks, IVolumeServiceState volumeServiceState, Boolean enableNetwork, INetworkInterfaceDetails networkInterfaceDetails, IHypAvailabilityZone zone, Boolean dedicatedTenancy, CloudTenancy tenancyType, Boolean tagVms, String customProperties)

at CloudCommon.CloudPluginBase.PluginHypervisor.<>c_DisplayClass39_0.<BeginCreateCompleteVM>b_0(PluginMachineManager manager)

at Citrix.HypervisorCommunicationsLibrary.TaskRunItem`2.Run(T manager)

at HypervisorsCommon.HCL.TaskRunner`1.Run()”

Related:

  • No Related Posts

XenDesktop Setup Wizard Failed to Create Target Devices in Hyper-V SCVMM

XenDesktop Setup Wizard Failed to Create Target Devices in Hyper-V SCVMM

Scope:

Get the wizard to create VMs in Hyper-V

Details:

CDF shows:

SCVMM not returning a job ID

SCVMM has no record of the job

Wizard completes without error, but 1 machine fails

verfiying settings:

-Hyper V – on scvmm – posh execution policy – allow unrestricted – no chg

-create VMs manually from template – ok

-template settings – ok

-legacy nic 1st, synthetic nic 2nd

VMs a re-pooled w/ WC drive on template (on local storage)

VMM console installed on all DDCs

Related:

How to create a template for the connector and provisioning application

It is recommended to have a template set in the connector configuration.. This ensures the VMs being created and the published image are based on the same hardware specifications and also prevents issues with the time.


1) Find the Gold Image used to create the base OS Layer or use a vm which is known to be configured as wanted and working properly. Preferably use a vm with the same OS and build.

2) Make a clone of either of the VMs

3) Edit the cloned vm and remove all hard disks

4) Convert the vm to a template

5) Use the template in our connector configuration and as the template to create new VMs with the provisioning software. This is critical for PVS devices to stream properly.

NOTE: Possible issues are wrong NICs in the production desktops, issues with the hypervisor tools and associated components, possible BSOD when accessing a desktop. session.

Related:

Slow Enumeration Of VMs On SCVMM Hypervisor Connections While Adding VMs To Machine Catalog

Observing delay while adding new VMs to machine catalogs when browsing SCVMM hosting connections.

After clicking on browse, it takes more than 15 minutes to expand a SCVMM hypervisor connection to display the host groups.

It can take another 15+ minutes to expand further and see the clusters and the VMs on the clusters.

Issue is not specific to any SCVMM version and can be seen in a large cluster environment.

Related:

SQL Report – CMS8.1 – Add IP address to report.

I need a solution

Hello. This is a query to show user computers  with the Symantec Management Agent.

The SQL query is below, I would like to add a IP address columb to this.

Please can someone assist. Thanks.

SELECT DISTINCT adrp.DisplayName,vms.[Last Start] AS [Last Run],vc.Name,Inv_AeX_AC_Identification.[Hardware Serial Number], vc.[User],adrp.InstallDate,
CASE WHEN vms.[Run Count]>= 1 THEN ‘Yes’ ELSE ‘No’ END usage FROM Vcomputer vc 
LEFT JOIN Inv_AddRemoveProgram adrp ON vc.Guid = adrp._resourceguid
LEFT JOIN vAMMonthlySummary vms ON adrp._resourceguid = vms._resourceguid
  AND vms.[Last Start] = (SELECT max(vms.[Last Start]) FROM vAMMonthlySummary vms WHERE vms._ResourceGuid = vc.Guid)
LEFT JOIN Inv_InstalledSoftware ins ON vms._ResourceGuid = ins._ResourceGuid
LEFT JOIN Inv_AeX_AC_Identification ON vms._ResourceGuid = Inv_AeX_AC_Identification._ResourceGuid
WHERE adrp.DisplayName LIKE ‘AUTODESK%’
ORDER BY vc.Name
 

Thanks

0

1575562199

44

Related:

A hardware change to the client computer has been detected

I need a solution

I’ve gotten more of these email alerts recently.  Not a huge amount, just handful, but I haven’t gotten many or any in the past I think.  I googled a bit but I’m not finding anything interesting.  

For the alerts I’ve gotten recently, three have been on virtual machines.  For my VMs, settings are static, so the VMs don’t change their hardware, MAC address, etc. that I’m aware of.  A few more physical machines popped up with these hardware change alerts.

Any ideas on what they could be?  Or can you point me to the log location (is that in the SEPM manager or the client machine’s windows system event log?)?

0

Related:

Hotfix XS71ECU2020 – For XenServer 7.1 Cumulative Update 2

Who Should Install This Hotfix?

This is a hotfix for customers running XenServer 7.1 Cumulative Update 2.

Note: This hotfix is available only to customers on the Customer Success Services program.

Information About this Hotfix

Component Details
Prerequisite None
Post-update tasks None
Content live patchable** No
Baselines for Live Patch N/A
Revision History

Published on Nov 20, 2019

** Available to Enterprise Customers.

Issues Resolved In This Hotfix

This hotfix resolves the following issues:

  • Sometimes, the storage garbage collection process might run continuously, taking snapshots, coalescing them, deleting the snapshots, and then repeating on an almost permanent basis. This introduces high IOPS load for little benefit.
  • When read caching is enabled it is significantly slower to read from the parent snapshot than from the leaf. This is now fixed for sequential reads.
  • On HA-enabled pools, when a task is initiated after a XenServer host has failed, VMs on the host can be blocked from restarting for many hours. This issue occurs when an in-progress coalesce process is not explicitly aborted after the failure.
  • All VMs on a XenServer host can experience slower read/write performance, during a VM disk copy, and up to 512 seconds after the copy finishes. The degradation of performance is caused by cache memory pressure in dom0 causing all tapdisks to incorrectly enter low memory mode.

    Important: This hotfix disables low memory mode. Therefore, VMs might require more memory to be available in dom0. Before applying this hotfix, you can check whether any of your VMs are running in low memory mode by adding the “Tapdisks in Low Memory Mode” graph to the Performance tab in XenCenter. The number of VMs in low memory mode is shown on this graph. We recommended that you increase dom0 memory to make an additional ~1.4MB per VM available in dom0.

This hotfix also includes the following previously released hotfixes:

Installing the Hotfix

Customers should use either XenCenter or the XenServer Command Line Interface (CLI) to apply this hotfix. When the installation is complete, see the Post-update tasks in the table Information About this Hotfix for information about any post-update tasks you should perform for the update to take effect. As with any software update, back up your data before applying this update. Citrix recommends updating all hosts within a pool sequentially. Upgrading of hosts should be scheduled to minimize the amount of time the pool runs in a “mixed state” where some hosts are upgraded and some are not. Running a mixed pool of updated and non-updated hosts for general operation is not supported.

Note: The attachment to this article is a zip file. It contains the hotfix update package only. Click the following link to download the source code for any modified open source components XS71ECU2020-sources.iso. The source code is not necessary for hotfix installation: it is provided to fulfill licensing obligations.

Installing the Hotfix by using XenCenter

Choose an Installation Mechanism

There are three mechanisms to install a hotfix:

  1. Automated Updates
  2. Download update from Citrix
  3. Select update or Supplemental pack from disk

The Automated Updates feature is available for XenServer Enterprise Edition customers, or to those who have access to XenServer through their XenApp/XenDesktop entitlement. For information about installing a hotfix using the Automated Updates feature, see the Applying Automated Updates in the XenServer documentation.

For information about installing a hotfix using the Download update from Citrix option, see Applying an Update to a Pool in the XenServer documentation.

The following section contains instructions on option (3) installing a hotfix that you have downloaded to disk:

  1. Download the hotfix to a known location on a computer that has XenCenter installed.
  2. Unzip the hotfix zip file and extract the .iso file
  3. In XenCenter, on the Tools menu, select Install Update. This displays the Install Update wizard.
  4. Read the information displayed on the Before You Start page and click Next to start the wizard.
  5. Click Browse to locate the iso file, select XS71ECU2020.iso and then click Open.
  6. Click Next.
  7. Select the pool or hosts you wish to apply the hotfix to, and then click Next.
  8. The Install Update wizard performs a number of update prechecks, including the space available on the hosts, to ensure that the pool is in a valid configuration state. The wizard also checks whether the hosts need to be rebooted after the update is applied and displays the result.
  9. Follow the on-screen recommendations to resolve any update prechecks that have failed. If you want XenCenter to automatically resolve all failed prechecks, click Resolve All. When the prechecks have been resolved, click Next.

  10. Choose the Update Mode. Review the information displayed on the screen and select an appropriate mode.
  11. Note: If you click Cancel at this stage, the Install Update wizard reverts the changes and removes the update file from the host.

  12. Click Install update to proceed with the installation. The Install Update wizard shows the progress of the update, displaying the major operations that XenCenter performs while updating each host in the pool.
  13. When the update is applied, click Finish to close the wizard.
  14. If you chose to carry out the post-update tasks, do so now.

Installing the Hotfix by using the xe Command Line Interface

  1. Download the hotfix file to a known location.
  2. Extract the .iso file from the zip.
  3. Upload the .iso file to the Pool Master by entering the following commands:

    (Where -s is the Pool Master’s IP address or DNS name.)

    xe -s <server> -u <username> -pw <password> update-upload file-name=<filename>XS71ECU2020.iso

    XenServer assigns the update file a UUID which this command prints. Note the UUID.

    52a16dea-740a-4a39-8a5e-8b71d617f13d

  4. Apply the update to all hosts in the pool, specifying the UUID of the update:

    xe update-pool-apply uuid=52a16dea-740a-4a39-8a5e-8b71d617f13d

    Alternatively, if you need to update and restart hosts in a rolling manner, you can apply the update file to an individual host by running the following:

    xe update-apply host=<host> uuid=52a16dea-740a-4a39-8a5e-8b71d617f13d

  5. Verify that the update was applied by using the update-list command.

    xe update-list -s <server> -u root -pw <password> name-label=XS71ECU2020

    If the update is successful, the hosts field contains the UUIDs of the hosts to which this patch was successfully applied. This should be a complete list of all hosts in the pool.

  6. Use the update-pool-clean command to remove the update files from all hosts in the pool. This command frees up space on shared storage and does not uninstall the update.

    xe update-pool-clean uuid=52a16dea-740a-4a39-8a5e-8b71d617f13d

Files

Hotfix File

Component Details
Hotfix Filename XS71ECU2020.iso
Hotfix File sha256 f9d5b0aad2cd089a4ae7340852704b9008cafca30f0c4a5f45efe40e2d06c83f
Hotfix Source Filename XS71ECU2020-sources.iso
Hotfix Source File sha256 a772d8816e6bb2cb14fba178c36a5df8fef4bb8fbd8a0b914d937ebf16bb042c
Hotfix Zip Filename XS71ECU2020.zip
Hotfix Zip File sha256 5fbcd65dd92c6a93164e7b47418b382ce23d9f92483284bc84aa8886645b9cfe
Size of the Zip file 1.24 MB

Files Updated

blktap-3.5.0-xs.2+1.0_71.2.6.x86_64.rpm
sm-1.17.0-xs.2+1.0_71.2.4.x86_64.rpm
sm-rawhba-1.17.0-xs.2+1.0_71.2.4.x86_64.rpm

More Information

For more information, see XenServer Documentation.

If you experience any difficulties, contact Citrix Technical Support.

Related: