While creating a new pooled or dedicated catalog using the Catalog Creation wizard in Desktop Studio, master images fail to enumerate with the following error message:
“Error expanding node”.
The application event log on the Controller where Desktop Studio is running and indicating a connection failure to the hosting infrastructure server.
Log Name: Application Source: CitrixHostService Date: 6/7/2012 10:16:42 AM Event ID: 1007 Task Category: None Level: Error Keywords: Classic User: N/A Computer: TESTXD505.test.lab Description: Otherwise unhandled exception in WCF call : Citrix.ManagedMachineAPI.HostingInfrastructureAddressNotFoundException: Xen master server not contactable ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.220.10:80 Log Name: Application Source: CitrixHostService Date: 6/7/2012 10:16:43 AM Event ID: 1006 Task Category: None Level: Error Keywords: Classic User: N/A Computer: TESTXD505.test.lab Description: Inner exception : Citrix.ManagedMachineAPI.HostingInfrastructureAddressNotFoundException: Xen master server not contactable ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.10.220.10:80
To resolve the issue, complete the following steps:
Verify for any change in the IP address or Fully Qualified Domain Name (FQDN) of the hosting infrastructure server (use ping to verify network connectivity or nslookup for FQDN resolution).
Update Host connection information in Desktop Studio with the appropriate value.
Note: The behavior can be caused by a missing vCenter certificate on one of the DDCs in the farm. Validate the vCenter certificate is imported to all the DDCs of the farm under the trusted people for the local computer.
This error is typically the result of an IP address or FQDN change (or possibly a DNS issue if FQDN is used) for the hypervisor connection after the initial successful configuration of the host connection following XenDesktop installation.