Server Discovery fails with "credential not found"

David77
Giga Guru

2 hours ago

We are on Xanadu. For discoveries that were previously working, we now see many of these errors in our job logs and discovery dates getting stale. 

However, when running a Discover now, it works. 

Also, if I take all the IPs of the failed discoveries, put into a job, and do an execute now, it works. 

We have a case open with NOW, but they have no idea what's going on. 

Has anyone else had this issue and how did you resolve?
Thanks!

0 Helpfuls
  • 107 Views
1 REPLY 1

Prahlad Kumar
Tera Guru

33m ago

Hi @David77 ,

 

This is a known and painful issue on Xanadu and you’re absolutely right,

Please ask ServiceNow Support to run:
Fix 1 — Flush Discovery Credential Cache (Most effective)

snc_credentials_util.flush()

or

gs.flushCache()


Then restart MID Servers.

 

Fix 2 — Clone the Discovery Schedules

Instead of editing:
-Create new discovery schedules
-Reassign MID Server & credentials
-Disable old schedules

This resolves corrupted schedule records in many cases.

Fix 3 — Rebuild Credential Affinity Rules

 

Quick validation test
-Disable all discovery schedules.
-Create one new schedule with 1 IP.
-Run scheduled discovery.

If it fails → platform bug confirmed.

 

If this helps, please mark it as Helpful.

 

Thanks & Happy to Help,
Prahlad Kumar (Tera Guru)
Solution Architect at HumIT
ITOM | ITAM | ITSM | CMDB | HRSD
LinkedIn: https://www.linkedin.com/in/prahlad-kumar-92a877117/

If this helps, please mark it as Helpful.

0 Helpfuls