1 of 1 people found this helpful
I have found that in some environments where we upgraded from versions without that feature to the ones that had it I would have to edit the subnet and specify the engineid to use for polling. Since the value didn't exist or wasn't used in older versions it was NULL for all my subnets and jobs weren't running.
Thank you for your reply, but we already went through the exercise of applying the secondary poller to all subnets, as we also faced the issue of stalled scans, when no poller was defined.
As I mentioned, we have the scheduled scans running fine now, but when I try to initiate a manual scan, that I would expect should start immediately, it doesn't.
This morning I tried defining the Primary poller for the subnet, and request a new manual scan, but the same happens, the job is added to the task list, but being held back, until a later time.
Funny thing is, the 18:20 time the job is scheduled for, was exactly the same as yesterday....