After upgrade vCenter 5.5 U2, inventory is empty

[SupportAzerty]

Hi,

I had yesterday upgrade my vCenter 5.1 to vCenter 5.5 U2.

I use SImple Install and no error displaying.

I cannot login with vSphere Client:

I can login with Web Client, but Inventory is empty and i have this error:

impossible de créer l'objet géré pour - urn:vmomi:TaskManager:TaskManager:FDA956DA-E433-4AD1-9DFC-94E68A16F653.

Impossible de se connecter à un ou plusieurs systèmes vCenter Server :

https://SRV-VCENTER.xxx.local:443/sdk

IN attachment, ds.log (inventory service) and vpxd.log

I have search on the web, found equal issue but nothing can correct my problem.

I have also open support request but no reply for moment...

Any idea ?

[Alistar]

Hello, from the error message itself it seems to be something wrong with the domain authentication - see the below lines:

2014-11-12T16:14:49.537+01:00 [09928 error '[SSO][SsoAdminFacadeImpl]'] [RefreshSsoToken] AcquireToken exception: Authentication failed: Invalid credentials

2014-11-12T16:14:49.597+01:00 [09928 error '[SSO]'] [UserDirectorySso] GetUserInfo exception: class Vmacore::Authorize::AuthUserUnresolvedException(User VSPHERE.LOCAL\Administrator, cause: class Vpx::Common::Sso::DomainUnresolvedException(RemoteGetDomainNames RuntimeServiceFault exception: sso.fault.RuntimeServiceFault))

2014-11-12T16:14:49.615+01:00 [09928 error 'authvpxdAuthorize'] Failed to set admin permission on SSO admin as user validation error

Seems like the Inventory Service has lost the credentials/domain trust - it can not reslove the domain. Are your DNS servers set up on your server where the Inventory Services reside? Were there any changes on your DNS IPs? Please double-check and try

ipconfig /flushdns

ipconfig /refreshdns

on the server once you have double-checked the DNS servers can communciate properly.

[Virtualinfra]

Got into same KB says to reinstall VC as a work around

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=209387...

did you resolve without reinstall

[jpmoock]

Ran into this same problem going from VC 5.1 Update 1 to VC 5.5 Update 2e.  We have a multi-site environment with SRM and dvSwitches.  The vCenter at the recovery site was the only one impacted.  We were able to uninstall/reinstall without impacting the dvSwitches and were able to then successfully upgrade the remaining components.