{"id":444,"date":"2022-04-12T12:34:36","date_gmt":"2022-04-12T12:34:36","guid":{"rendered":"https:\/\/ouritsource.com\/blog\/?p=444"},"modified":"2025-05-29T15:30:18","modified_gmt":"2025-05-29T15:30:18","slug":"troubleshooting-exploration-phase-failures-in-discovery","status":"publish","type":"post","link":"https:\/\/ouritsource.com\/blog\/troubleshooting-exploration-phase-failures-in-discovery\/","title":{"rendered":"Troubleshooting Exploration Phase Failures in Discovery"},"content":{"rendered":"\n

Below shows Discovery state stuck on \u201cActive\u201d. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

We go to the ECC Queue, and filter out all the processed items to verify there is nothing still in the \u201cready\u201d or \u201cprocessing state. Basically, you right-click on the \u201cState\u201d column and choose Filter Out <\/strong> from the pop-up menu.<\/p>\n\n\n\n

<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

As you can see, it now shows the error which means processing did complete however something also did go wrong.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

The next step is to check the Discovery log. The log shows Discovery starting, a shazzam probe was launched, it identified the device, it found a match in the CDMDB (hyy_on_esx3), then it failed with a sensor error: Sensor error when processing Windows \u2013 Hardware Information: No sensors defined. This means a probe was launched but no corresponding sensor was defined to process the data.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

So Discovery stopped in an \u201cActive\u201d State. The State is only listed as \u201cCompleted\u201d if the Started and Completed values match. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

At this case, because of the sensor error, the Discovery ended without updating the completed count and the state remains active. At this point, our options are to cancel the discovery by clicking on the State field and selecting \u201cCompleted\u201d and Save it. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This takes care of the failed Discovery however we still have the sensor issue. Someone added the \u201cWindows \u2013 Hardware information\u201d probe to the exploration phase and didn\u2019t realize the probe lacked a corresponding sensor.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To check, you can click on the probe itself by clicking on the \u201cWindows \u2013 Hardware Information\u201d link. The probe\u2019s configuration opens as highlighted in yellow. The error string highlighted in blue states there are no sensors defined as highlighted in green.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

To fix, we will go to the probe definition. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

We need to first find what class of device this is.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In this case, it is a \u201cHyper-V Server\u201d. So, we will go to the WIndows Classification and open the \u201cHyper-V Server\u201d configuration. In the bottom of the configuration are a list of probes used by this classification. The WMIRunner-Windows \u2013 Hardware Information circled is what was the probe that was added. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

So, we can go to that probe by clicking on the WMIRunner-Windows \u2013 Hardware Information Link and create a sensor in the Sensors section\u2026<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Or since this probe comes with a ServiceNow based system and by design has no sensor, this is an incorrect setup. So, we should remove it. To remove, you go back to the Hyper-V Server Windows Classification screen and click on the Edit button for the Trigger probes:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Once the Members list appears, remove the \u201cWindows \u2013 Hardware Information\u201d from the Triggers probes List by clicking on it and then clicking on the \u201cremove\u201d button so that it goes back to the Collection list. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Don\u2019t forget to Save it<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Now, if you go back and run the Discovery again, it should complete without any issues. <\/p>\n\n\n\n

So if the Discovery is stuck in an Active State, and the S tared and Completed counts do not match, and the ECC Queue records have all been processed, this indicates Discovery has finished but something went wrong. To resolve, cancel the Discovery or manually change its State to Completed. Then you find out what went wrong, fix it, and then re-run the Discovery. <\/p>\n\n\n\n

3:41<\/p>\n\n\n\n

<\/p>\n<\/body>","protected":false},"excerpt":{"rendered":"

Below shows Discovery state stuck on \u201cActive\u201d. We go to the ECC Queue, and filter out all the processed items to verify there is nothing still in the \u201cready\u201d or \u201cprocessing state….<\/p>\n","protected":false},"author":1,"featured_media":493,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[26],"tags":[],"class_list":["post-444","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-servicenow","has-thumbnail"],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/ouritsource.com\/blog\/wp-content\/uploads\/2022\/04\/ChatGPT-Image-May-29-2025-11_26_49-AM.png?fit=1024%2C1024&ssl=1","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/posts\/444","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/comments?post=444"}],"version-history":[{"count":1,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/posts\/444\/revisions"}],"predecessor-version":[{"id":462,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/posts\/444\/revisions\/462"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/media\/493"}],"wp:attachment":[{"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/media?parent=444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/categories?post=444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ouritsource.com\/blog\/wp-json\/wp\/v2\/tags?post=444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}