Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
You can see the successful creation of a template vm from your golden image .Instant clones fail to complete customization and fail on. The Horizon Console displays a message similar to:"AD_FAULT_RETRYABLE unable to contact peer unable to create connection pool"Instant Clone Provisioning fails with a Log Line entry similar to the below in a Connection Server debug file: Location of Horizon (VDM) log files (1027744) Initial publish failed: Fault type is AD_FAULT_RETRYABLE - com.vmware.daas.cloneprep.ldap.LdapException$LdapConnectionException: unable to contact peer: unable to create connection pool, resultCode=91 (connect error), errorMessage=null "Caused by: LDAPException(resultCode=91 (connect error), errorMessage='An error occurred while attempting to connect to server dc1:389 java.io.IOException: Unable to establish a connection to server dc1:389 within the configured timeout of 10000 milliseconds.')" Fault type is AD_FAULT_RETRYABLE - com.vmware.daas.cloneprep.ldap.LdapException$LdapConnectionException: unable to contact peer: createComputerAccount: Fail to create computer account xxxx, entryDn: CN=xxxx,OU=xxx,OU=xx,DC=xx,DC=xx,description: Internal Template account. Can be deleted if vm cp-template-xxxx does not exist in the VC, due to LdapConnectionException. - unable to contact peer: unable to create entry, resultCode=81 (server down), errorMessage=null
ResultCode=91 (connect error) is a API response to a request. This code is indicative of a connection failure to the Domain Controller .There are a number of potential reasons for this result code, including: A server is currently down or not accepting new connections.A networking problem prevents the Horizon agent machine from reaching the DC.Security negotiation between the client and the server fails (for example, an invalid SSL certificate)The client encounters a connection timeout before the connection can be established. resultCode=81 (Server Down) indicates that an existing connection to the server is no longer valid.Causes can vary including Antivirus or Firewall interference.Network issues. Horizon relies on API calls to the active directory to process jobs in a timely manner. Environmental Matters and Customization Issues can have varied causes, Please see these resources for additional context: Troubleshooting Vmware Horizon Machines that do not complete Customization (83985) Horizon View Best Practices: Parent Image Creation and Maintenance. (90152)
Ensure all basic connectivity checks are performed between the components involved :Horizon agent machine, Horizon Server and Domain Controller Infrastructure Check the network connection utilizing tools such as ping , telnet. Make sure that the hostnames and IP addresses are correct and can be resolved properly.Verify DNS Resolution utilizing tools such as nslookup .Check network device settings: Verify that any firewall, load balancer, every network device in the path of each component allows a consistent and permanent connection path. Ensure all Guest Operating Systems involved , both server and virtual desktop are healthy and operational. Ensure all services needed for a domain join are up and running.Ensure there is adequate available memory and disk space.Ensure any account in use for the domain join is available, with appropriate permissions and enabled.With the timestamp from log event on the horizon server, verify the response in logs and events on the specified domain controller Ensure your operating systems are inter compatible with both Horizon and your domain controller .Ensure all operating systems are synced to the same time source and receiving valid time. Please refer to vendor documentation in terms of best practice and specifics on troubleshooting:Active Directory domain join troubleshooting guidance
This is a child article of AD_FAULT_FATAL: An Index of Instant Clone Creation Errors returned by Active Directory (91065)