Quantcast
Channel: Symantec Connect - ブログエントリ
Viewing all articles
Browse latest Browse all 5094

DS 7.5 SP1 PECTAgent.exe crashing after upgrade (SP1 HF3 - SP1 HF4)

$
0
0
corrupted .dll files

In some case, after upgrading DS, the PECTAgent.exe is crashing in automation without any error message.

From the PECTAgent. logs we see as final lines:

"</resourcekeys>
</request>"

the PECTAgent.exe crashes and stops

Suspected cause of this is corrupted .dll components.

Compare the size of the .dll files below taken from a DS 7.5 SP1 HF4 environment:

PECTAgent.exe version: 7.5.3290.0

x86

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

07822105.jpg

x64

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

x64.jpg

It is possible that even .dll files having size as above may still be corrupted.

For troubleshooting with other PECTAgent issues collect pectagent dmp files as from article below:

https://www-secure.symantec.com/connect/blogs/ds-75-info-how-create-pectagentdmp-files-automation

FIX:

1 - Call support and ask for the delivery of files to replace the corrupted ones (excluding PECTAgent.ini. This file contains the server information and it is environment-specific -> keep the original)

2 - Replace corrupted files at locations below:

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

3 - Check if replicated OK at Site Server location below:

Site Server:

\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

\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

4 - If not replicating delete the corresponding GUID snapshot at location below on SMP

C:\ProgramData\Symantec\SMP\Snapshots

5 - Re-create the pre-boot environment

6 - Test

NOTE:

If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help our tech community – Thank you, Mauro


Viewing all articles
Browse latest Browse all 5094

Trending Articles