Discovery Credential Issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2020 04:45 PM
Appreciate some assistance from someone more knowledgeable than myself.
The ECC queue input payload for some workstations shows credential issues when trying to classify. SEE BELOW
WMI:classify probe shows. (Authentication failure with the local MID server service credential.</error><error>Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: The RPC server is unavailable. but differ depending on the probe used). I have found that this could be Windows firewall blocking this service. Is this assumption correct?
HTTP Classy Probe shows: (error="No credential found for type [BASIC_AUTH]" probe_time="0" result_code="41). This is an error I'm not familiar with?
Learning how to troubleshoot discovery. Mine is a mess.
Thanks
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2020 05:00 PM
Are you able to get any other sort of data via discovery?
Many organizations will not allow a random computer on the network (in this case, your MID Server host) to access other hosts and get WMI information.
Most commonly, to fix the above, you'll need to:
- Get a windows network account on the domain, typically a "service account"
- Have the windows/domain administrators grant that account the rights to access the machines you are trying to discover via SNMP/WMI/any other protocols you need to use
- Log in to your machine running the MID Server and set it to run the MID Server process *as* the windows network account from step 1. Details on how to do that are here: https://docs.servicenow.com/bundle/london-servicenow-platform/page/product/mid-server/task/t_ConfigM...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2020 05:03 PM
It could be a windows firewall..but there is also the most likely opportunity that you dont have correct credentials. Take a look at the troubleshooting section of my best practice document, that and lots of videos Are available to help compliment your discovery training.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2020 11:59 PM
Hi,
Doug said it all.
To solve above errors i will just one one thing and that is this articles can help you alot to debug
https://hi.service-now.com/kb_view.do?sysparm_article=KB0564282
https://hi.service-now.com/kb_view.do?sysparm_article=KB0549830
Thanks,
Ashutosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2020 04:59 PM
Thanks all for the assist. Discovery seems to be a beast and I've got my work cut out.
Much appreciated