ビデオヘルプ
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Task runs on client but server displays wrong status

作成: 15 Jan 2013 • 更新: 15 Jan 2013 | コメント数: 7

I've created a Task to run a full inventory on my test computer.  The Task runs on the computer.  Result status is 'Success - return code 0'.  On the server, the status reads '100% Running'.  When I go into the details, the status reads 'Not started'.  Does anyone know what is going on?

コメント コメント数: 最新のコメントを表示

Andrew Bosch の写真

There can be a slight delay in task status reporting from the client, but typically not more than 5 or 10 minutes.  There is always the possibility that the status was lost when being sent back to the server, but that is rare, especially in a smaller environment.  That being said, I know we are working on more error checking/handling in these scenarios to make sure the task status makes it back to the server, no matter what.

------------------------------------
Sr. Principal SQA Engineer
Symantec

ArthurV の写真

It has been 24 hours and still the same status.  I've created more Tasks and still get the same results.

mclemson の写真

What version?  In older versions this was a known issue:

http://www.symantec.com/docs/TECH164398

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

ArthurV の写真

I'm running version 7.1 SP2 MP1.  I checked the version of the CTDataLoad.exe on the NS and the Site Server and they are bothing running the same version.

alasiri の写真

There can be a slight delay in task status reporting from the client, but typically not more than 5 or 10 minutes.  There is always the possibility that the status was lost when being sent back to the server, but that is rare, especially in a smaller environment.  That being said, I know we are working on more error checking/handling in these scenarios to make sure the task status makes it back to the server, no matter what.

Klim_Belchev の写真

We have had the exact same issue.

One of the Altiris services on our NS server had stopped for some reason.

Just started it and it all came back to normal.

HighTower の写真

If you're not getting status back at all check the "Altiris Client Task Data Loader" service on your task servers.  I think it's somewhat of a known issue that this service simply dies sometimes.

If it's stopped, configure the service's failure recovery to always restart or consider setting up a monitoring policy to start if it's stopped.