Error: The hypervisor could not be contacted
Article ID: CTX131512
Updated On:
Description
XenDesktop cannot communicate with the Hosting Infrastructure
This article contains information about a number of possible reasons why XenDesktop might not be able to communicate with your hosting infrastructure, such as XenServer, vSphere or SCVMM.
General Problems
-
Check that the correct address, username, and password for the machine is used. Also check the machine has the correct DNS records, and your network infrastructure allows communication with the machine.
Note: The cause of the failures here might be because of an incorrectly configured firewall.
-
Check that a supported version of the hosting infrastructure is used. The supported hosting infrastructures for each version of XenDesktop are listed in the Knowledge Center article CTX131239 - XenDesktop/Provisioning Services Hypervisor Citrix Product Support.
XenServer - Specific Issues
If attempting to use SSL to communicate with XenServer, replace the default SSL certificate installed with XenServer. See Citrix Documentation- Replace the default XenServer SSL certificate.
Note: Every XenDesktop Controller in the Site must trust the certificate you generate.
vSphere - Specific Issues
-
If attempting to use HTTPS to communicate with vSphere, ensure that every XenDesktop Controller in the site trusts an appropriate SSL certificate. For details on how to do this if you are using the default vCenter certificate, see Citrix Documentation - VMware and virtual machine management.
-
If attempting to use HTTP to communicate with vSphere, ensure you have modified the vCenter configuration appropriately. For details on how to do this, refer to the Knowledge Center article CTX125578 - XenDesktop Error: The hosting infrastructure could not be reached at the specified address.
-
Ensure attempting to communicate with vCenter, not directly with an instance of ESXi.
-
Ensure that the URL specified for vCenter ends in /sdk, unless you have reconfigured your vCenter to use a different path.
SCVMM - Specific Issues
-
Ensure attempting to communicate with SCVMM, not directly with an instance of Hyper-V.
-
Ensure that the SCVMM Console is installed on every XenDesktop Controller in the Site, and that the SCVMM Console is the same version as your SCVMM server.
Additional Resources
Citrix Blog - Provision your apps and desktops straight onto AWS with XenApp & XenDesktop 7.5
Issue/Introduction
