Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Live Update failed with errors. Return code = 4

pete

peteSep 27, 2011 05:17 AM

can you post the log.liveupdate?

  • 1.  Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 04:10 AM

     

    I have problems with live update on SEPM 11 server. When I try to download LiveUpdate Content I get this error:

    "LiveUpdate encountered one or more errors. Return code = 4.  [Site: My Site]  [Server: xxxxservername]"

    I try to reinstall LiveUpdate but that didn’t help.

    Liveupdate version is 3.3 from SEPM CD.

    What is errors 4?



  • 2.  RE: Live Update failed with errors. Return code = 4

    Broadcom Employee
    Posted Sep 27, 2011 04:36 AM

    It could be becuase of proxy

    check this article

    http://www.symantec.com/business/support/index?page=content&id=TECH103112



  • 3.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 04:52 AM

    Hi Qubick,

    Have you examined the log.liveupdate from that SEPM?  That would contain the in-depth information needed to determine what exactly is happening.

    LU logs can be difficult to read- you may wish to cut the log dwon to display only the most recent sessions and then attach it to this thread.  Peer admins here in the forum may be able to offer you some advice.

    Hope this helps!



  • 4.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 04:55 AM

     

    When I try LiveUpdate on Symantec Endpoint Protection client install on the same server I can sucesfully update...

    After that I can see new virus definitions under LiveUpdate Most recent Downloads under Symantec endpoint Protection Manager console.

     

    So I don’t think proxy is an issue...



  • 5.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 05:16 AM

    its proxy error

    when u run liveupdate on client manually, it will run under admin account, so admin will have direct access without proxy.

    schedule is system account so it needs access...

    check the document from pete again, it should fix it

    if not do a repair from add/remove programs.



  • 6.  RE: Live Update failed with errors. Return code = 4

    Broadcom Employee
    Posted Sep 27, 2011 05:17 AM

    can you post the log.liveupdate?



  • 7.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 07:03 AM

     

    I check the proxy server and there is a rule which allow AV server to pass proxy without authentication.

    I already reinstall Live update trough add/remove programs.



  • 8.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 07:13 AM

     

     

    I‘am sorry but I try to search for log.liveupdate file but I can't find it anywhere???

    I have Win2008 with SP2.



  • 9.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 07:19 AM

    Here is a good KB:

    Where is the location of LiveUpdate Log file Log.liveupdate?
    Article: TECH92881 | Created: 2009-01-16 | Updated: 2011-07-19 |
    Article URL http://www.symantec.com/docs/TECH92881

     

    Windows 2003: C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate

    Windows 2008: C:\ProgramData\Symantec\LiveUpdate



     



  • 10.  RE: Live Update failed with errors. Return code = 4

    Broadcom Employee
    Posted Sep 27, 2011 07:23 AM

    check out this path "installataion drive :\ProgramData\Symantec\LiveUpdate"



  • 11.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 08:32 AM

    its under program data, sometimes it will be hidden so check that too



  • 12.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 09:38 AM

    If you are having trouble running LiveUpdate from the SEPM and not a SEP client, I'd look at the "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\SesmLu.log"

     

    Cheers



  • 13.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 27, 2011 12:59 PM

    I see that you said you reinstalled liveupdate through add/remove programs. If you have not done so already you are going to need to re-register liveupdate with the SEPM. Below is how to do this.

    Note: To re-register the SEPM with LiveUpdate, follow the steps below:

    1. Open a command window, then browse to:
      C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin
    2. Type lucatalog -update and press Enter.
    3. Run LiveUpdate to verify that there are no errors.


  • 14.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 28, 2011 03:56 AM

     27.9.2011, 11:17:46 GMT -> ProductRegCom/luProductReg(PID=528/TID=4036): Setting property for Moniker = {FF153018-0A02-8610-00C2-EE15D170ADA2}, PropertyName = LU_SESSION_OPTOUT, Value = YES

    27.9.2011, 11:17:46 GMT -> ProductRegCom/luProductReg(PID=528/TID=4036): Set property error -- Moniker {FF153018-0A02-8610-00C2-EE15D170ADA2} is not found.
    27.9.2011, 11:17:46 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:46 GMT -> The PreSession callback for product SESM Content Catalog completed with a result of 0x0       
    27.9.2011, 11:17:46 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESC Virus Definitions Win32 v11 with moniker {C60DC234-65F9-4674-94AE-62158EFCA433}.
    27.9.2011, 11:17:46 GMT -> The callback proxy for moniker {C60DC234-65F9-4674-94AE-62158EFCA433} was successfully registered with LiveUpdate.
    27.9.2011, 11:17:46 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESC Virus Definitions Win32 v11.
    27.9.2011, 11:17:46 GMT -> LiveUpdate is about to execute a PreSession callback for product SESC Virus Definitions Win32 v11.
    27.9.2011, 11:17:47 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:47 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Setting property for Moniker = {B36CDA3C-B15B-421c-A2A4-7EC70E3B852B}, PropertyName = SEQ.HUBDEFS, Value = 110915016
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Setting property for Moniker = {B36CDA3C-B15B-421c-A2A4-7EC70E3B852B}, PropertyName = SEQ.CURDEFS, Value = 110926019
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Setting property for Moniker = {C60DC234-65F9-4674-94AE-62158EFCA433}, PropertyName = SEQ.CURDEFS, Value = 110926019
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Destroyed luProductReg object.
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:48 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Setting property for Moniker = {B36CDA3C-B15B-421c-A2A4-7EC70E3B852B}, PropertyName = VERSION, Value = MicroDefsB.Sep
    27.9.2011, 11:17:49 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Setting property for Moniker = {B36CDA3C-B15B-421c-A2A4-7EC70E3B852B}, PropertyName = SEQ.HUBDEFS, Value = 110915016
    27.9.2011, 11:17:49 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Setting property for Moniker = {B36CDA3C-B15B-421c-A2A4-7EC70E3B852B}, PropertyName = SEQ.CURDEFS, Value = 110926019
    27.9.2011, 11:17:49 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Destroyed luProductReg object.
    27.9.2011, 11:17:49 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:49 GMT -> The PreSession callback for product SESC Virus Definitions Win32 v11 completed with a result of 0x0       
    27.9.2011, 11:17:49 GMT -> Progress Update: TRYING_HOST: HostName: "xxxxNamexxx" URL: "http://xxxxNamexxx:PortNum/clu-prod" HostNumber: 0
    27.9.2011, 11:17:49 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0 Downloading LiveUpdate catalog file
    27.9.2011, 11:17:49 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.0.102_english_livetri.zip
    27.09.2011, 11:17:49 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    27.09.2011, 11:17:49 GMT -> Progress Update: PRE_CONNECT: Proxy: "http=proxyname:PortNum" Agent: "Symantec LiveUpdate" AccessType: 0x3       
    27.09.2011, 11:17:49 GMT -> Progress Update: CONNECTED: Proxy: "http=proxyname:PortNum" Agent: "4XqP0J3/a70RgSpqA5b+4GdwHB0x7CBTgAAAAA" AccessType: 0x3       
    27.09.2011, 11:17:49 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://xxxxNamexxx:PortNum/clu-prod/liveupdate_3.3.0.102_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    27.09.2011, 11:17:49 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    27.9.2011, 11:17:49 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://xxxxNamexxx:PortNum/clu-prod/liveupdate_3.3.0.102_english_livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\liveupdate_3.3.0.102_english_livetri.zip" HR: 0x802A002B
    27.9.2011, 11:17:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    27.9.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    27.9.2011, 11:17:50 GMT -> LiveUpdate will check for Mini-TRI file support on the server since the first Mini-TRI file was not available (liveupdate_3.3.0.102_english_livetri.zip).
    27.09.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    27.09.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://xxxxNamexxx:PortNum/clu-prod/minitri.flg", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    27.09.2011, 11:17:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    27.9.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://xxxxNamexxx:PortNum/clu-prod/minitri.flg", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x802A002B
    27.9.2011, 11:17:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    27.9.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    27.9.2011, 11:17:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
    27.9.2011, 11:17:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1 Downloading LiveUpdate catalog file
    27.9.2011, 11:17:50 GMT -> LiveUpdate could not find the MiniTri.flg file on the server.  LiveUpdate is entering legacy mode and will attempt to download the full LiveUpdate Catalog file.
    27.09.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    27.09.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://xxxxNamexxx:PortNum/clu-prod/livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    27.09.2011, 11:17:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    27.9.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://xxxxNamexxx:PortNum/clu-prod/livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x802A002B
    27.9.2011, 11:17:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    27.9.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    27.9.2011, 11:17:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
    27.9.2011, 11:17:50 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server xxxxNamexxx at path /clu-prod via a HTTP connection. The server connection attempt failed with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
    27.9.2011, 11:17:50 GMT -> Progress Update: HOST_SELECTION_ERROR: Error: 0x802A0027
    27.9.2011, 11:17:50 GMT -> LiveUpdate did not find any new updates for the given products.
    27.9.2011, 11:17:50 GMT -> EVENT - SESSION END FAILED EVENT - The LiveUpdate session ran in Express Mode. LiveUpdate found 0 updates available, of which 0 were installed and 0 failed to install.  The LiveUpdate session exited with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Content Catalog.
    27.9.2011, 11:17:53 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:53 GMT -> The PostSession callback for product SESM Content Catalog completed with a result of 0x0       
    27.9.2011, 11:17:53 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=528/TID=4036): Destroyed luProductReg object.
    27.9.2011, 11:17:53 GMT -> LiveUpdate has called the last callback for product SESM Content Catalog, so LiveUpdate is informing the callback proxy that it can exit.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win32 with moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264}.
    27.9.2011, 11:17:53 GMT -> The callback proxy executable for product {7073FE74-CAB0-42cc-B839-9808FCB47909} is exiting with no errors
    27.9.2011, 11:17:53 GMT -> The callback proxy for moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} was successfully registered with LiveUpdate.
    27.9.2011, 11:17:53 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win32.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win32.
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=4896/TID=752): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=4896/TID=752): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:53 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:53 GMT -> The PostSession callback for product SESM AntiVirus Client Win32 completed with a result of 0x0       
    27.9.2011, 11:17:53 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=4896/TID=752): Destroyed luProductReg object.
    27.9.2011, 11:17:53 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win64 with moniker {E4052532-F65C-4007-B620-DBEE893C2B2A}.
    27.9.2011, 11:17:53 GMT -> The callback proxy executable for product {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} is exiting with no errors
    27.9.2011, 11:17:53 GMT -> The callback proxy for moniker {E4052532-F65C-4007-B620-DBEE893C2B2A} was successfully registered with LiveUpdate.
    27.9.2011, 11:17:53 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win64.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win64.
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=6020/TID=5404): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=6020/TID=5404): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:53 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:53 GMT -> The PostSession callback for product SESM AntiVirus Client Win64 completed with a result of 0x0       
    27.9.2011, 11:17:53 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    27.9.2011, 11:17:53 GMT -> ProductRegCom/luProductReg(PID=6020/TID=5404): Destroyed luProductReg object.
    27.9.2011, 11:17:53 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM Network Access Control Client Win32 with moniker {A6BA2770-E351-4694-AB02-5358E0F9CDBE}.
    27.9.2011, 11:17:53 GMT -> The callback proxy executable for product {E4052532-F65C-4007-B620-DBEE893C2B2A} is exiting with no errors
    27.9.2011, 11:17:53 GMT -> The callback proxy for moniker {A6BA2770-E351-4694-AB02-5358E0F9CDBE} was successfully registered with LiveUpdate.
    27.9.2011, 11:17:53 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win32.
    27.9.2011, 11:17:53 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win32.
    27.9.2011, 11:17:54 GMT -> ProductRegCom/luProductReg(PID=3812/TID=3984): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:54 GMT -> ProductRegCom/luProductReg(PID=3812/TID=3984): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:54 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:54 GMT -> The PostSession callback for product SESM Network Access Control Client Win32 completed with a result of 0x0       
    27.9.2011, 11:17:54 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    27.9.2011, 11:17:54 GMT -> ProductRegCom/luProductReg(PID=3812/TID=3984): Destroyed luProductReg object.
    27.9.2011, 11:17:54 GMT -> LiveUpdate has called the last callback for product SESM Network Access Control Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
    27.9.2011, 11:17:54 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM Network Access Control Client Win64 with moniker {C6ACF447-A89C-42d7-A954-E31003AE0B26}.
    27.9.2011, 11:17:54 GMT -> The callback proxy executable for product {A6BA2770-E351-4694-AB02-5358E0F9CDBE} is exiting with no errors
    27.9.2011, 11:17:54 GMT -> The callback proxy for moniker {C6ACF447-A89C-42d7-A954-E31003AE0B26} was successfully registered with LiveUpdate.
    27.9.2011, 11:17:54 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win64.
    27.9.2011, 11:17:54 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win64.
    27.9.2011, 11:17:54 GMT -> ProductRegCom/luProductReg(PID=3440/TID=792): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:54 GMT -> ProductRegCom/luProductReg(PID=3440/TID=792): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:54 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:54 GMT -> The PostSession callback for product SESM Network Access Control Client Win64 completed with a result of 0x0       
    27.9.2011, 11:17:54 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    27.9.2011, 11:17:54 GMT -> ProductRegCom/luProductReg(PID=3440/TID=792): Destroyed luProductReg object.
    27.9.2011, 11:17:54 GMT -> LiveUpdate has called the last callback for product SESM Network Access Control Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
    27.9.2011, 11:17:54 GMT -> LiveUpdate is about to execute a PostSession callback for product SESC Virus Definitions Win32 v11.
    27.9.2011, 11:17:54 GMT -> The callback proxy executable for product {C6ACF447-A89C-42d7-A954-E31003AE0B26} is exiting with no errors
    27.9.2011, 11:17:56 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Successfully created an instance of an luProductReg object!
    27.9.2011, 11:17:56 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
    27.9.2011, 11:17:56 GMT -> ProductRegCom/luProductReg(PID=3912/TID=5488): Destroyed luProductReg object.
    27.9.2011, 11:17:56 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    27.9.2011, 11:17:56 GMT -> The PostSession callback for product SESC Virus Definitions Win32 v11 completed with a result of 0x0       
    27.9.2011, 11:17:56 GMT -> Successfully released callback {855BA5F4-6588-4F09-AE61-847E59D08CB0}
    27.9.2011, 11:17:56 GMT -> LiveUpdate has called the last callback for product SESC Virus Definitions Win32 v11, so LiveUpdate is informing the callback proxy that it can exit.
    27.9.2011, 11:17:56 GMT -> The callback proxy executable for product {C60DC234-65F9-4674-94AE-62158EFCA433} is exiting with no errors
    27.9.2011, 11:17:56 GMT -> ***********************           End of LU Session           ***********************
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    // End LuComServer
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
     
    I cut the part of the log and change AV server name, proxy server name and ports for security reasons :)


  • 15.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 28, 2011 04:32 AM

    Today this is what I find in manager console under LiveUpdate Status

     

    2011. rujan 28 10:19:39 CEST:  LiveUpdate succeeded.  [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:39 CEST:  LUALL.EXE finished running.  [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:39 CEST:  LiveUpdate will start next on 2011. rujan 28 14:19:39 CEST on xxxServer.  [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:39 CEST:  LUALL.EXE successfully updated the content. Return code = 0.  [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:19 CEST:  Symantec Endpoint Protection Win64 11.0.7000.975 (English) is up-to-date.    [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:19 CEST:  Symantec Endpoint Protection Win32 11.0.7000.975 (English) is up-to-date.    [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:18 CEST:  TruScan proactive threat scan engine Win32 11.0 is up-to-date.    [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:18 CEST:  TruScan proactive threat scan commercial application list Win32 11.0 was successfully updated.  [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:10 CEST:  TruScan proactive threat scan whitelist Win64 11.0 was successfully updated.  [Site: My Site]  [Server: xxxServer]
    2011. rujan 28 10:19:08 CEST:  Intrusion Prevention signatures Win64 11.0 was successfully updated.  [Site: My Site]  [Server: xxxServer]
     

    It looks like that everything is working today...hmm



  • 16.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 28, 2011 04:35 AM

     

    I try to find SesmLu.log but can't, have all folder structure but don't have any log there.



  • 17.  RE: Live Update failed with errors. Return code = 4

    Posted Sep 28, 2011 01:13 PM

    It looks like it was having trouble reaching the internal LUA 2.x server the otehr day:

    HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    27.9.2011, 11:17:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://xxxxNamexxx:PortNum/clu-prod/livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x802A002B
    27.9.2011, 11:17:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR

    27.9.2011, 11:17:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
    27.9.2011, 11:17:50 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server xxxxNamexxx at path /clu-prod via a HTTP connection. The server connection attempt failed with a return code of 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
     

    This may have just been a knock-on effect because some network component was rebooting or offline at that minute (?)

    I recommend, keep an eye on it and see if that happens often!