Auto upgrade does not work when migrating from Endpoint Protection 12.1 to 14.

book

Article ID: 169609

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

After assigning an upgrade package to a group in the Symantec Endpoint Protection Manager (SEPM), some clients in that group successfully upgrade to Symantec Endpoint Protection (SEP) 14, but the rest of the SEP 12.1 clients fail to upgrade.

Reviewing the sylink log shows the client receiving an HTTP 469 CONTENT PENDING error:

12/30 14:17:54.706 [1292] <mfn_GetClientPackage> The package at Index 0 is needed by the client .. Begin Downloading the information.. 
12/30 14:17:54.706 [129
2] ************CSN=184164
12/30 14:17:54.707 [1292] <GetClientPackageInfoUrl:>Request is: action=301&hostid=3B39CFCBC0A801B00034D0F653058E98&groupid=B1805E04C0
A80102001404D1F7A7CD5F&ClientProductVersion=12.1.7004.6500&as=184164&lun=[hex]4E4C52&udn=[hex]4D45525249434B494E442E434F4D&agentpackagechecksum=792d83855e4af987
b57c2a72a156d634&agentpackagetargetchecksum=4fcf90abb29c8923c128f21195932a40&agentpackagetargetmoniker={57201BD7-52EE-4841-8368-05C54B1F44DC}&lu=6&osv=06010100

12/30 14:17:54.707 [1292] <GetClientPackageInfo:>URL: /secars/secars.dll?h=96C6133806ABC0C204F604CFBC0ED16B0EBF3D33F1BA3138A2FB45F9AC90F18B2E9D6C2F20037E543FEC
E552771DFF7171245014313B272754F36B82D489FDD44DE0173B477B41AFA781A56A2DC39FD3B7B25AAF73F3C084DE64EB1DC70CBEC97E91A740226B92B10AAAAD5B847C5DC1F177A59EE4227EC4A4B4
44E716ACA793F94C8FA988C22A7BF1B213AC64D9402BEC1AAE41ECCD97614603C1CCDF367EFAE4884C13CCD16175360AF9635C7E1AFB4C426CF7769806BFF0DA5DC54E0E07BC38FA7B663DCE2FB27811
C9A1022C5C863B6ECE13B28CAEEDF32F9872835588B8A40ED1F644EE664D8249F5CE0D31819FDC12760137866CB13347C29FDB68D46093197FB38455B40EAEFDC848407C4998F83A590A34F7038FA483
1A4AC286098C12D5E48C7063AFFFBAEEAFEAD7363EF98B3892FA17EB5F5463CA9033BB67530B2BFE9D092330EF193DA2A73645D4303A319AA45A7885B5A3A2C57215FAFE0CB20D299BA07F8E67046CB1
1DD85FCBA20BFB97DAEF6BD368D2330C1502AD864138D799E96FAE05CC45822373334BDC6ACF
12/30 14:17:54.707 [1292] <SendUrlAndReceiveResponse:>http://SEPM:8014/secars/seca
rs.dll?h=96C6133806ABC0C204F604CFBC0ED16B0EBF3D33F1BA3138A2FB45F9AC90F18B2E9D6C2F20037E543FECE552771DFF7171245014313B272754F36B82D489FDD44DE0173B477B41AFA781A56
A2DC39FD3B7B25AAF73F3C084DE64EB1DC70CBEC97E91A740226B92B10AAAAD5B847C5DC1F177A59EE4227EC4A4B444E716ACA793F94C8FA988C22A7BF1B213AC64D9402BEC1AAE41ECCD97614603C1C
CDF367EFAE4884C13CCD16175360AF9635C7E1AFB4C426CF7769806BFF0DA5DC54E0E07BC38FA7B663DCE2FB27811C9A1022C5C863B6ECE13B28CAEEDF32F9872835588B8A40ED1F644EE664D8249F5C
E0D31819FDC12760137866CB13347C29FDB68D46093197FB38455B40EAEFDC848407C4998F83A590A34F7038FA4831A4AC286098C12D5E48C7063AFFFBAEEAFEAD7363EF98B3892FA17EB5F5463CA903
3BB67530B2BFE9D092330EF193DA2A73645D4303A319AA45A7885B5A3A2C57215FAFE0CB20D299BA07F8E67046CB11DD85FCBA20BFB97DAEF6BD368D2330C1502AD864138D799E96FAE05CC458223733
34BDC6ACF
12/30 14:17:54.707 [1292] <InternetCallback> HttpOpenRequest; Internet status: 60; CtrlBlk: 043A3FF8
12/30 14:17:54.707 [1292] 14:17:54=>Send HTTP REQUEST
12/30 14:17:54.713 [4340] <InternetCallback> HttpSendRequest; Internet status: 100; CtrlBlk: 043A3FF8
12/30 14:17:54.727 [1292] AH: (InetWaiting) bFinished is TRUE on CtrlBlk: 043A3FF8
12/30 14:17:54.727 [1292] 14:17:54=>HTTP REQUEST sent
12/30 14:17:54.727 [1292] <SendUrlAndReceiveResponse:>SMS return=469

12/30 14:17:54.727 [1292] <ParseHTTPStatusCode:>469=>469 CONTENT PENDING

Resolution

This issue is resolved in Symantec Endpoint Protection 14 RU1.

As a workaround in previous versions, remove the upgrade package and its content from the SEPM and then re-assign the package.

To remove the package and content:

  1. In a text editor, open the sylink.log
  2. In the sylink.log file, find the agentpackagetargetchecksum value in the request URL.
    Example:
    12/30 14:17:54.707 [1292] Request is: action=301&hostid=3B39CFCBC0A801B00034D0F653058E98&groupid=B1805E04C0A80102001404D1F7A7CD5F&ClientProductVersion=12.1.7004.6500&as=184164&lun=[hex]4E4C52&udn=[hex]4D45525249434B494E442E434F4D&agentpackagechecksum=792d83855e4af987b57c2a72a156d634&agentpackagetargetchecksum=4fcf90abb29c8923c128f21195932a40&agentpackagetargetmoniker={57201BD7-52EE-4841-8368-05C54B1F44DC}&lu=6&osv=06010100
  3. In the SEPM console, in the left pane, click Clients, and then, in the middle pane, click the group to which you applied the upgrade package.
  4. In the right pane, on the Install Packages tab, right-click the upgrade package and then click Delete.
  5. Stop all of the Symantec Endpoint Protection Manager services.
  6. In Windows Explorer, browse to the <SEPM Install Directory>\Inetpub\ClientPackages\ folder, and locate the folder that corresponds to the agentpackagetargetchecksum value from step 1.
  7. Inside of that folder, remove all *.dax and corresponding *.sig files.
  8. Restart all of the Symantec Endpoint Protection Manager services.
  9. In the SEPM console, re-assign the upgrade package to the group.

The remaining clients should now upgrade successfully.