Client Management Suite

 View Only
  • 1.  Client agents stuck running tasks

    Posted Apr 24, 2013 12:21 PM
      |   view attached

    NS Version 7.1 SP1

    We sometimes notice some of our client PCs get stuck running tasks and any subsequent tasks refuse to run.  See the attached screenshot for how this appears in the client PC task history.  Looking at the same tasks on the server - they all fail with "The task timed out on the Task Server while waiting for the agent to pick it up"

    This means we cannot run tasks on these computers.  The solution so far is to re-deploy them.

    What causes this problem and is there a easier workaround other than re-deploying the PCs to solve it?



  • 2.  RE: Client agents stuck running tasks
    Best Answer

    Trusted Advisor
    Posted Apr 24, 2013 03:26 PM

    Do you have any of the hotfix rollups installed? 

    If you're on 7.1 SP1 you are being several revisions:

    • 7.1 SP2
    • Rollup V1
    • Rollup V2
    • Rollup V3
    • Rollup V4
    • 7.1 SP2 MP1
    • Rollup 1
    • Rollup 2
    • Rollup 3
    • Rollup 4 (current)

    We used to have this problem and it was fixed in Rollup V3 of the pre-MP1 rollups:

    http://www.symantec.com/business/support/index?page=content&id=HOWTO64413

    If you can jump up to SP2 MP1 that should fix your problem as well without the intermediary steps.  Here's the link to the upgrade process:

    http://www.symantec.com/business/support/index?page=content&id=TECH177513

    The rollups are only available directly from Support.

    Good luck!



  • 3.  RE: Client agents stuck running tasks

    Trusted Advisor
    Posted Apr 26, 2013 11:02 AM

    Did this answer your question?



  • 4.  RE: Client agents stuck running tasks

    Posted May 30, 2013 03:12 AM

    Besides all the articles provided, do you perhaps make use of site servers (With Task Service) in multiple sites? If so, it has been said that you should only have a Site Server (With Task Service) next to the SMP itself, the agent for example, will not know that it received a task from SS1 and if the agent is restarted, it could potentially connect to SS2, therefore not completing it's task.

    Hope this makes sense.