VMware Aria Automation Tools

 View Only
  • 1.  vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Jul 02, 2016 01:20 PM

    After powering on IaaS server,  VCAC Management Agent service had stopped. When we tried to start the service we got the below error as seen in the below image. And also services were not showing as registered in VRA root console.  So we tried reinstalling agent in IaaS server and after that VCAC Management Agent service was up and running. But still services were not showing as registered in VRA root console. Anyone who can guide me on same?





  • 2.  RE: vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Jul 04, 2016 03:05 AM

    You may have the same root cause, but the Management Agent being online/offline won't affect service registration.

    Have you by any chance performed a certificate update?



  • 3.  RE: vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Jul 04, 2016 07:55 AM

    no



  • 4.  RE: vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Jul 04, 2016 07:57 AM

    Could you attach the Management Agent config file?

    Example location : C:\Program Files (x86)\VMware\vCAC\Management Agent\VMware.IaaS.Management.Agent.exe.Config



  • 5.  RE: vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Jun 08, 2017 04:28 PM

    Hey did you ever get a resolution for this? i am having same problem in vra 6.2 and looks to be preventing upgrade



  • 6.  RE: vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Jun 08, 2017 05:52 PM

    Found the issue for me. Turns out for some reason the  VMware.IaaS.Management.Agent.exe.Config file was empty! Luckily i could get this info from another agent server.

    Cheers



  • 7.  RE: vCloud Automation Center Management Agent Service failed to start in vRA 7

    Posted Feb 06, 2018 10:10 AM

    I managed to resolve this issue by deleting the blank config file, copying the backup config file (.bak) and renaming the copied backup config to the original name. After this the service started without issues.