Discovery is not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2017 10:18 PM
Hi,
I am using service now jakarta version and I am mostly using Service now instance for my cloud needs. I have configured service account and cloud account and I have configured discovery schedules for them. Recently I observed that one of my discovery job is stuck for two days and I canceled that schedule and rescheduled my discovery job but after doing that now my discovery completely stopped working. If I create a new schedule then discovery status is as follows
Can you please help me to understand what is causing this issue and how to solve this?
Regards,
Shruthi

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2019 07:30 AM
Hello @berny
Today i did have a similar problem with "Cloud Management" in London to discover two VMware datacenter.
Previous I did migrate from kingston to london my non-production instance.
The midservers "lost" the "Supported Applications", "IP's ranges" and "Capabilities" settings.
The error was: "Unable to find any validated MID Server based on status (degraded), and application: Discovery"
I add the "ALL" for the three settings and works for me.
Thanks! You rocks Berny
Ariel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2019 01:57 PM
Awesome! Glad to hear it was helpful and most important... that it worked! 🙂
Thanks,
Berny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2017 11:05 AM
I see the exact same error - the Sys ID is the same. Weird.