VMware Cloud Community
windroot
Contributor
Contributor

VCenter Start Error - VmwareComponentManager faild to start

my vcenter server is 6.0, installed on window, when i run service-control --start --all then VMwarecomponentManager service failed to start. How to fix this error. Thank you.

access web:

503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:00000000012F9190] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)

log: sso > vmware-sts-idmd

[2019-12-19T04:50:55.702-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 INFO ] [IdmServer] IDM Server starting... [2019-12-19T04:50:56.046-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 WARN ] [LdapErrorChecker] Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 49 [2019-12-19T04:50:56.046-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 ERROR] [WinLdapClientLibrary] Failed ldap_bind_s(). com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid Credentials

[2019-12-19T04:50:56.046-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 WARN ] [ServerUtils] cannot bind connection: [ldap://localhost:389, cn=172.16.199.200,ou=Domain Controllers,DC=vsphere,DC=local]

[2019-12-19T04:50:56.062-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 ERROR] [ServerUtils] cannot establish connection with uri: [ldap://localhost:389]

[2019-12-19T04:50:56.062-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 INFO ] [ServerUtils] Waiting for vmware directory to come up - Retry 1 [2019-12-19T04:51:06.065-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 WARN ] [LdapErrorChecker] Error received by LDAP client: com.vmware.identity.interop.ldap.WinLdapClientLibrary, error code: 49 [2019-12-19T04:51:06.065-08:00                      4b3cb569-e80c-4702-9505-804a4e0f86d8 ERROR] [WinLdapClientLibrary] Failed ldap_bind_s().

log cm:

2019-12-19T07:07:01.431-08:00 [WrapperListener_start_runner  WARN  com.vmware.cis.services.cm.service.util.LsUtils ()] Call to lookup service failed; uri:https://172.16.199.200/lookupservice/sdk [com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 404]

2019-12-19T07:07:01.431-08:00 [WrapperListener_start_runner  WARN  com.vmware.vim.vmomi.client.http.impl.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase ()] Shutting down the connection monitor.

2019-12-19T07:07:01.431-08:00 [WrapperListener_start_runner  WARN  com.vmware.vim.vmomi.client.http.impl.HttpConfigurationCompilerBase$ConnectionMonitorThreadBase ()] Shutting down the connection monitor.

2019-12-19T07:07:01.432-08:00 [WrapperListener_start_runner  WARN  com.vmware.cis.services.cm.service.SecurityAgent ()] Failed to connect to SSO service; e: com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 404, attempt 31 of 60, retry in 5s, left:148s

0 Kudos
6 Replies
T180985
Expert
Expert

looks like a username and password error.

[WinLdapClientLibrary] Failed ldap_bind_s(). com.vmware.identity.interop.ldap.InvalidCredentialsLdapException: Invalid Credentials

&

2019-12-19T07:07:01.432-08:00 [WrapperListener_start_runner  WARN  com.vmware.cis.services.cm.service.SecurityAgent ()] Failed to connect to SSO service

Please mark helpful or correct if my answer resolved your issue. How to post effectively on VMTN https://communities.vmware.com/people/daphnissov/blog/2018/12/05/how-to-ask-for-help-on-tech-forums
0 Kudos
windroot
Contributor
Contributor

So, How can i fix it?

Do you have any idea.

0 Kudos
T180985
Expert
Expert

Are the services using a specific service account to start? If so i would start with checking that account

Please mark helpful or correct if my answer resolved your issue. How to post effectively on VMTN https://communities.vmware.com/people/daphnissov/blog/2018/12/05/how-to-ask-for-help-on-tech-forums
0 Kudos
windroot
Contributor
Contributor

This problem begin from that i cannot login vcenter by administrator@vsphere.local. I follow this VMware Knowledge Base  and delete sso log, but it's not work. So i restart all vcenter service and get above error?

I tried multiple ways to troubleshoot but was not succeeded.

0 Kudos
nirmalgnair
VMware Employee
VMware Employee

Hi

Kindly check the vmdird-syslog.log and if you see the below error,

Bind Request Failed ([17] 10.105.217.85:389<-10.105.212.102:54753) error 49: Protocol version: 3, Bind DN: "cn=accountname,ou=Computers,dc=vsphere,dc=local", Method: 163

Then go ahead and follow the below VMware KB :

VMware Knowledge Base

Regards,

Nirmal Nair

0 Kudos
windroot
Contributor
Contributor

I changed and updated password dcAccount, but my problem didn't resolve.
How can i check my dcAccount change successful?

I

0 Kudos