Unbale to get the access to this KB, Can anyone help me with the information in that Kb
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @community, recently I have encountered with an Issue Regarding the windows Server Discovery in Dev instance, we recently upgraded our sub-prod instances to Australia 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],
I was going through some community issues, found the similar one but the KB attached there is not opening,
I'm not sure whether this is removed or what or updated, can someone help me with this,
I'm also attaching the issue that I encountered with a similar post in community
Discovery Error = No credential found for type [Wi... - ServiceNow Community
https:/support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0719158__;!!Hs6A79YYbFfQ525liA!dEfu2yLgzwWddZtgn7XXxJYdPQX1FORkwIVNCyIfbPVzoaIXx9J_38Pi6ewKkIRdvG4PTMk$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
hi @naziyabegum ,
I too can't access the article, but I got what will be causing this issue..
Because of your recent upgrade there might be the chances you are credentials are corrupted..
You can check these in your discovery and mid server logs.
Discovery Log:
Navigate to All > Discovery schedule >Quick discovery of one ip >Open the ECC queue > Open the input classifier probe and analyze the error, Whether is this due to creds.,
Mid server Log
Open/ login to the Vmware where mid server is installed, Navigate to the folder where mid server is installed and open the agent log files, there also if you see any kind of errors related to credentials(Error occurred while decrypting credentials from instance). This conforms your creds is being corrupted..
Action Needs to taken..
Delete the existing creds which seems broken(Not Working) & Create those credentials agian., Redo the discovery this will work well.. If it's not feel free to raise a high ticket with ServiceNow..
If you find this helpful., Please Mark it as Helpful and Please Accept the solution..
Best Regards,
SIVASANKARI S
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @sivasankaris Thanks for the Response, this is what I'm seeing in the input classifier probe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @naziyabegum ,
Before trying the discovery , can you test your credentials..