Error while Discovery : Authentication failure with the local MID server service credential.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-08-2015 05:51 AM
Hi All,
I am trying to discover windows and unix devices available in my network.
I have created MIDserver and started discovery using configuration items. I have even set behavior with IP range in my network.
And then I started Discovery by clicking Discovery Now.
After this I got all the devices in my network with their IP Address and few activity as Active, couldn't classify and few activity as Alive, not classified.
And when I checked Discovery log, I found warning with messages like
"Authentication failure with the local MID server service credential." for Windows devices,
"Failed to access target system. Please check credentials and firewall settings on the target system to ensure accessibility: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))".
and for UNIX
"SSH authentication or connection failure" and
And only my device was discovered properly but remaining devices are not discovered which are in the network.
Please help me out step by step as I am new to this and I want to discover all devices in my network and check for the further process.
Thank You.
- Labels:
-
Discovery
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-08-2015 02:27 PM
When discovery goes to discover a device, it needs valid credentials to do so.
The Windows error you're receiving is because the MID server is trying to authenticate against the machine you're discovering using the credentials that the MID Server service is running as. If this account has no access, it will fail. You can overcome this by either A) Running the MID Server Service as a user that has the appropriate permissions or B) Adding the appropriate credentials to the Credentials table in Service Now.
The SSH authentication error is telling us the same story, we have no valid credentials to log into the target host. To fix this you must add valid SSH credentials to the Credentials table in service now, either using a username/password combo or an SSH private key.
These links may further help.
http://wiki.servicenow.com/index.php?title=Discovery_Troubleshooting_-_Classification
Advanced Discovery Troubleshooting - WMI
If my response answered your question, please mark this as answered so other people may find the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2015 03:53 AM
Hi,
Thank you for the reply. As per you said in your reply, I tried accordingly, but still I am unable to discover devices in the network.
I am confused in what actual credentials are required in MID Server Service and Credentials table.
I have set the device credentials in the credential table. But still it is giving me same error "Authentication failure with the local MID server service credential." for Windows devices.
I even gone through the links given by you regarding this but I was unable to find the proper steps to discover devices.
I am even confused in windows domain requirements. I even read about Powershell, is it required?
Please guide me more step by step. It would more helpful if you will tell me each step with exact requirement for a single device discovery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-12-2015 10:49 AM
Gaurav,
Have you checked this page out..
5-part series on Troubleshooting a failed Discovery
Or reviewed section #9 of a legacy but still fitting troubleshooting..
Also, have you had the chance to take discovery training?
ServiceNow | Training | Configuration Item Identification, Implement ServiceNow Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-27-2016 06:05 AM
For LINUX: what are the machines u want to discover check whether SSH is installed or not in machines.
For WINDOWS: check 1) user must be ADMIN
2)WMI connnection is working properly or not.