VMware vCenter ldm client exception: Error trying to leave AD, error code [1332], user

WARN sts-default[14:localhost-startStop-1] [CorId= OpId=] [org.glassfish.jersey.internal.Errors] The following warnings have been detected: HINT: A HTTP GET method, public void com.vmware.identity.rest.idm.server.resources.ServerResource.getStatus(), returns a void type. It can be intentional and perfectly fine, but it is a little uncommon that GET method returns always "204 No Content".
[...]
WARN sts-default[20:Thread-8] [CorId=fva17628-42b4-4a15-a3c2-1442g417d72c OpId=] [com.vmware.identity.interop.ldap.LdapErrorChecker] Error received by LDAP client: com.vmware.identity.interop.ldap.OpenLdapClientLibrary, error code: -1
ERROR sts-default[20:Thread-8] [CorId=bba76607-42b4-4a15-a3c2-7542f427d12c OpId=] [com.vmware.identity.interop.ldap.OpenLdapClientLibrary] Exception when calling ldap_search_s: base=, scope=0, filter=objectclass=*, attrs=[Ljava.lang.String;@1f7g52d9, attrsonly=0
com.vmware.identity.interop.ldap.ServerDownLdapException: Can't contact LDAP server

root@esxi01 [ ~ ]/opt/likewise/bin/domainjoin-cli query
#Error: LW_ERROR_KRB5KDC_ERR_C_PRINCIPAL_UNKNOWN [code 0x0000a309]
#Client not found in Kerberos database

root@esxi01 [ ~ ]/opt/likewise/bin/domainjoin-cli leave
#Leaving AD Domain:   VMWARE.LOCAL
#SUCCESS