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

Error: “Unable to connect server” when connecting XenCenter to a Pool Master

Cannot connect to Pool Master by using XenCenter. XenCenter gives an error message:

Unable to connect to server ‘10.90.206.83’.

Could not find XenServer on ‘10.90.206.83’.

Check that XenServer is configured correctly on ‘10.90.206.83 and try again.

Unable to connect to server, Could not find XenServer on

However, Pool Master is accessible by SSH. The command df shows that the root disk /dev/sda1 is full:

[root@XenServer01 ~]# df -h Filesystem Size Used Avail Use% Mounted on/dev/sda1 4.0G 4.0G 0 100% /

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

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

How to Configure Web Interface 5.4 to Start Java Receiver Deployment

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

This article explains how to deploy the Citrix Java Receiver from Web Interface 5.4 and to configure clients to start ICA sessions in Citrix Java Receiver.

Requirements

  • JRE 1.16 32 bit (tested with JRE 1.16 Update 37:32-bit)

  • Pop-up blockers must be enabled and the site must be added to trusted sites

Background

This has been tested from a Windows 7 64-bit OS with Internet Explorer 9, XenApp 6.5, Web Interface 5.4, and Java Runtime Environment 1.16 Update 37 (32-bit).

Related:

  • No Related Posts

Unable to Launch Citrix Studio to Access XenDesktop Site: “The License Server Has Been Upgraded”

ISSUE:

Unable to launch Citrix Studio to access XenDesktop Site. Following message appears: “The license server has been upgraded” and Studio prompts for a Site upgrade.

When running through the upgrade, the following error appears:

“The Service Instance is already registered with the Central Configuration Service”

Related:

  • No Related Posts

Recommended Hotfixes for XenApp 7.x

The following Citrix and Microsoft hotfixes are found to resolve the most common issues with XenApp/XenDesktop 7.6, and XenApp/XenDesktop 7.5 running on a Windows Server 2008 R2 or a Windows Server 2012 R2 platform. These hotfixes focus on basic functionality and stability.

Note :

1. Fixes for Current Releases will likely be released in the next Current Release; therefore, it is less likely that an individual fix would be released for a Current Release version. You may be asked to upgrade to the next version of a Current Release that includes the requested fix and new functionality.

2. This article aims to describe the recommended hotfixes before Citrix LTSR(7.6.300) and Citrix CR(7.7~7.14). Please go to docs.citrix.com for more hotfixes regarding LTSR and CR.

Issue: Attempts to restart the Citrix Device Redirector Service from within a VDA or RDP session can cause the service to remain in an unresponsive state rather than actually restarting.

Available Software Updates:

ICAWS760WX64047 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit) – English
ICAWS760WX86047 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64053 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

Issue:

  • The operating system experiences an error on picadm.sys and a blue screen appears with stop code 0x20.
  • A deadlock on picadm.sys can cause published applications to become unresponsive.
  • The operating system experiences an error on picadm.sys and a blue screen appears with stop code 0x50.
  • The VDA might become unresponsive at the “Welcome” screen due to a deadlock on picadm.sys.
  • Remote Desktop (RDP) connections to the server fail.

Available Software Update:

ICATS760WX64048 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue: Certain third-party published applications might fail to start on XenApp servers. As a result, the wfshell.exe process might close unexpectedly. When this error occurs, no indication that the session is starting or error messages appear on the user device.

Available Software Updates:

ICAWS760WX64042 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit)-English
ICAWS760WX86042 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64040 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue: Citrix XenApp 7.6 and XenDesktop 7.6 VDA Core Services running on Windows Server 2008 R2 (Server OS) might become unresponsive at the “Welcome” screen. If this occurs, new Receiver and Remote Desktop (RDP) connections to the server fail.

Available Software Updates:

ICAWS760WX64026 – For VDA Core Services 7.6 for Windows Desktop OS (64-bit) – English
ICAWS760WX86026 – For VDA Core Services 7.6 for Windows Desktop OS (32-bit) – English
ICATS760WX64032 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue: The Citrix Stack Control service quits unexpectedly if there is an invalid session key.

Available Software Update:

ICATS760WX64006 – For VDA Core Services 7.6 for Windows Server OS (64-bit) – English

XenApp 7.5/ 7.1

Issue:

  • The memory consumption of the Monitoring Service can grow steadily until the service stops responding to requests from Director, eventually rendering Director unresponsive as well.
  • If the resource name (display name) changes on the Delivery Controller, users who previously subscribed to the applications cannot start the applications.
  • If you create virtual machines (VM) with Desktop Studio that uses Machine Creation Services and the VMs are hosted on a VMware hypervisor, attempts to update VMs that are part of the machine catalog fail.

Available Software Updates:

Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x64 – English
Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x86 – English

_______________________________________________________

Issue:

  • VDAs can becomes stuck in the “initializing” state of registration process. The issue occurs after the Citrix Desktop Service is running for several days without being restarted.
  • When the function “CName” is enabled, VDA registration can take excessively long.

Available Software Updates:

BrokerAgent750WX64003 – For Broker Agent 7.1/7.5 for Windows OS (64-bit) – English
BrokerAgent750WX86003 – For Broker Agent 7.1/7.5 for Windows OS (32-bit) – English

_______________________________________________________

Issue: Installing hotfixes for XenApp 7.5, and XenDesktop 7.1 and 7.5 VDA Core Services for Windows Desktop and Server OS released before September 2014 causes the ICA Session performance monitor counter to be removed. This can have an adverse effect on the operation of tools and processes that rely on these counters.

Available Software Updates:

ICAWS750WX64011 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English
ICAWS750WX86011 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English
ICATS750WX64011 – For VDA Core Services 7.1/7.5 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue:The Citrix Print Manager Service (CpSvc.exe) process might exit unexpectedly.

Available Software Updates:

ICAWS750WX64019 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (64-bit) – English
ICAWS750WX86019 – For VDA Core Services 7.1/7.5 for Windows Desktop OS (32-bit) – English
ICATS750WX64019 – For VDA Core Services 7.1/7.5 for Windows Server OS (64-bit) – English

_______________________________________________________

Issue:

  • This fix addresses an intermittent high memory utilization issue of the Broker Service on the Controller.
  • This fix addresses a memory consumption issue of the Monitoring Service.

Available Software Updates:

Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x64 – English
Update 3 – For Citrix XenDesktop 7.1 Delivery Controller x86 – English

Note:

Refer to the complete list of all the available HotFixes for

XenApp 7.6 64-bit32-bit

XenApp 7.5 64-bit32-bit

Microsoft HotFixes (including links to Microsoft HotFix list)

Windows Server 2012 R2 contains most of the following hotfixes (exceptions noted inline). Microsoft has published the following KB article specific to Remote Desktop Services: Available Updates for Remote Desktop Services (Terminal Services) in Windows Server 2012 R2. For Microsoft Hotfixes applicable to the Windows Server 2008 R2 and the Windows 7 platforms, see the “Microsoft Hotfixes” section in the following article: CTX129229 – Recommended Hotfixes for XenApp 6.x on Windows Server 2008 R2.

Note: The descriptions of the Microsoft fixes listed in this article (CTX142357) might not match the descriptions in the Microsoft articles for the following Microsoft fixes. This is not an error. The issue description listed by Citrix in the following matrix was resolved by an earlier version of that file however it has been superseded by the article/fix currently listed.

KB Number Issue description
KB3033929
  • UPM driver load breaks if this KB is not applied.
KB3078676 – NEW
  • This article describes an issue in which even 1530 is logged, and user profile service (ProfSvc) leaks paged pool memory and handles in Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2. This issue occurs if the ProfSvc service loads and then unloads a user profile. Additionally, the following event is logged in the Event viewer: Event ID 1530. Description: Windows detects your registry file is still in use by other applications or servers. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards. No user action is required.
KB3127673 – NEW
  • The Stop error 0x000000C2 might be caused by an error handling issue in the win32k.sys file.
  • The Stop error 0x0000003B might be caused by a synchronization issue in the dcgkrnl.sys file.
  • The parameters in Stop error messages may vary, depending on the configuration of the computer.
  • Not all “Stop 0x000000C2” errors or “Stop 0x0000003B” errors are caused by one of these issues.
KB3055615 – NEW
  • A windows Server 2012 R2 Server becomes slow and unresponsive if update 2927901 is installed.
  • You have update 2927901 installed on a Windows Server 2012 R2 server.
  • You have users who frequently log in and log off the server through Remote Desktop.
KB3013769
  • Memory leak occurs when you create or delete CSV snapshots by using a VSS hardware provider
  • IIS crashes occasionally when a request is sent to a default document in Windows 8.1 or Windows Server 2012 R2
  • You receive Stop error 0xD1 in Windows Server 2012 R2 or Windows 8
  • Device does not exist error after you reinsert a USB COM port device
KB2978367
  • Remote Desktop session freezes when you run an application in the session in Windows 8.1 or Windows Server 2012 R2.
KB2967077
  • A network printer is deleted unexpectedly in Windows
KB2895698
  • Users who have the remote audio setting enabled cause the RD Session Host servers to freeze intermittently in Windows Server 2012 R2 or Windows Server 2008 R2 SP1
KB2896328
  • You are logged on with a temporary profile to a remote desktop session after an unexpected restart of Windows Server 2012
KB2852483
  • Memory leak occurs in the Dwm.exe process on a Remote Desktop computer that is running Windows 8 or Windows Server 2012
KB2995388
  • Memory leak occurs when you play mp4 files in Windows 8.1 or Windows Server 2012 R2
  • Computer freezes when you switch to another account in Windows 8.1 or Windows Server 2012 R2
  • An NTFS volume is flagged as dirty after each restart, and CHKDSK can find no issues
  • Print jobs are intermittently processed slowly through Windows 8.1-based or Windows Server 2012 R2-based printer servers
  • Network printers that use TCP/IP port cannot print after first document has printed in Windows

Related:

  • No Related Posts

Voice call over AVAYA Softphone may have a choppy voice or humming sound after multiple users login, while using Receiver for Windows 

1. Enable the Audio policies as documented in this article:

7.15 https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/policies/reference/ica-policy-settings/audio-policy-settings.html#audio-quality

1912 https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/1912-ltsr/policies/reference/ica-policy-settings/audio-policy-settings.html#audio-quality

Ensure Audio quality is set to Medium in Citrix audio policy

2. Added following in default.ica at C:inetpubwwwrootCitrixStoreApp_Datadefault.ica

; This is to enable Real-Time Transport

EnableRtpAudio=true

; This is to Allow Real-Time Transport Through gateway

EnableUDPThroughGateway=true

; This is to set audio quality to Medium

AudioBandwidthLimit=1-

; UDP Port range

RtpAudioLowestPort=16500

RtpAudioHighestPort=16509

3. Did a iisreset using following command on Storefront server < elevated command prompt>

iireset


4. Set HDX Adaptive Transport to “Preferred” in Citrix Policies


5. Do a group policy update on VDA hosting Avaya softphone application

gpupdate /force


6. The ICA file should have following entries:

[Avaya one-X Communi]

Address=XXX.XXX.XXX.XXX:1494

AudioBandwidthLimit=1-

AutologonAllowed=ON

BrowserProtocol=HTTPonTCP

CGPAddress=*:2598

ClearPassword=XXXXXXXXXXX

ClientAudio=On

DesiredColor=X

DesiredHRES=0

DesiredVRES=0

Domain=<Hexa Decimal>

DoNotUseDefaultCSL=On

EnableRtpAudio=true

EnableUDPThroughGateway=true

FontSmoothingType=0

HDXoverUDP=Preferred

InitialProgram=#Avaya one-X Communi

Launcher=WI

LaunchReference=<Hexa Decimal GUID>

LocHttpBrowserAddress=!

LogonTicket=<Hexa Decimal GUID>

LogonTicketType=CTXS1

LongCommandLine=

LPWD=687

NRWD=656

ProxyTimeout=30000

ProxyType=Auto

RtpAudioHighestPort=16509

RtpAudioLowestPort=16500

SessionsharingKey=<Hexa Decimal GUID>

SFRAllowed=Off

SSLEnable=Off

startSCD=XXXXXXXXXX

Title=Avaya one-X Communicator

TransportDriver=TCP/IP

TRWD=0

TWIMode=On

UDPCGPPort=XXX.XXX.XXX.XXX:2598

UDPICAPort=XXX.XXX.XXX.XX:1494

WinStationDriver=ICA 3.0

7. Test Avaya softphone, by calling an extension or direct phone number

Related:

  • No Related Posts

Error:”Operation Not Permitted” on NetScaler VPX on Hyper-V while modifying interface

In ns.logs it was observed that other parameters are also getting set while making changes to the inteface Alias from GUI.The parameter which was failing was the set ha monitor ON parameter.

Logs:

——

ns.log.0:Sep 15 15:59:04 <local0.info> 127.0.0.2 09/15/2015:20:59:04 GMT NLR-A-NS01 0-PPE-0 : default GUI CMD_EXECUTED 139 0 : User nsroot – Remote_ip 10.1.1.6 – Command “set interface 0/1 -speed AUTO -duplex AUTO -flowControl OFF -autoneg ENABLED -haMonitor ON -mtu 1500 -tagall OFF -state ENABLED -lacpMode DISABLED -lagtype NODE -ifAlias MANAGEMENT -throughput 0 -linkRedundancy OFF -bandwidthHigh 0 -bandwidthNormal 0 -intftype “Hyper v” -ifnum 0/1 -lldpmode NONE -lrsetPriority 1024″ – Status “ERROR: Operation not permitted”

This an expected behaviour as per Issue Id: TSK0312538

When VPX is installed on top of a hypervisor – the interfaces are registered based on what the hypervisors expose.

There will be several parameter given back to VPX when it tries to register – physical link state being one of them.

The way the drivers are written specific to each hypervisor is different – and in case of Hyper-V the physical link state information is not passed through the virtual interface, unlike Xenserver which passes on this information.

As a result since VPX does not have link state information in case of Hyper-V it will flag this information and on execution of the HAMON set command rejects as it does not apply in this scenario.

User-added image

Related:

  • No Related Posts

Citrix Hypervisor unable to sync to NTP/Chrony server

Make sure that your host is having similar/correct DNS servers throughout the pool

1 Add all xenserver Public NTP servers to the host . Refer below link for the same.

https://support.citrix.com/article/CTX121278

Note: Make sure that you have identical and equal number of NTP source servers on all xenserver host in pool

2. It will automatically restart the ntpd/chronyd service but sometimes that does not sync the time to NTP and we have to manually restart the ntpd/chronyd service using below command.

# service ntpd restart

Run below command to restart chronyd service

# systemctl restart chronyd.service

If even after manually restarting the service it does not work then follow below steps

3. Stop ntpd service using below command

# Service ntpd stop

Run below command for chronyd service

# Systemctl stop chronyd.service

4. Manually sync xenserver from hwclock to desired ntp servers using below command

# ntpdate 0.xenserver.pool.ntp.org

Use below command for Citrix Hypervisor 8.1 and 8.2

# chronyd -q 'server 0.xenserver.pool.ntp.org iburst'

5. Started ntpd service

service ntpd start

It will Sync the host to NTP servers now.

Use below command to start chronyd service

systemctl start chronyd

Related: