A problem was encountered while registering the provider
.”/var/log/vmware/vmware-sps/sps.log
shows the following error:SNI = null
multiVcSupported = true
port = null
serviceHost = null
vcGuid = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
The vcGuid
appeared in uppercase
letters which is the cause of the failure.
instance.cfg
" and "vpxd-service-spec.prop
" to use lowercase letters for the vCenter GUID. /etc/vmware-vpx/instance.cfg
", update all uppercase letters to lowercase letters. # vi /etc/vmware-vpx/instance.cfg
Change line "instanceUuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" to "instanceUuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
/etc/vmware-vpx/firstboot/vpxd-service-spec.prop
", update all uppercase letters to lowercase letters. # vi /etc/vmware-vpx/firstboot/vpxd-service-spec.prop
Change line "cmreg.serviceid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX" to "cmreg.serviceid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
lsdoctor -r
" (option 3).lsdoctor
tool from KB320837 and upload it into vCenterpython lsdoctor.py -r
"Fix license tied to the vCenter
a.Record current vCenter license key.
b.Obtain current vCenter LDU ID with command: # /usr/lib/vmware-vmafd/bin/vmafd-cli get-ldu --server-name localhost
yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy
c.Remove license associated with current LDU ID by command:
#/opt/likewise/bin/ldapdelete -H ldap://localhost -D "cn=administrator,cn=users,dc=vsphere,dc=local" -w "password" "cn=AssetEntity_<XXXXX>-<yyyyyyyy>,cn=LicenseService,cn=Services,dc=vsphere,dc=local"
Notes:
dc=vsphere,dc=local
to reflect the environment's SSO domainyyyyyyyy
with the LDU ID from above Step 4.bd. If the above step (c) fails to remove the license with an error similar to:
ldap_delete: No such object (32) additional info: (9703)((MDB_NOTFOUND: No matching key/data pair found
Remove the vCenter license using KB - vCenter 6.x/7.x/8.x incorrectly displays the amount of licenses in use by ESXi hosts
e. Reboot vCenter and re-assign license.
If SRM is used in the environment, please export the configuration data. When the vCenter GUID changes, SRM will break so we will need to unregister both of them then re-register and import the xml.