Hi,
Upgraded our vCenter to 5.1 U1 from 4.1 last week.
After installing SSO, Inventory service and upgrading the vCenter all looks OK until I try to use the vsphere web client.
I get the following error and there are no resources in the client:
"Client is not authenticated to VMware Inventory Service - https://myserverFQDN:10443"
I have already uninstalled the inventory service and the web client and reinstalled both several times.
I have also re-registering the inventory service with no change.
Any ideas or suggestions would be appreciated.
Thanks in Advance,
HG.
Hi,
Ended up working with support to resolve this. Ended up removing all components (inventory, SSO, vCenter, web client) and re-installing. I would have hoped there would have been an easier way to get these products to interact - but at least it is working now.
Thanks,
HG
See if the post by dlund in this thread helps:
http://communities.vmware.com/thread/421398?start=0&tstart=0
Regards
Girish
Hi,
Thanks for the information.
I had referenced this item in my attempts to resolve the problem but had not tried re-initializing the IS database. Think I will give that a shot this weekend and post the results. Removing, re-installing and re-registering have not worked.
Have a great weekend!
HG
Hi,
Ended up working with support to resolve this. Ended up removing all components (inventory, SSO, vCenter, web client) and re-installing. I would have hoped there would have been an easier way to get these products to interact - but at least it is working now.
Thanks,
HG
I just had a similar issue, tried everything I could find. Was pointed to this link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203362.... That is all well and good, but I have the appliance, so it is Linux based. Deleted the inventory service user and from there was lost. Browsed out in the file system using WinSCP and found a promising script located at "/usr/lib/vmware-vpx/inventoryservice/scripts/ds-register-sso.sh" This recreated the service account user, I was then able to run the commands to fix the problem.
rm -rf /storage/db/inventoryservice/data
/usr/lib/vmware-vpx/inventoryservice/scripts/ds-invoke.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice com.vmware.vim.dataservices.CreateDb /storage/db/inventoryservice/data changeme default changeme
service vmware-inventoryservice start
vcenterhost={FQDN}
/usr/lib/vmware-vpx/inventoryservice-registration/vcregtool.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice-registration com.vmware.vim.dataservices.vcregtool.RegisterVC -action register -lookupserviceurl https://$vcenterhost:7444/lookupservice/sdk -isurl https://$vcenterhost:10443 -vcurl https://$vcenterhost/sdk/vimService -vccert /etc/vmware-vpx/ssl/rui.crt -vcprivkey /etc/vmware-vpx/ssl/rui.key -vcinstancecfg /etc/vmware-vpx/instance.cfg -vcendpointsdir /usr/lib/vmware-vpx/endpoints -vcextensionsdir /usr/lib/vmware-vpx/extensions
service vmware-vpxd restart
The following KB resolved the issue for me:
It lists the commands applicable to multiple versions of the Vcenter server appliance.