Unable to start Altiris Client Task Data Loader service
|Article:TECH192580|||||Created: 2012-07-09|||||Updated: 2012-07-10|||||Article URL http://www.symantec.com/docs/TECH192580|
When you try to start the Altiris Client Task Data Loader service on your main Symantec Management Platform Server (Formerly known as Notification Server) or on one of your site servers you get the error message below:
Could not start the Altiris Client Task Data Loader service on Local Computer
Error 1053: The service did not respond to the start or control request in a timely fashion
SMP 7.1 SP2
DS 7.1 SP1a MR1a
This problem is caused by the Certificate Revocation List (CRL) lookup.
If the Symantec Management Platform computer does not have internet access, the .NET runtime cannot access the Microsoft Certificate Revocation List servers to verify the Authenticode assembly. Although none of the applications that comprise the Symantec Management Platform make use of Authenticode assembly signing evidence, the standard Microsoft assemblies that are included with the .NET framework are all Authenticode signed. When the computer has no internet connection, .NET will try for up to 15 seconds to access the CRL before timing out as a failure.
This delay can lead to Windows services failing during startup, as some services take a long time to start and may time out. This delay also causes some Symantec Management Console pages to take a very long time to load.
To resolve this issue, follow the instructions of KB article HOWTO9585
ADDITIONAL NOTE: Please note that on a Windows 2008 R2 x64 server you need to customize the machine.config file located in C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\.
Article URL http://www.symantec.com/docs/TECH192580