Vcenter not accessible after upgrading from 5.5 0b to 5.5 2b

Hello, I updated my vcenter last night successfully from 5.5 0b to 5.5 2b, however I couldn't connect via vsphere client to VCenter after the upgrade, I checked all services running. I tried connecting then via vsphere web client and found no inventory. I had a clone as backup plan that I turned on to keep the environment running and services available.
I have now powered down original Vcenter and need to troubleshoot this issue, any help?
between after I successfully installed vcenter, I moved on to upgrade update manager and I was asked at some point to enter credentials, my colleague that keep login info attempted 3 times locking the account, not sure this has any impact on vcenter not being accessible.



I updated my vcenter last night successfully from 5.5 0b to 5.5 2b



however I couldn't connect via vsphere client to VCenter after the upgrade


Does not seem like a successful upgrade, if it was successful you would be able to connect!

I'm a little confused as to where you are now

1. Can you now connect to vCenter Server via vSphere Client and Web Client?



I updated my vcenter last night successfully from 5.5 0b to 5.5 2b



however I couldn't connect via vsphere client to VCenter after the upgrade


Does not seem like a successful upgrade, if it was successful you would be able to connect!

I'm a little confused as to where you are now

1. Can you now connect to vCenter Server via vSphere Client and Web Client?



Hi Andrew, was not able to connect with vsphere client, when I did with web client no inventory found. at the moment i'm running on the clone I had in case of failure. I have powered down original Vcenter, Vcenter version on original server has been upgraded to 5.5 2b( that's why I used "successfully") but unable to connect.



Upgrades are always terrible, and sometimes break.

I would copy your clone, and try again. It would seem permissions have broken.

We have for example a number of vCenter 5.5 installations, that since updates have been applied have broken VMware vCenter Orchestrator and Ruby vSphere Console - for unknown reasons, which are still working with VMware Support with as too why!



Check this article for known Issues with vCenter Server 5.5 Update 2b : https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-55u2b-release-notes.html#knownissues



It was UPDATE and not UPGRADE.
It looks like vpxd (vcenter server) is not started.

Share this

Related Posts

There was an error in this gadget