Video Screencast Help

Task Server not reporting task status

Created: 12 Mar 2012 | 9 comments
sgosden's picture

Hi,

i have a strange problem on about 100 of the 150 machines we have installed with CMS 7.1 SP2.

We have a task server (on the NS) which when I run any tasks, the clients receive it immediately and run it successfully. If I check the agent logs it says task run successfully. However, the status on the task in the agent gui on the machine says running (even though i can see it has finished). The status on the server says 'waiting for the agent to get the task' even though the task has been delivered and run on the client.

This is causing us lots of problems with jobs as it only runs the first task and just waits for the client to tell it has finished before it can start the next one and all jobs eventually have a status of failed when the timeout is reached

Have checked firewall to see if it was being blocked but the are currently off.

any ideas?

 

Comments 9 CommentsJump to latest comment

andykn101's picture

I've had problems with certain agent update paths and Task Agent.

 start "" /wait aexagentutil.exe /clean

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

sgosden's picture

thanks for your reply

have tried this and it works, as does a reimage. Issue i have is that most of the machines were a new image and were fine for 5 days and now nearly all of them are broken.

The site servers also have the issue and there are 9 of them. An uninstall and  reinstall of  them means replicating all the packages again which would be a major pain. The NS server also has the issue and i don't want to uninstall the agent on that.

The machines were all working fine for sevral days on SP2, whats to stop it happening again. I can't keep reinstalling the entire environment.

andykn101's picture

If they were a new image.

You can avoid downloading all your packages again if you reinstall Package Servers. I move (not copy, for speed and space considerations) the package directory to the root of the drive before I uninstall the whole agent. I then remove all xml files from the package directory just in case they cause problems, reinstall the agent and move the folder back.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

sgosden's picture

good plan, will do that. What about the NS server though? reinstalling the agent on the NS seems like it will break everything

andykn101's picture

I'd leave it be.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

sgosden's picture

yep. makes sense. think it would kill the NS. will start to rollout uninstall and reinstalls and see how it goes. will update post with reaults. Thanks for your help

sgosden's picture

Hi,

reinstalled the agent on some machines and all worked ok. However it has happened again.

It is the power control task that causes this. I noticed that the machines were ok until a power control task is run on them. This task stays at running and after that no further updates are sent back to the NS. As mentioned everything still works if i run individual tasks, they complete and the client log say it is complete, but the server says it failed and the client says running in the gui.

 

sgosden's picture

Definately the power task that causes it.

basic power tasks such as reboots are fine, but the power wake - Wake up built in task causes it.

Ran it on a machine that was working fine and was switched on. The task has a built in timeout of 30 minutes but this never actually timeouts. Consequently all tasks show up as running and do not report to the NS. Only fix seems to be an install and uninstall of the agent.

We regularly run wake up tasks for maintenaince at the weekend so not really ideal to not be able to use this task. Also major pain having to uninstall and reinstall all agents particularly as i cant use the WOL task :)

anyone else seen this? or have any idea on fixing it without having to reinstall the entire environment

 

cheers

jpopik's picture

We are having the same problem, using Restart command in the Power Control task type.  We also had to re-install the agent in order to restore the ability to run tasks on it.  As a workaround to using Power Control to reboot a PC, we are using the "Reboot To" task type from the Deployment and Migration folder, and performing a Reboot to Production command.  This will not work for Shutdown, Log off, or Wake-up though.