Washington DC Endpoint Management User Group

I had a task that used to run daily on our agents to clear out the TaskManagment folder because after a period of time it would cause the Symantec Managment Service to crash and not start. I have since deleted that job yet I still have agents trying to run it every day at the scheduled time or worse.... over and over and over. It seems the NS still has this task stuck somewhere so when the agents check back in they get the task schedule again. I need to find it and KILL IT ASAP!

What task tables should I be looking at? I know the Guid of the original task as I exported it prior to deleting it. If needed I can import it again.

I am also noticing that other tasks wont run on some clients because they are waiting for this task to run or timeout.

first tried in sql to find jobs with the sql statement

and the change the status if it not stop

you can/should add more WHERE statement to narrow your scan 

SELECT
  tis.TaskInstanceGuid          AS [Task Instance Guid],
  itm.Name                      AS [Task Name],
  itm.Guid                      AS [Task Guid],
  ist.InstanceStatus            AS [Instance Status],
  tip.ParentTaskInstanceGuid    AS [Parent Task Instance Guid],
  tis.ResourceGuid              AS [Resource Guid],
  itr.Name                      AS [Resource Name],
  tis.TaskVersionGuid           AS [Task Version Guid],
  ivd.State                     AS [State],
  tis.InstanceType              AS [Instance Type],
  ivs.Version                   AS [Version],
  tst.StartTime                 AS [Start Time],
  tir.EndTime                   AS [End Time],
  tir.Result                    AS [Result]
FROM
  TaskInstances tis
  LEFT OUTER JOIN ItemVersions         ivs ON ivs.VersionGuid      = tis.TaskVersionGuid
  LEFT OUTER JOIN ItemVersionData      ivd ON ivd.VersionGuid      = tis.TaskVersionGuid
  LEFT OUTER JOIN vItem                itm ON itm.Guid             = ivs.ItemGuid
  LEFT OUTER JOIN vItem                itr ON itr.Guid             = tis.ResourceGuid
  LEFT OUTER JOIN TaskInstanceStatus   ist ON ist.TaskInstanceGuid = tis.TaskInstanceGuid
  LEFT OUTER JOIN TaskInstancesStarted tst ON tst.TaskInstanceGuid = tis.TaskInstanceGuid
  LEFT OUTER JOIN TaskInstanceResults  tir ON tir.TaskInstanceGuid = tis.TaskInstanceGuid
  LEFT OUTER JOIN TaskInstanceParents  tip ON tip.TaskInstanceGuid = tis.TaskInstanceGuid

WHERE
ist.InstanceStatus = 0 OR ist.InstanceStatus = 1 -- NotStarted = 0 OR Started = 1
--  ist.InstanceStatus = 2 -- The task has completed successfully
or ist.InstanceStatus = 3 -- The task has failed
--  ist.InstanceStatus = 4 -- The task has been told to stop

ORDER BY
  itm.Name, ist.InstanceStatus

we got the advice from symantec when we had a power taks which kept running

 -------------

With regards to your issue,

To try to resolve the issue, please run the below SQL Query after a full backup of the Symantec_CMDB database:

INSERT INTO ItemToDelete (Guid, DeleteDate)

SELECT vi.Guid, NULL

FROM vItem vi

WHERE vi.ClassGuid = '2c8d08c3-a9ba-4e39-a6ea-08701fba4a6e'

AND vi.Name LIKE '%Power%'

GO

NOTES: This query will result in the deletion of all Power Management Task schedules currently on the Symantec Management Platform.

You will need to re-schedule tasks which you want to run at a later time. The deletion will take place after a several minutes after the query is executed by the Notification Server. Once the deletion is complete the "Run Power Management on Schedule" scheduled tasks should be gone.

I tested this query and deletion on my test system.

Please restart the Altiris Object Host Service after running the above query to clear all current tasks from memory and release all used memory by the AtrsHost.exe process.

Best practice is to disable tasks by removing the target, schedule, etc., and setting it aside in a Disabled group.  Same for policies -- disable, remove target, schedule, and set aside.  It helps to have access in situations like these.

I would refer to this KB and follow the solutions within:
http://www.symantec.com/docs/TECH144662

Does this help?

Thats the task running over and over again on my clients!

I have experienced this issue about 6 times so far. What happens is that there is a failed job task run sometime in the past on a computer, maybe yesterday, maybe a week or month ago. The computer starts up and runs the task (it is being pushed from task server).

The only way I found found to stop it is to restar the task services on the task server the computer is talking to. That fixes the problem for me. I am on 7.0 SP5 and currently have a case open on it.

Hope that helps.

If the task running again and again is only fixed by running the task that's running again and again, I might contact support directly.  I think they'll work to modify some tables and get you functional again.

hi,

Check the windows task schedular, might be those task are still running in Windows Task Schedular so disable them.

I have seen this issue, after removing the HP client manager the tasks were running every second on the clients, after disabling it them from Windoes Task Schedular they never ran again.

Regards,

Alim Shaikh

There were some known issues of tasks repeating in 7.1.  Make sure you have the latest service pack.

If you have the latest build, you can clear out the instances of that task by running the following query then running the NS.Daily Scheduled task: 

Please note: It is suggested you backup your database before making any changes.

Insert into ItemToDelete
 select item.guid, getdate() from Item where name like ‘%<full name of the task>%’