Scheduled LiveUpdate through the Symantec Endpoint Protection Manager console fails with an error Return code of 6013

book

Article ID: 177943

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

Why does the scheduled LiveUpdate fail in the Symantec Endpoint Protection Manager (SEPM) with an error return code =4, whereas a manually-launched LiveUpdate session is successful?


Performing a manual LiveUpdate session through the SEPM console by clicking on "Download LiveUpdate content" option under Admin>Servers>Local Site is successful without any errors

  • The usual scheduled LiveUpdate sessions fail with an error "Liveupdate encountered one or more errors, return code =4.
  • There is no proxy server in the environment.
  • Log.liveupdate file has the following error,


9/20/2009, 15:26:46 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
9/20/2009, 15:26:46 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/minitri.flg", Estimated Size: 0, Destination Folder: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads"
9/20/2009, 15:26:46 GMT -> HttpSendRequest (status 200): Request succeeded
9/20/2009, 15:26:46 GMT -> ERROR - The requested file, minitri.flg, is too large (11190 bytes) for LiveUpdate to start to download.
9/20/2009, 15:26:46 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantecliveupdate.com/minitri.flg", Full Download Path: "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x802A0048
9/20/2009, 15:26:46 GMT -> HR 0x802A0048 DECODE: E_FILE_NOT_TRUSTED
9/20/2009, 15:26:46 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x802A0048, Num Successful: 0
9/20/2009, 15:26:46 GMT -> HR 0x802A0048 DECODE: E_FILE_NOT_TRUSTED
9/20/2009, 15:26:46 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server liveupdate.symantecliveupdate.com at path via a HTTP connection. The server connection attempt failed with a return code of 6013, LiveUpdate is unable to continue, because a file needed on the server may be corrupt. Please run LiveUpdate again later.

Cause

One of the updates or TRI files LiveUpdate download cannot be trusted. This error occurs if the size of a TRI file or update file is too large or there are problems with the file's archiving. The file archiving problems can be either the file will be too large when it is extracted, the extractable size of the file is greater than the size reported in the zip headers, or the zip file contains illegal path information.

Resolution

Launch LiveUpdate manually through the SEPM console by going to Admin>Servers>Local Site and clicking on the "Download LiveUpdate content" option. If LiveUpdate completes successfully without any errors, the subsequent scheduled LiveUpdate sessions through the SEPM console should be successful.