on demand scan not starting

[User16096767]

We have servers not starting on damand scan. When we kick off manually, it does scan.

ENS 10.6.1.1128

ePO agent 5.5.1.388

on demand scan schedule on the client machines  shows what we set up in ePO.

[danteoz]

I have the exact same issue but with our clients, we started wondering why only 350 of 2600 clients were reporting completed scans in the last 7 days, checked and looks like they are the only ones completing scans for the last month even. I think I will raise a ticket with support as the number of clients completing scans or even starting them is abysmal.

[User16096767]

How often is the task scheduled for your evironment? our is setup for  every 8 days.

[danteoz]

We run Quick scans every day but Thursday and a Full scan every other Thursday. Maybe a bit over the top but if I have 92% of my computers not scanning in over 30 days, that is a problem

[User16096767]

The engineer who worked on our environment suggested to change the schedule. That is the reason I asked your environment schedule.

we have a lot of servers haven't been scanned more than 30 days. Something is not working properly.

Suspecting ENS since the impacted servers inlcude different ePO agents.

ENS

[sovanpratihar]

There could be many reasons for schedule ODS not running on a machine.

To start with we would need to check and verify if the task has reached the client machine and at the time of trigger do we see any details in the MASVC log?
Does this happen all machines and all times?

if you can share the log at the time when the agent should trigger the task we can look at it.

[danteoz]

I see this a lot in the logs on computers that are not running scans.

2019-03-29 10:19:40.818 masvc(3776.4316) scheduler service.Critical: scheduler get task request failed, last error(1101)

[User16096767]

I see the same thing in our log, but different number

macompatsvc (3760, 20112) Scheduler Error  Task get setting failed.

[Former Member]

If the task starts when you run it manually, I would suggest enabling MA debug logging, reproducing the issue and providing a MER to the McAfee Agent technical support team. It sounds like there may be an issue with their scheduling mechanism.

[User16096767]

we have submitted an SR with MER yesterday. The ticket is assigned to ENS team.