Discovery Schedule hangs on in 'Active' state if probe times out - Known Error

Discovery Schedule hangs on in 'Active' state if probe times out Description When running Discovery, for certain type of probes, if the probe times out and is interrupted by Probe Reaper, no results are sent back to the instance. This causes discovery getting stuck in 'Active' state and eventually being cancelled.

Steps to Reproduce

1. Goto ec_agent_property and add 'mid.windows.probe_timeout' = 1. 2. Open "Windows - Storage 2012" and test the probe. 3. Wait a few seconds for the probe to time out. 4. Inspect the MID Server log and check that the probe is interrupted by ProbeReaper. 4. Check the \agent\work\monitors\ECCSender\output_2\ folder for 0 byte file queued.

Workaround This problem has no workaround, is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form.