> I have the probe set up for a few windows servers, which it's monitoring > fine most of the time. The top message is from a successful probe, > following a failed probe 30 seconds earlier. The "Response time: XXX msec" > in the "Condition:" field I found interesting - the timeout for the probe is > std 3sec so it's not timing out.
You are correct that the probe is not timing out. However, the probe is entering the warning state because your VBScript occasionally takes longer than 2 seconds to return a value. "2000 msec" is the lower round-trip time threshold for most maps. Change the device's threshold to 4000 milliseconds. Right-click -> Set Info -> Set Thresholds... > I can run the script using cscript every 30secs outside of Intermapper and > it returns a value consistently. [...] > This failure to return a value, and as such going into the warning state, > happens every 1-4 hours. It sounds like an occasional memory/disk/cpu fluctuation causes the VBScript to take longer. Regards, Bill Fisher Dartware, LLC ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
