Updated VI Client

[Esys]

I updated my Virtual Center server to VC-2.0.2-61426. Now the VI client will not connect to one ESX server. There are four in my farm, two 3.0.2, patched thru Oct 8, and two 3.0.1 also patched thru Oct 8. Three of the servers load fine, the fourth (3.0.1) always fails with the errors:

Login failed due to a bad username or password

Failed to install the VirtualCenter Agent service

I am not using a bad username or password - and in fact can use the VI client to connec directly to the server. My whole purpose here was to upgrade the servers to ESX-3.0.2-61618, but now I have these orphaned VMs on a server that has no idea of VMotion.

Since installing the newer version, even version 2.0.2-50618 on a workstation no longer connects to this server.

Suggestions, help, face saving quick maneuvers?

thx

Bill

[sbeaver]

Log on to the ESX server is question. Make sure autostart and autostop are disabled and restart these services

service vmware-vpxa restart

service mgmt-vmware restart

Steve Beaver

VMTN Forum Moderator

*Virtualization is a journey, not a project.*

[Esys]

Thank you Steve. I read the post "Failed to install service agent after upgrade to 2.0.1" after posting my message. While the restart didn't fix the issue, copying and installing vpx-upgrade-esx-6-linux-61426 from the VCMS server, then restarting the mgmt service did the trick.

Thanks

Bill

[sbeaver]

Ok great glad things got worked out