ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Deployment tasks fail in automation environment


Article ID: 160923


Updated On:


Deployment Solution


When deploying an image on 7.5 HF3 and later, the target machine reboots and goes into automation but no deployment tasks will run.

  <![CDATA[CClientTaskInstance::Execute(): CAtrsException exception, error = "Unable to find class ID", OS error = 2147746291, at line 69
 re-throw at CAtrsComPtr::CoCreateInstance
 re-throw at CAtrsComPtr::CoCreateInstance(BSTR)
 re-throw at CClientTaskInstanceWin32::_CreateTaskHandler
 re-throw at CClientTaskInstanceBase::_CreateTaskHandler
 re-throw at CClientTaskInstanceBase::_Execute]]>
<event date='07/07/2014 12:11:04.9660000 -08:00' severity='1' hostName='minint-p2edeek' source='CAtrsException' module='Client Task Agent.dll' process='PECTAgent.exe' pid='1216' thread='2024' tickCount='164671' >

<![CDATA[CTaskExecutionEngineBase::_onProcessExecuteTask(): CAtrsException exception, error = "Failed to execute task", OS error = 2147746291, at line 535
 re-throw at CTaskExecutionEngineBase::_onProcessExecuteTask
 re-throw at CTaskExecutionEngineBase::_onProcessExecuteTask
 re-throw at CTaskExecutionEngineBase::_onProcessExecuteTask]]>



The cause for this error is that one or more of the .dll or .exe files are missing from within these two locations on the Site Server:

C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base\Program Files\Symantec\Deployment


C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x64\Base\Program Files\Symantec\Deployment

These won't show up in the PectAgent.log as missing but will stop the imaging task from being able to start. This is a known issue and it is currently unclear why these files go missing but it seems to occur after upgrading to another hot fix or service pack.


The following steps are to show you how to properly replace the files. To get the files, you will need to contact Symantec Support and get them from one of the technicians. These two screenshots show you which files should be in the x86 and x64 locations:





Step 1:

Go into this location on the Notification Server and copy the files that are missing into the corresponding folders:


C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base\Program Files\Symantec\Deployment


C:\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x64\Base\Program Files\Symantec\Deployment



Step 2:

This is the "source" location so you will still need to update your packages to make sure the files are added to the destination location that the packages get replicated to. To do this manually, go to Task Scheduler and run NS.Package Refresh and then run NS.Package Distribution Point Update Schedule. Or wait overnight for these tasks to run and automatically update. This will update the package resource that the package servers will then re-download. You can verify that the updated package was downloaded by checking the following location for those files AFTER initiating a rebuild of a preboot configuration:

C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{374E1C49-4F58-4F5C-8D51-07A30F0D44AD}\cache\bootwiz\oem\DS\winpe\x64\Base\Program Files\Symantec\Deployment


C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\SBS\Bootwiz\{374E1C49-4F58-4F5C-8D51-07A30F0D44AD}\cache\bootwiz\oem\DS\winpe\x86\Base\Program Files\Symantec\Deployment


Once you have added these files to the correct locations, updated the packages, and rebuilt your preboot configuration, the image will deploy successfully.


Applies To


7.5 HF3 and later