Empty inventory in vSphere 6.7 H5 client followed by "Unexpected error encountered while retrieving VC summary data"

Products

• VMware vCenter Server

Issue/Introduction

• Empty inventory in vSphere 6.7 html5 (H5) client after log in, followed by one or all of the below messages:

"dashboard.error.hosts_information"
"Unexpected error encountered while retrieving VC summary data"

• In /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log, you will see entries similar to,

Found a VC containing 0 service endpoints: https://vCenter_name:443/sdk

Environment

VMware vCenter Server 6.7.x

Cause

This is observed to be from stale 5.x vCenterServer service registrations available in lookupservice.

Resolution

This issue is resolved in vCenter Server 6.7 0a.

Workaround:

1. Identify 5.x vCenter service registrations:
   
   • On vCSA:
   /usr/lib/vmidentity/tools/scripts/lstool.py list --url https://localhost/lookupservice/sdk --no-check-cert|grep -A 6 "Service Type: vcenterserver"
   • On Windows VC (Use powershell ):
    
   &$Env:VMWARE_PYTHON_BIN "$Env:VMWARE_CIS_HOME\VMware Identity Services\lstool\scripts\lstool.py" list --url https://localhost/lookupservice/sdk --no-check-cert |sls "Service Type: vcenterserver" -Context 0,6
   
   Example for output:
           Service Type: vcenterserver
           Service ID: default-first-site:98a077d1-0336-4766-a2b5-60a9b038e578
           Site ID: default-first-site
           Owner ID: vCenterServer_2013.12.11_105415@System-Domain
           Version: 5.1
           Endpoints:
                   Type: com.vmware.vim
   --
           Service Type: vcenterserver
           Service ID: B4257C45-9D4B-4EAB-B519-770F1200B784
           Site ID: default-first-site
           Node ID: 16f6bb11-6249-11e3-8547-005056bc000a
           Owner ID: [email protected]
           Version: 6.7
           Endpoints:
   • Note down "Service ID" field  of vCenterserver registration with "version:" field 5.x.
   Note: Usually the 5.x registrations are prefixed with site name, use the entire string shown after "Service ID:" including site name in commands used at step 2.
   
   

2. Based on the above result create the following un-register command for 5.x service clean up:

• On VCSA:

/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url https://localhost/lookupservice/sdk --user [email protected] --password 'PASSWORD' --id <5.x ID noted in step 1> --no-check-cert

Example:
/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url https://localhost/lookupservice/sdk --user [email protected] --password 'PASSWORD' --id default-first-site:98a077d1-0336-4766-a2b5-60a9b038e578 --no-check-cert

• On Windows VC :

 

If using command prompt:

"%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\lstool.py" unregister --url https://localhost/lookupservice/sdk --user [email protected] --password 'PASSWORD' --id <5.x ID noted in step 1> --no-check-cert

• If using powershell:

&$Env:VMWARE_PYTHON_BIN "$Env:VMWARE_CIS_HOME\VMware Identity Services\lstool\scripts\lstool.py" unregister --url https://localhost/lookupservice/sdk --user [email protected] --password 'PASSWORD' --id <5.x ID noted in step 1> --no-check-cert

Example
If using command prompt:

 "%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\lstool.py" unregister --url https://localhost/lookupservice/sdk --user "[email protected]" --password 'PASSWORD' --id default-first-site:98a077d1-0336-4766-a2b5-60a9b038e578 --no-check-cert

If using powershell:
&$Env:VMWARE_PYTHON_BIN "$Env:VMWARE_CIS_HOME\VMware Identity Services\lstool\scripts\lstool.py" unregister --url https://localhost/lookupservice/sdk --user "[email protected]" --password 'PASSWORD' --id default-first-site:98a077d1-0336-4766-a2b5-60a9b038e578 --no-check-cert

3. Perform the un-register operation using the command constructed in Step 2.