no credential would validate for http:10.xx.xx.xx sdk error in VMWare discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā10-19-2018 09:25 AM
no credential would validate for http:10.xx.xx.xx sdk error in VMWare discovery, when we test credential using discovery affinity IP address it is successful, but when we run discovery it shows the error no credential would validate for http:10.xx.xx.xx sdk .... What s the reason?
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā01-18-2019 12:04 PM
Did you ever resolve this issue? I am getting the same error message.
Kindly,
Steve Croft

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā07-31-2019 03:09 PM
Hi scroft,
Did you resolve this issue ?? I am going through the same error.
If soo can you please share workaround for this issue.
Thanks in advance!
Karim.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā08-07-2019 02:32 AM
Hi scroft,
Did you get a chance to check this and fix the issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā07-31-2019 10:15 PM
Can you please delete the IP affinity rules manually from discovery_credentials.
Validate credentials
Try discovery. It should work.
Delete 'Discovery IP Affinity' from discovery_credentials.
If this step doesn't work check the IP affinity entries from 'dscy_credentials_affinity' table and delete those entries which uses the Ip mentioned in credential.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ā02-20-2020 01:28 AM
Hi,
We just discovered a similar problem and after an hour of scrabbling around my colleague discovered that the Credential was affiliated with a "unknown" MID server, i.e. just a numeric reference! Either reassociate the Credential to a known MID Server or select All MID Servers!
We had move the credentials via an export and reimported but lost the affiliaten along the way!
Regards
Andrew