Task executes properly on the client system, however the NS Console shows the case as Failed.
Last Updated February 18, 2015
The Quick Delivery Task executes and installs software successfully, however when looking at the Target Computer through Manage > Computer, the Jobs / Tasks section of the screen shows that the job Status is FAILED or NOT STARTED. Both of these would be incorrect, as the system had successfully run the Job / Task. However the information was not returned to the NS in a timely fashion.
Note: It took about 36 hours for the Task to timeout and show as Failed in the console.
This issue is caused by the Client Task Data Loader (CTDL) service not running properly on the Task Server that the client is registered with.
Check: run "netstat -an" and see that the port 50120 is bound.
First of all, as this is dealing with the Client Task Data Loader (CTDataload.exe or CTDL), try to start the service on the Task Server. If that fails, stop the agent service, restart it, and then try to start the CTDL again. If that also fails, the following may be necessary.
Does the Task Server have access to the Internet? In a couple of situations this was the cause of the error as we need to verify a certificate before starting the service. See KB HOWTO9585 for further resolution.
On a couple of Task Servers we still were not able to start the CTDL service and so it was reinstalled using the following procedure:
To reinstall the Client Task Data Loader, run the following commands:
<Open CMD prompt as an Administrator> cd C:\Windows\Microsoft.NET\Framework64\v2.0.50727 then run installutil -u "X:\Program Files\Altiris\Altiris Agent\Client Task Server\CTDataLoad.exe" (Where X is the drive where the Altiris Agent is installed)
Restart the server when that completes.
When it comes back, run:
cd C:\Windows\Microsoft.NET\Framework64\v2.0.50727 followed by: installutil "X:\Program Files\Altiris\Altiris Agent\Client Task Server\CTDataLoad.exe"
Then Start the Service (may need to refresh Services)
Check Netstat -an, and it should be listening on 50120.
Usually Clients are registered to a Remote Task Server
Imported Document ID: TECH216993
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe