The vSphere Web Client may display the following error:
or
Additionally, objects such as hosts or VMs are not displayed in the vSphere Web Client.
These errors usually occur with a re-installation or upgrade of vCenter Server, where the vCenter Server is registered to the same vSphere SSO more than once.
The faulty registration needs to be resolved by unregistered all duplicate vCenter Server instances from vSphere SSO, so only the correct registrations remain.
You will have to unregister all incorrect vCenter Server registrations from vSphere SSO. To determine and unregister these entries, follow the steps outlined below.
Be sure to select the instructions for the correct vSphere version. The instructions assume default installation paths. If vCenter was installed in a location other than the default, be sure to adjust accordingly.
The formatting of ServiceID will be different between versions of vSphere, but if you've upgraded vCenter Server, it may be possible older notations are used among newer ones. Be sure to exactly match the ServiceID, even if the current version of vSphere is different.
First, we have to retrieve a list of services currently registered with the vSphere SSO.
set JAVA_HOME=C:\Program Files\VMware\Infrastructure\jre
set JAVA_HOME=C:\Program Files\Common Files\VMware\VMware vCenter Server - Java Components
ssolscli.cmd listServices https://vCenter_Single_Sign-on_FQDN:7444/lookupservice/sdk > c:\sso_services.txt
The output of the temporary file should be similar to:
Verify the contents of the file. If there's only one vCenter Server (i.e. non-linked configuration), there should be only one vCenter Server registered with vSphere SSO. Also, if it is a linked configuration, there should only be one registration per vCenter Server. You need to unregister each invalid vCenter Server (or duplicate of a vCenter Server), until there's only one registration per vCenter Server registered with SSO.
You can retrieve and identify vCenter Servers by checking their ServiceID in the config file vpxd.cfg (location: %PROGRAMDATA%\VMware\VMware VirtualCenter). The file should look similar to this:
<lookupService>
<serviceId>{9300C2AC-4D97-4191-8EB1-387D9823E6E3}:23</serviceId>
</lookupService>
<solutionUser>
<name>vCenterServer_2013.02.28_170324</name>
</solutionUser>
Once you verified the ServiceIDs to be unregistered from the vSphere SSO, continue to unregister each, following the procedure outlined below. These steps need to be done for each of the services that need to be unregistered from vSphere SSO.
ssolscli unregisterService -d https://vCenter_Single_Sign-On_FQDN:7444/lookupservice/sdk -u admin@system-domain -p SSO_Password -si c:\serviceID.txt
ssolscli unregisterService -d https://vCenter_Single_Sign-On_FQDN:7444/lookupservice/sdk -u administrator@vsphere.local -p SSO_Password -si c:\serviceID.txt
If the correct services were unregistered, try logging back in to the vsphere Web Client. Verify that the error message no longer appears.
If the error still remains, you may have to replace the SSL certificates:
If the issue is still not resolved, you may have to completely uninstall and re-install vMWare vCenter.
Although the basic are similar, vSphere 6.0 has been redesigned from the ground up, and uses a different approach. The steps are similar whether you are running the Windows version of vSphere 6.0, or running the appliance.
Retrieve a list of all services registered with Platform Services Controller.
"%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\lstool.py" list --url http://localhost:7080/lookupservice/sdk --type vcenterserver > c:\psc_services.txt
The output of the temporary file should be something similar to this:
Name: AboutInfo.vpx.name
Description: AboutInfo.vpx.name
Service Product: com.vmware.cis
Service Type: vcenterserver
Service ID: 608AF497-B198-40D1-9855-545533A488AF
Site ID: home-office
Node ID: 86ca3bf1-9201-11e3-8f19-000c29562ae2
Owner ID: vpxd-86ca3bf1-9201-11e3-8f19-000c29562ae2@vsphere.local
Version: 6.0
Endpoints:
Type: com.vmware.cis.workflow
Protocol: vmomi
URL: http://vCenter1.domain.local:8088
SSL trust:
Name: AboutInfo.vpx.name
Description: AboutInfo.vpx.name
Service Product: com.vmware.cis
Service Type: vcenterserver
Service ID: 6ae3bf1a-9318-4a33-b2cb-d2eaa7a306c5
Site ID: home-office
Node ID: 86ca3bf1-9201-11e3-8f19-000c29562ae2
Owner ID: vpxd-bf048b3a-231e-40b0-96ea-e5792f7fa65b@vsphere.local
Version: 6.0
Endpoints:
Type: com.vmware.cis.workflow
Protocol: vmomi
URL: http://vCenter2.domain.local:8088
SSL trust:
Name: vCenterService
Description: vCenter Server
Service Product: com.vmware.cis
Service Type: vcenterserver
Service ID: default-first-site:01c98f18-770a-41c2-a967-b7a4b574cad2
Site ID: default-first-site
Owner ID: vCenterServer_2015.04.20_143355@vsphere.local
Version: 5.5
Endpoints:
Type: com.vmware.vim
Protocol: vmomi
URL: https://Legacy_vCenter.domain.local:443/sdk
To unregister the duplicate service:
"%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\lstool.py" unregister --url http://localhost:7080/lookupservice/sdk --id ServiceID from Step 4 --user "administrator@vsphere.local" --password "administrator_password" --no-check-cert
If the duplicate services were unregistered, try logging back in to the vsphere Web Client. Verify that the error message no longer appears.
Retrieve a list of all services registered with Platform Services Controller.
shell.set --enabled true
shell
/usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vcenterserver > /tmp/psc_services.txt
The output of the temporary file should be something similar to this:
Name: AboutInfo.vpx.name
Description: AboutInfo.vpx.name
Service Product: com.vmware.cis
Service Type: vcenterserver
Service ID: 1dbc3e9f-626d-4314-8731-ca744a0d9f4b
Site ID: home
Node ID: d3eba55a-d4df-11e4-b3f7-000c2987c143
Owner ID: vpxd-2752b8d1-e68b-49f8-8c92-ce3f042bf487@vsphere.local
Version: 6.0
Endpoints:
Type: com.vmware.cis.workflow
Protocol: vmomi
URL: http://vcsa2.domain.local:8088
Name: AboutInfo.vpx.name
Description: AboutInfo.vpx.name
Service Product: com.vmware.cis
Service Type: vcenterserver
Service ID: 6ae3bf1a-9318-4a33-b2cb-d2eaa7a306c5
Site ID: home
Node ID: 44b05c52-d4d3-11e4-830b-000c29a0e10e
Owner ID: vpxd-bf048b3a-231e-40b0-96ea-e5792f7fa65b@vsphere.local
Version: 6.0
Endpoints:
Type: com.vmware.cis.workflow
Protocol: vmomi
URL: http://vcsa1.domain.local:8088
To unregister the duplicate service endpoint, run this command in the shell (on the Platform Service Controller):
/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url http://localhost:7080/lookupservice/sdk --id ServiceID --user 'administrator@vsphere.local' --password 'administrator_password' --no-check-cert
If the duplicate services were unregistered, try logging back in to the vsphere Web Client. Verify that the error message no longer appears.
« ‹ | October 2024 | › » | ||||
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
1 | 2 | 3 | 4 | 5 | ||
6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 14 | 15 | 16 | 17 | 18 | 19 |
20 | 21 | 22 | 23 | 24 | 25 | 26 |
27 | 28 | 29 | 30 | 31 |