ePO 5.1.1 server tasks don't expire as configured

[Former Member]

Thanx artuha for your response,

will you write the response from mcafee here?

/Kenneth

[Former Member]

Yes I will try to write, may be this will help to someone else

[harris_s]

I too am experiencing the same.  This happened last time I upgraded ePO. Logged an SR last time, was a waste of time, was told I didn't need hotfix, applied it anyway which fixed the issue.

Have tried the sql stuff in the kb but still getting tasks that never complete, therefore comprimising the security of our ePO system.

Would be interested what they come back with.

[Former Member]

I just managed to fix my ePO exhibiting exactly the same symptoms.

In my scenario, the McAfee services lost communication with the database for long enough that the DB Clean-up Task was no longer running. This would appear to handle terminating expired tasks.

I terminated all running tasks, followed solution 3 in KB79875 https://kc.mcafee.com/corporate/index?page=content&id=KB79875 then restarted the McAfee ePO services.

After this, tasks started terminating as expected.

[m.bocchini-eus@]

I've had same issue in my enviroment.

This problem seems to be caused by the Daylight Saving Time in an ePO Cluster enviroment and, indeed, i've server tasks blocked since October, 25th (i'm in italy, my DTS is on 25-26 October).

Like cabbott, i've followed solution 3 in KB79875, restarted ePO services and all is ok.

[Former Member]

McAfee support after 2 weeks and escalation to Tier 3 level send to me SQL queries which resolve my issue

update
OrionTaskQueueMT set RunTime=GETUTCDATE() where taskdescription like
‘%dbclean%’

update
OrionTaskQueueMT set RunTime=GETUTCDATE() where taskdescription like
‘%task.queue%’

[JoeBidgood]

This is an issue that we've seen with 5.1.1. It's documented in KB83384, which is at the time of writing in the process of being updated with the solution given here.

Regards --

Joe

[Former Member]

Same Problems here with 5.1.1. I´ll try KD Article...