VDAs Do Not Register in LHC Mode When Registration Port is Not Set To Default
Article ID: CTX229493
Updated On:
Description
In a 7.12+ XenApp/XenDesktop site where the DDC(s) and VDAs have been configured to communicate over a non-default port, if the site goes into outage (Local Host Cache) mode due to the database being unavailable, VDAs will fail to re-register with the DDC(s).
Resolution
C:\Program Files\Citrix\Broker\Service\HighAvailabilityService.exe –VdaPort <CORRECT PORT #>
Where CORRECT PORT is the non-default port you have configured and to match that which is configured for BrokerService.exe.
Example below where the non-standard port is 8080
Problem Cause
Although the Broker Service has been configured to listen on the non-default port the High Availability Service which takes over for the Broker Service may still be configured to listen on the default port (TCP port 80). To confirm this run the following commands:
Cd C:\Program Files\Citrix\Broker\Service
HighAvailabilityService.exe /show
In this example the High Availability Service is set to listen on the default TCP Port 80. If the VDAs are configured to use a different TCP port they will fail to register when the High Availability Service is active (LHC Mode).
Additional Information
