Failed to install the VirtualCenter Agent Service
VMware, VMware ESX, Virtual Center October 1st. 2007, 7:08pmA number of customers have been reporting the message: “Failed to install the VirtualCenter Agent Service“, when trying to connect an ESX host to virtual center, often after upgrading to ESX 3.0.2 and VC 2.0.2. In all the cases I have come across these reason seems to be that /tmp/vmware-root does not exist. This directory has to exist for the agent install process. To remedy this you can-
- Login to ESX Server via ssh client as root user
- cd /tmp
- mkdir vmware-root
- Try re-connecting the host to Virtual Center
Apparently there is a cron job that is removing this directory whenever it runs.Here is another method:
- Disable HA. Otherwise, the virtual machines might be forcibly powered down by step 2.
- At the service console, issue
service mgmt-vmware restart - At the service console, issue
service vmware-vpxa restart - Reconnect the virtual machines to VirtualCenter.
- Attempt to re-enable HA within VirtualCenter. If this doesn’t work, this means that vpxa did not install properly.
- At the service console, issue
rpm -qa | grep vpxa - At the service console, issue “rpm -e” on the rpm file that displayed in the previous command.
rpm -e <rpm from step 6> - Reconnect the virtual machines in the usual manner within VirtualCenter.
- Re-enable HA.
- How To Configure Networking from the Service Console Command LineI noticed to
- ESX Disconnected after Upgrading to VirtualCenter 2.0.1ESX Server 3
- Network copy failed for file nvram VMotion mig
- Failed to initialize not well-formed invalid tokenA few Virtua
- Which ESX log fileQuite a few
VMwarewolf
January 22nd, 2009 at 10:57 pm
Perfect. Solved the problem for me. Upgrading existing ESX 3.01 servers after upgrading Virtual Centre to 2.5 U3
March 11th, 2009 at 8:32 am
Perfect also. It solved my problem too. I couldn’t connect tot esx 3.5 servers after upgrading Virtual Centre to 2.5
April 24th, 2009 at 4:05 am
Thanks that worked perfectly
June 27th, 2009 at 6:17 am
Excellent! The service restarts were required but it did the trick. Thanks