Thursday, 9 March 2017

Vmware Component Service-Failed to Start,Stuck on Starting

Hello Professionals,
Today am sharing a very frustrating issue that was irritating, and because of this only re-installed full vcenter setup 3 times.God grace today got one solution which was very straight and clear according to my infrastructure.
 It tools 4.5 hours me to get the solution for this issue and i got it.
Issue: Vmware component service stuck on starting and failed to start. Service name vmware-cm (VMware Component Manager).

Precaution steps: Backup all certificate that are related to VMWARE before making any changes to certificate.  

Login to Vcenter server as administrator privilege and browse to C:\Program Files\VMwarevCenter Server\vmcad\certificate-manager
and run the certificate bat file.

Here you can lots of option after running certificate-manager bat file. Select option 4 and press enter. Here i gave option to regenerate a new VMCA certificate and register for this vcenter domain.
After this it will ask to update the following details one by one for server IP address, FQDN, Company Name, State, City etc..Then it will start it processing and will take approx 20-30 min to give you status final status.

Once this is 100% completed, you can see all services are started by automatic. In My case regeneration failed due to Adding cert to VECS Store Failed and rolled back all the process by after this even component service started. Looking on the Certificate-Manager log for checking exactly why this happens. This will generate Root Cert using VMCA with sha256WithRSAEncryption Signature Algorithm.
But i did again and its completed 100% successfully and all services are running properly.

Other Important Points for VMCA:
1.  There is a known issue with version 6.0 U2 where the CSR created for the VMCA as a Subordinate will not have the all attributes. In case with Microsoft CA server will force to include the attributes based on the certificate template last time used or if you had created any template for your reference.
2. VMCA will only issue certificates to clients that can authenticate to VMware Directory Service in the same domain network as well as issues certificates for VMware solution users, machines that and services.
3. Must watch this Youtube Link.Here a good discussion about Vmware Licensing and other terms.
4. A vCenter Server with an Embedded PSC will have 4 Solution Users:vpxd,vpxd-extension,machine and vsphere-webclient
5. A vCenter with an External PSC will have 4 Solution Users:vpxd,vpxd-extension, machine and vsphere-webclient
6.An External PSC will have 2 Solution Users: machine and vsphere-webclient
7.vSphere 6.0 U3 has made very nice enhancement in Certificate-Manager.You need to update only cfg file under certificate-manager and other dependency creation and registernation will be taking care by this too it self.Its Automatic process.

This cert tool will regenerate and register the certificate for all these Solution users which are mentioned in point 4,5 and 6

I will be happy to listen from you. Learn, earn and share the knowledge.
Please comment and share the blog, Let your friends know the solution for this issue.
Thanks a lot for your support.


Posted by at
Labels: ,

3 comments:

  1. Piyush Srivastava28 June 2017 at 13:33

    and another update on this issue, if your NTP settings is not correct or time difference is there. Then also this service will not start.

    ReplyDelete
  2. Unknown8 October 2018 at 20:31

    Hi, Just to add to the thread above. I have experienced the same issue, in my case the problem was the external PSC services were not fully started. thanks

    ReplyDelete
  3. Unknown17 December 2018 at 09:47

    Hi Piyush, I am facing similar problem. I am trying to upgrade a Windows vcenter server from 6.0 u3e to 6.0 u3h. The installation completes successfully, but the vcenter services are not starting, except vmwareAfdService, rhttpproxy,vmwareDirectoryService, vmwareCertificateService, VMwareIdentityMgmtService Services start successfully. The VMwareSTS, that is the security Token service failing to start, its status is Starting and as such none of the other vmware vcenter services start.We have expired custom certificates on this server. I ran the certificate-manager batch file and chosen option 8, reset all certificates. Should i also chose 4 as you did. Please let me know.

    ReplyDelete

Subscribe to: Post Comments (Atom)