Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

Discovery Issue Getting error

Ashish Kathait
Tera Contributor

MID Server mid.server.ServiceNow00001 is not a suitable MID because it does not have the following capabilities [{Capability: Nmap, value: null}]

4 REPLIES 4

shubhamseth
Giga Sage

@Ashish Kathait @What action you are performing and exactly on what phase you are getting this error? 

are you running simple discovery? Or trying something else. 

✔️ If this solves your issue, please mark it as Correct.


✔️ If you found it helpful, please mark it as Helpful.



Shubham Jain


You can see the screenshot shared all the phases, but I think not able to classify. Active, couldn't classify, now finished

@Ashish Kathait  as per your snap, you are trying to run Credential less discovery and you do not have Namp enabled or installed in MID server hence you are getting this error? 

do you really want to run credential less discovery? If yes, please go to mid server respectively and there would be option to enable nmap or credential less discovery and then try. Otherwise there itself you will have option to disable to credential less discovery. 

let me know if this helps! 

 

✔️ If this solves your issue, please mark it as Correct.


✔️ If you found it helpful, please mark it as Helpful.



Shubham Jain


doug_schulze
ServiceNow Employee

If you havent deployed nmap to do credentialless discovery then you have the sys_property mid.discovery.credentialless.enable , enabled. It was an error when we pushed the capability to have the property set to true when it should have been false out of box.  So just go update that property and the messages will no longer trouble you.