Discovery Error = No credential found for type [Windows]

[Michele19]

Hi

we recently upgraded our sub-prod instances to Rome from Quebec.  I have tried to discover a windows server that was discovered before the upgrade and got the following error: No credential found for type [Windows]

Please see my attachment for the details of what I have tried.

[Kieran Anson]

Hi Michele,

Have you run through enabling debugging to retrieve further logging information?

Credentials/Permissions troubleshooting on Discovery, Service Mapping, Orchestration.

[Michele19]

yes, I did try the ones I had access to such as

1. test credentials - this was successful

2. I was able to login to the target server with the discovery credentials - successful

3. Collecting MID Server Debug logs- unable to select mid.log.level parameter, new screen was just a text box for value

4. Powershell WMI query - didn't bother as I was able to login to the target server from the mid server host.

I have eliminated the network as a problem as well as the credentials.

The same credentials work on another sub-prod instance.  See my attachment.

What configuration is missing on one instance to make it behave differently?  I have checked the related lists between the successful instance and the unsuccesful instance, there are some minor difference in the capabilities but they do not relate to windows servers - such as Ansible, AWS, Chef...  WMI and PowerShell are a capability in both.

 

[Steven Coda]

Michele,  Have you been able to obtain a resolution on this since you posted this?  I have the same issue since we just upgraded to Quebec Patch 8 and was wondering if you had a solution you can post.  Thanks.

[Michele19]

I raised a case with support and they fixed it.  This is the related KB

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0719158

Here is what they did:

Discovery with same credential, target and MID server is not working
ECC Queue Input of Windows Classify probe shows "credentials_attempted":[] (no credential tried)
In Agent Log, we can see error below:
10/15/21 16:27:12 (380)

Worker-Interactive:PowershellProbe-dd6747c0db9b3010a4c895d7f496192b

SEVERE *** ERROR *** An error occurred while decrypting credentials from instance

com.snc.automation_common.integration.exceptions.AutomationIOException:

Unable to retrieve data from instance. This MID may not be validated.

Above Symptom confirms an issue which is usually caused by orphan / corrupted credentials.

I have deleted the orphan credentials, and discovery is now working fine

Hope this helps.