Error: "Catalog Creation Master Image Selection Fails with Error Expanding Node"

Error: "Catalog Creation Master Image Selection Fails with Error Expanding Node"

book

Article ID: CTX133616

calendar_today

Updated On:

Description

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”.

User-added image

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

Environment

The above mentioned sample code is provided to you as is with no representations, warranties or conditions of any kind. You may use, modify and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that (a) the sample code may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the sample code fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the sample code. In no event should the code be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SAMPLE CODE, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Although the copyright in the code belongs to Citrix, any distribution of the sample code should include only your own standard copyright attribution, and not that of Citrix. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the sample code.

Resolution

To resolve the issue, complete the following steps:

  1. 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).

  2. 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.


Problem Cause

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.

Issue/Introduction

This article provides a resolution to the error: "Catalog Creation Master Image Selection Fails with Error Expanding Node"

Additional Information

CTX133512 - Error Expanding Node when Adding Virtual Machines to a Streamed Catalog