VMware Cloud Community

Web Client Does Not Match vSphere Client

I've got a strange one here.  I have vCenter Appliance 5.5 and have primarily been using the vSphere client.  I decided to log into the Web client today and noticed that it does not match what I see in the vSphere client.  The Web client is still showing data from the first week I built the VCSA.  It does not show any of the new hosts, clusters, or VMs that I have added since then (I've added over 100 objects since then).  What's even more strange is that I'm using the same Active Directory account on both Web client and vSphere client.

Has anyone encountered this?  If so, what was your solution(s)?  Thanks in advance.

2 Replies
VMware Employee
VMware Employee

Check this thread


Sounds like a similar issue.

Abhilash B
LinkedIn : https://www.linkedin.com/in/abhilashhb/

0 Kudos
Hot Shot
Hot Shot

To resolve this issue, recreate the vCenter Inventory Service database and re-register it to vCenter Server Appliance.

To recreate the vCenter Inventory Service database and to and re-register it to vCenter Server Appliance:

  1. Connect to the vCenter Server Appliance using SSH or a virtual machine console and log in as the root user.
  2. Run these commands:

    # service vmware-inventoryservice stop
    # 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

    Note: The database password is changeme.

  3. Ensure that the vCenter Inventory Service is started by running this command:

    # service vmware-inventoryservice start

  4. To re-register the vCenter Inventory Service to vCenter Server Appliance, run these commands in order depending on your version:

    vCenter Server Appliance 5.0:

    # /usr/lib/vmware-vpx/inventoryservice/scripts/ds-invoke.sh -Dvim.logdir=/var/log/vmware/vpx/inventoryservice-registration com.vmware.vim.dataservices.provider.util.SetupLocalService -vcurlhttps://vcenter_name_or_ip:443 /sdk/vimService -providercfg file:/usr/lib/vmware-vpx/inventoryservice/lib/server/config/vc-provider-registration.xml -servicecfg /usr/lib/vmware-vpx/inventoryservice/lib/server/config/dataservice.properties

    # service vmware-vpxd restart

    vCenter Server Appliance 5.1:

    # /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://vcenter_name_or_ip:7444/lookupservice/sdk -isurl https://vcenter_name_or_ip:10443 -vcurl https://vcenter_name_or_ip/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

    vCenter Server Appliance 5.5:

    # vcenterhost=vchost.mydomain.com

    Note: The above command sets the vcenterhost= to the FQDN of your vCenter Server Appliance. To obtain the FQDN of your vCenter Server Appliance, run the command hostname.

    # /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

Best regards

Yours, Oscar