[SM] Specific MID server throws credential related issue if picked up for Service Mapping from MID Cluster - Support and Troubleshooting

[SM] Specific MID server throws credential related issue if picked up for Service Mapping from MID Cluster Issue A specific MID server from the MID cluster throws WMI (or) SSH credentials related issue on some Windows or Linux nodes during Horizontal and Top-Down discovery. Failed to execute WMI command on host XXXXXX command: %SystemRoot%\system32\netstat -a -n -o | %SystemRoot%\system32\findstr /R ":1433" error message: No credential found for type [Windows]. where XXXXX- ip address Release Any release. Cause The affected MID Server encryption keys do not match and are no longer valid due to which the credential couldn't be validated during discovery. Resolution Validate the list of MID Servers in the MID Cluster and check if the affected MID server has any "Unresolved Issues". The probable reason behind the credential issue during the Horizontal and Top-Down discovery could be due to " UpdatePublicKey " with the affected MID server. i.e. under the "Unresolved Issue" of the MID server Related links could see the error " MID Server encryption keys do not match and are no longer valid. To restore proper functionality, invalidate and re-validate the MID Server ." Resolve this error by Invalidating and Re-validating the affected MID server and post that discovery succeeds and there won't be any WMI or SSH credentials errors seen during the discovery. (On the MID Server form you can see " Invalidate " OR " Validate " UI action under related links)