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

NOTICE of STATUS CHANGE ANNOUNCEMENT FOR CITRIX ADC (formerly NetScaler ADC) Traffic Domain BASED FEATURES & FUNCTIONALITIES

Citrix Systems, Inc. announces a Notice of Status Change (NSC) for Citrix ADC Traffic Domain features and functionalities. Table 1 below explains Citrix ADC life cycle management milestones as well as important information about dates and options during this period. The dates and milestones provided are in accordance with stated End of Life/End of Support policies for Citrix Systems, Inc.

Table 1. Milestones and Dates for Citrix ADC Traffic Domain features & functionalities

Milestone Definition Date/Release
Notice of Status Change The NSC date is the date on which Citrix announces the intent to initiate the lifecycle management process for Traffic Domain. Sep 1st, 2021
Feature Deprecation The dates on which these features and capabilities will be deprecated. Users will be warned to switch to the replacement features when using given build. Q3 2021 (next Citrix ADC GA release – 13.1)
Feature Removal The timeline from which these features will not be available. Q3 2023

Citrix ADC Features & Functionalities Affected

The features & functionalities affected by this announcement and their replacements are listed in Table 2 (below). The features & functionalities listed in the Feature Replacement column represent the migration path for these deprecated features/functionalities.

Table 2. Features & functionalities affected by this announcement

Feature Description Feature Replacement
Traffic Domain Admin Partition

Recommendations for Customers

Citrix recommends that all Citrix ADC customers take steps to switch from the deprecated features & functionalities to the corresponding replacements suggested in Table 2 above.

Tools to aid in migration from Traffic Domains to Admin Partitions are available at https://github.com/citrix/ADC-scripts/tree/master/td-to-ap

For More Information

Related:

  • No Related Posts

Error “cannot connect to the hypervisor at object reference not set to an instance of an object” when running the XDSW

When running the XenDesktop Setup Wizard, it can fail with the following error:

“cannot connect to the hypervisor at <ADDRESS> object reference not set to an instance of an object”

The string <ADDRESS> will contain the actual URL of the vCenter Server.

This issue can appear when the DataCenter name on the VMWare side has a comma character anywhere in the name.

For example notice the use of the comma character in the following screenshot:

User-added image

Related:

  • No Related Posts

Users unable to relaunch the published applications, error “Citrix workspace will try to reconnect…”

Keep Alive policy settings:

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies/reference/ica-policy-settings/keep-alive-policy-settings.html

Session reliability policy settings:

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies/reference/ica-policy-settings/session-reliability-policy-settings.html

Session reliability on Citrix ADC high availability pair:

https://docs.citrix.com/en-us/citrix-adc/current-release/ns-ag-appflow-intro-wrapper-con/session-reliablility-on-citrix-adc-ha-pair.html

Related:

  • No Related Posts

Failed to launch session with the error code “Your session ‘AppName’ did not launch successfully due to error code 3505. Please contact your administrator for more information about the error.” on Citrix Workspace App During App/Desktop Launch

This article is intended for Citrix administrators and technical teams only.

Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.

When launching an application or desktop session using Citrix Workspace App, the session fails to launch with the error code “Your session ‘AppName’ did not launch successfully due to error code 3505. Please contact your administrator for more information about the error.”

Related:

  • No Related Posts

Failed to launch session with the error code “Your session ‘AppName’ did not launch successfully due to error code 3500. Please contact your administrator for more information about the error.” on Citrix Workspace App During App/Desktop Launch

Causes and Solutions

Cause 1: For Multi-session OS machines, the VDA machine is reaching the maximum load you specified in one of following load management policies:

  • Maximum number of sessions
  • CPU usage
  • Disk usage
  • Memory usage
  • Memory usage base load

Solution 1: Please confirm if the VDA Server has reached the settings you specified in above HDX policies. This can be checked:

  • Using Citrix Director: Trends => Load Evaluator Index tab.
  • Using PowerShell:
Get-BrokerMachine |Select DNSName, LoadIndex, LoadIndexes

When troubleshooting the issue, please consider:

  • Logging off idle or disconnected sessions
  • Increasing the number of VDA servers hosting the published resource to the Delivery Group.
  • Resolving the performance issue on the VDA server if it is running into performance problems.

Cause 2: The Random single-session OS or multi-session OS machine the user is connecting to is in maintenance mode.

Solution 2: Please turn off Maintenance Mode for that machine from Citrix Studio or PowerShell cmdlet:

Set-BrokerMachineMaintenanceMode -InputObject <domainname><hostname> $false

Cause 3: The user attempts to launch an app or desktop in Citrix Workspace app after access to the resource in the Delivery Group has been removed, but before the user has refreshed avaialbe apps in Citrix Workspace app.

Solution 3:

  • If Citrix Workspace app Self-Service Plug-in is disabled by Manage SelfServieMode policy , right click the Citrix Workspace app icon in Windows notification area and click Refresh.
  • From the Citrix Workspace app, click the user name, in the dropdown list, and click Refresh Apps.

Cause 4: The VDA machine to host the HDX session is not registered to any of the Delivery Controller servers in the site.

Solution 4: Please refer to How to Troubleshoot Virtual Delivery Agent (VDA) Registration issues to resolve VDA registration issue.

Cause 5: There are insufficient random/non-persistent Windows desktop VDA machines available for the user to successfully launch one.

Solution 5: Please power on more VMs in the Delivery Group or add more VDA machines to the Delivery Group.

Cause 6: Pass-through authentication to Citrix Workspace app is attempted but the XML trust service is not correctly configured.

Solution 6: Please run the following PowerShell command as an administrator on the Delivery Controller:

Set-BrokerSite -TrustRequestsSentToTheXmlServicePort $True

Cause 7: SSL related registry settings under “HKLMSYSTEMCurrentControlSetControlTerminal ServerWdsicawd” are rolled back to the default values after installing CU on VDA 1912 LTSR. (This is problem only when HdxSslEnabled is true on your delivery group.)

Solution 7: Please refer to Configure TLS on a VDA using the PowerShell script and enable TLS with “Enable-VdaSSL.ps1” on VDA. This is a bug. Investigation is in progress under CVADHELP-17421. Please contact technical support if you need help.

Related:

  • No Related Posts

Error: “Login Failed. The address given did not provide a valid App list” in Citrix Receiver

This article is intended for Citrix administrators and technical teams only.

Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.

The following error message is displayed on a smart phone when connecting to Citrix Receiver:

“Login Failed. The address given did not provide a valid App list. Please check the address, gateway settings, and your network connection.”

User-added image

Related:

  • No Related Posts

Receiver 4.0 for Windows Unable to Use Least Loaded Server Using Custom ICA file with “HTTPBrowserAddress=”

This article is intended for Citrix administrators and technical teams only.

Non-admin users must contact their company’s Help Desk/IT support team and can refer to CTX297149 for more information.

When using Receiver version 4.0 and a custom ICA file with a value set for an Application name for the tag “HTTPBrowserAddress=”, it might not be possible to connect to the least loaded server.

Steps to reproduce the issue:

  1. Install Receiver for Windows 4.0.
  2. Try to launch a published application via Citrix Quick Launch tool.

    Ensure “Launch on this server” check box is cleared.

Expected behavior: The application can be launched successfully.

Actual behavior: Cannot launch the application. The following message is displayed:

“Unable to launch your application. Contact your help desk with the following information: Cannot connect to the Citrix XenApp server. There is no Citrix XenApp server configured on the specified address.”

Related:

  • No Related Posts

“Your Operation is Canceled.”Receiver 4.5 – Scan and 4.6 -USB Redirection Failing on Receiver for Windows 4.6

A public fix for this case issue has been released, and is available for download.

ref: https://www.citrix.com/downloads/citrix-receiver/

The issue is documented in the current documentation.

ref: http://docs.citrix.com/en-us/receiver/windows/4-7/about/fixed-issues.html

◦Citrix Receiver for Windows 4.5 and 4.6 might fail to perform the scan function with the following error message:

“Your operation is canceled.”

[#LC6468]

Related:

  • No Related Posts