Hi Stefan,

ldapdelete might be one of the options to delete invalid/duplicate service registrations. Another way to remove them is using lstool

List service registrations: /usr/lib/vmware-lookupsvc/tools/lstool.py list --url https://localhost/lookupservice/sdk > /tmp/services.txt

This will list the service name and it's ID. For example:

Service Type: vcenterserver

Service ID: 1dbc3e9f-626d-4314-8731-ca744a0d9f4b

Once you have the service ID, you can run following command to un-register(Update service ID, username and password)

/usr/lib/vmware-lookupsvc/tools/lstool.py unregister --url http://localhost:7080/lookupservice/sdk --id 6ae3bf1a-9318-4a33-b2cb-d2eaa7a306c5 --user 'administrator@vsphere.local' --password 'VMware123!' --no-check-cert 

Hi,

yes that sounds much easyer than with ldapdelete.

But the service ID i don't need to query, because look in the log i posted. For example:

Duplicate service URLs detected for URL http://localhost:10102/certificateauthority and serviceIds f4f49eca-389a-4cd4-9539-7b016cd9b387\com.vmware.certificateauthority.vapi and f50da208-1be7-4752-8cda-8651fb94f4bc\com.vmware.certificateauthority.vapi. Service f4f49eca-389a-4cd4-9539-7b016cd9b387\com.vmware.certificateauthority.vapi will not be registered.

So i have unregistered the ID which wasn't registered...

I also made a query before, but the services are listed twice, so how should i decide what service id to delete? I decided to follow the log, to delete the not registered service id.

You can use lsdoctor with option '--l'

If you do not have external solutions integrated you may try '--r' option

==> https://kb.vmware.com/s/article/80469

I have the NetApp Virtual Storage Console installed -> VASA Provider for the VVOLs.

So the other solution seems to be the better solution...

But for a small environment with nothing extra this looks simple.

Hi,

and again i have 2 messages in my VCSA:

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:7080/tokenservice/vapi.
Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:12020/lcm/api.

This time a took a closer look to the tool recommend by @Vijay2027 and so i run: "python ./lsdoctor.py -r"

I used the option 3 to "Replace individual service."

Here i get a list of all services and then i was able to select the "tokenservice", and this was the result:

You have chosen to replace the service: tokenservice -- Continue?[y/n]: y
2021-04-18T09:48:09 INFO unregisterServiceType: Unregistered 607d4ad1-7ac3-49db-a17e-1deb660f4631
2021-04-18T09:48:09 INFO unregisterServiceType: Unregistered cef7ec77-cc98-4bd5-81a0-e96d3d142688
2021-04-18T09:48:09 INFO rebuild_single_service: Registered service: tokenservice with service ID: 607d4ad1-7ac3-49db-a17e-1deb660f4631

2 services unregistered and one is registered, perfect. The same with the other service:

You have chosen to replace the service: cis.vlcm -- Continue?[y/n]: y
2021-04-18T09:49:29 INFO unregisterServiceType: Unregistered e5df686b-7cdb-4de2-9ac5-927bd6e481ec
2021-04-18T09:49:29 INFO unregisterServiceType: Unregistered 9a29af6f-22ea-473e-905d-131b1aee6104
2021-04-18T09:49:29 INFO rebuild_single_service: Registered service: cis.vlcm with service ID: 7a7f5b32-ed67-4778-bb25-4c077ef0f67e

So this is the best and safe way to solve that problem. And i think even if i have external solutions integrated it must work, because i don't "rebuild" all services, i rebuild only the selected service.

And after a few minutes the messages in the VCSA services is gone.

The other way, suggested by @ashilkrishnan, here is the problem, how can i decide which of the two registrations is the correct one? This is more complex...

So thank you, @Vijay2027 for the link to the KB!

Kind regards
Stefan

Very strange, yesterday i installed a vCenter Patch and today again:

Incorrect service registration found in Lookup Service. Multiple services registered on same URL - http://localhost:12020/lcm/api.

But only this one...

Now i must wait for a new version of the lsdoctor, when there is a template for 7.0.2.00100 included...

Thanks for this.  Solved my variant of this issue.  I opted for replacing individual service and picked my service. 

option 3. Replace individual service.
picked appropriate file
picked appropriate service (18 - trustmanagement in my case)

Rebooted and all was well.