Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

luall.exe problem

  • 1.  luall.exe problem

    Posted Apr 22, 2013 03:20 PM

    Hello

    I one SEPM have problem because can't run luall.exe from schedule. When run manull all is OK.

    In Log.LiveUpdate I see entry

    HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.

     

    Could Give same advice

    SEPM is in 12.1.ru2 LU in version 3.3

    This option I do

    lucatalog -cleanup and press Enter.

    then  lucatalog -forcedupdate

     

     



  • 2.  RE: luall.exe problem

    Posted Apr 22, 2013 03:29 PM

    Can you post the full log.liveupdate file?

    Do you have a firewall or proxy in place?



  • 3.  RE: luall.exe problem

    Posted Apr 22, 2013 03:42 PM

    Hello

    In this enviroment is proxy called proxyv.pl

    Same part of log





    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    // Start LuComServer
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    4/22/2013, 15:20:43 GMT -> LuComServer version: 3.3.100.15
    4/22/2013, 15:20:43 GMT -> LiveUpdate Language: English
    4/22/2013, 15:20:43 GMT -> LuComServer Sequence Number: 20120518
    4/22/2013, 15:20:43 GMT -> OS: Windows 2008R2 Standard Edition, Service Pack: 1, Major: 6, Minor: 1, Build: 7601 (64-bit)
    4/22/2013, 15:20:43 GMT -> System Language:[0x0409], User Language:[0x0409]
    4/22/2013, 15:20:43 GMT -> IE9 support.
    4/22/2013, 15:20:43 GMT -> ComCtl32 version: 6.16
    4/22/2013, 15:20:43 GMT -> IP Addresses: 10.143.140.57
    4/22/2013, 15:20:43 GMT -> Loading C:\ProgramData\Symantec\LiveUpdate\Product.Inventory.LiveUpdate
    4/22/2013, 15:20:43 GMT -> Opened the product inventory at "C:\ProgramData\Symantec\LiveUpdate\Product.Inventory.LiveUpdate".
    4/22/2013, 15:20:43 GMT -> Account launching LiveUpdate is not a logged in user's account
    4/22/2013, 15:20:43 GMT -> Combined Product Inventory Flags 0, Permanent Flags 0, Permanent Flags Filter 0
    4/22/2013, 15:20:43 GMT -> LiveUpdate flag value for this run is 0
    4/22/2013, 15:20:43 GMT -> **** Starting a Silent LiveUpdate Session ****
    4/22/2013, 15:20:43 GMT -> ***********************        Start of New LU Session        ***********************
    4/22/2013, 15:20:43 GMT -> The command line is -S
    4/22/2013, 15:20:43 GMT -> EVENT - SESSION START EVENT - The LiveUpdate session is running in Silent Mode.
    4/22/2013, 15:20:43 GMT -> Check for updates to:  Product: LiveUpdate, Version: 3.3.100.15, Language: English.  Mini-TRI file name: liveupdate_3.3.100.15_english_livetri.zip
    4/22/2013, 15:20:43 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESC Virus Definitions Win64 (x64) v11 with moniker {1CD85198-26C6-4bac-8C72-5D34B025DE35}.
    4/22/2013, 15:20:43 GMT -> Starting Callback Proxy Worker thread.
    4/22/2013, 15:20:43 GMT -> The callback proxy for moniker {1CD85198-26C6-4bac-8C72-5D34B025DE35} was successfully registered with LiveUpdate.
    4/22/2013, 15:20:43 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESC Virus Definitions Win64 (x64) v11.
    4/22/2013, 15:20:43 GMT -> LiveUpdate is about to execute a PreSession callback for product SESC Virus Definitions Win64 (x64) v11.
    4/22/2013, 15:20:45 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:45 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Setting property for Moniker = {DFB8BBDD-52DE-427e-9EB3-FB7665893221}, PropertyName = SEQ.HUBDEFS, Value = 101018021
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Setting property for Moniker = {DFB8BBDD-52DE-427e-9EB3-FB7665893221}, PropertyName = SEQ.CURDEFS, Value = 130421007
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Setting property for Moniker = {1CD85198-26C6-4bac-8C72-5D34B025DE35}, PropertyName = SEQ.CURDEFS, Value = 130421007
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Destroyed luProductReg object.
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:47 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Setting property for Moniker = {DFB8BBDD-52DE-427e-9EB3-FB7665893221}, PropertyName = VERSION, Value = MicroDefsB.Old
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Setting property for Moniker = {DFB8BBDD-52DE-427e-9EB3-FB7665893221}, PropertyName = SEQ.HUBDEFS, Value = 101018021
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Setting property for Moniker = {DFB8BBDD-52DE-427e-9EB3-FB7665893221}, PropertyName = SEQ.CURDEFS, Value = 130421007
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Destroyed luProductReg object.
    4/22/2013, 15:20:49 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:49 GMT -> The PreSession callback for product SESC Virus Definitions Win64 (x64) v11 completed with a result of 0x0       
    4/22/2013, 15:20:49 GMT -> LiveUpdate is about to launch a new callback proxy process for product SEPM Content Catalog with moniker {999C2E87-0AB4-F6CD-0051-672E4F7C7C3D}.
    4/22/2013, 15:20:49 GMT -> The callback proxy for moniker {999C2E87-0AB4-F6CD-0051-672E4F7C7C3D} was successfully registered with LiveUpdate.
    4/22/2013, 15:20:49 GMT -> LiveUpdate successfully launched a new callback proxy process for product SEPM Content Catalog.
    4/22/2013, 15:20:49 GMT -> LiveUpdate is about to execute a PreSession callback for product SEPM Content Catalog.
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {01BAFA03-6B97-4906-B1E0-D8EFAEEFC618}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {10A44203-D0BD-4c6b-8E21-9D3797F07C95}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {14AEB036-9BBE-42c1-BA01-B948F11C4BAE}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {2B6323DE-0AB4-F6D4-00BE-153983F159FA}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {307D2C61-0AB4-F6D4-00BE-15391E224ABA}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {352B4220-A20F-4474-ABB7-A652097EF26C}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {3D536A52-C508-4bd1-9654-2FBCF673DA46}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {409B0A0A-A5DD-476e-B4CE-C290EF0AAD85}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {43EEFBAE-0AB4-F6D4-0039-BF120CC562DF}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {4884EB8B-77E8-457b-9096-6E9FFE1DC0CA}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {5B79C00A-F811-449a-8E40-FBB5C297E20B}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {6C974ED4-0AB4-F6D4-0039-BF12F0A8137A}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {735FBC97-0A02-8790-00AC-DD02C85454A9}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {7EC7284A-7033-45bb-86BD-10A3D1251AFD}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {999C2E87-0AB4-F6CD-0051-672E4F7C7C3D}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {9D30944B-771E-4d55-8AF4-FD12CD8EBB51}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {9F018B25-0AB4-F6D4-011B-1FC437E6A122}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {A25A92D9-B0AD-48de-BBD0-29DC3CEF8FFC}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {A261B05B-5B02-4f6e-BEFE-688C713FF74C}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {A6517C77-0AB4-F6D4-00D3-77DFC3591A64}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {ABD160D8-0A02-8790-00E1-DAC2498E1AC7}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {AC3C3154-0CC4-4fbc-8BBF-AACF4FFD4CC3}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {B16C770C-0AB4-F6D4-00BE-153954BBCF55}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {B259F24D-C28B-48e9-B8CD-C0AD23D516AA}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {B6453A57-0AB4-F6D4-00BE-1539CD2A614D}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {BB1D2DAC-7DED-4879-90B4-E3DAF2CD5E83}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {BCBBDC5B-6687-478b-9BEA-46E095D03164}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {C2A0F497-BA4F-4692-A37D-2EAA69900EE0}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {C41CDA09-1D42-41c6-A8FC-2257EC441FF4}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {C5B1F4E2-0AB4-F6D4-00D3-77DFC6E95DE1}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {C6A6D4AF-0AB4-F6D4-0039-BF121BF35C90}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {C8C42A08-0AB4-F6D4-00BE-1539101AB358}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {CC28F6AE-0A02-8790-00AC-DD020F2453D3}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {CF6C189A-CD24-4338-AD65-E495DDB30DE3}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {D2EE983B-0AB4-F6D4-00BE-1539CD0C259E}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {D4FBB370-104B-4ADD-9D4F-034C8681DA1D}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {D68BB248-0A02-8790-00E1-DAC2226E34F2}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {DB69402C-0AB4-F6D4-0039-BF12340A3BC8}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {DEF4748D-6773-4919-9F62-9BA130334D9B}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {E89D0525-8788-4824-A412-43C9D0B3E1D1}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {F3A2888E-9FC4-4df6-A7AE-F85F981152F4}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {F4FDEEDA-115D-4140-8E24-DD696AE38029}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:49 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {F95A6B17-0AB4-F6D4-00D3-77DF1EDEF277}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:50 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Deleting Property for Moniker = {FD4D935E-EA7F-4529-A14C-7E6C79E65BD7}, PropertyName = LU_SESSION_OPTOUT
    4/22/2013, 15:20:50 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:50 GMT -> The PreSession callback for product SEPM Content Catalog completed with a result of 0x0       
    4/22/2013, 15:20:50 GMT -> Progress Update: TRYING_HOST: HostName: "liveupdate.symantecliveupdate.com" URL: "http://liveupdate.symantecliveupdate.com" HostNumber: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0       Downloading LiveUpdate catalog file
    4/22/2013, 15:20:50 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.100.15_english_livetri.zip
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: PRE_CONNECT: Proxy: "http=proxyv.pl:80" Agent: "Symantec LiveUpdate" AccessType: 0x3       
    4/22/2013, 15:20:50 GMT -> Progress Update: PROMPT_RAS_DIALUP:possibly prompting the RAS dialogue...
    4/22/2013, 15:20:50 GMT -> Progress Update: CONNECTED: Proxy: "http=proxyv.pl:80" Agent: "jLV+CWPZSLHyyiqnNbXqNuXMI08S1V1UQAAAAA" AccessType: 0x3       
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/liveupdate_3.3.100.15_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantecliveupdate.com/liveupdate_3.3.100.15_english_livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\liveupdate_3.3.100.15_english_livetri.zip" HR: 0x802A002B
    4/22/2013, 15:20:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    4/22/2013, 15:20: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.100.15_english_livetri.zip).
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/minitri.flg", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantecliveupdate.com/minitri.flg", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x802A002B
    4/22/2013, 15:20:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1       Downloading LiveUpdate catalog file
    4/22/2013, 15:20: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.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantecliveupdate.com/livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantecliveupdate.com/livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x802A002B
    4/22/2013, 15:20:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
    4/22/2013, 15:20:50 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 1814, LiveUpdate could not retrieve the catalog file of available Symantec product and component updates.
    4/22/2013, 15:20:50 GMT -> Progress Update: TRYING_HOST: HostName: "liveupdate.symantec.com" URL: "http://liveupdate.symantec.com" HostNumber: 1
    4/22/2013, 15:20:50 GMT -> Progress Update: DISCONNECT
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0       Downloading LiveUpdate catalog file
    4/22/2013, 15:20:50 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.100.15_english_livetri.zip
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: PRE_CONNECT: Proxy: "http=proxyv.pl:80" Agent: "jLV+CWPZSLHyyiqnNbXqNuXMI08S1V1UQAAAAA" AccessType: 0x3       
    4/22/2013, 15:20:50 GMT -> Progress Update: CONNECTED: Proxy: "http=proxyv.pl:80" Agent: "jLV+CWPZSLHyyiqnNbXqNuXMI08S1V1UQAAAAA" AccessType: 0x3       
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantec.com/liveupdate_3.3.100.15_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantec.com/liveupdate_3.3.100.15_english_livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\liveupdate_3.3.100.15_english_livetri.zip" HR: 0x802A002B
    4/22/2013, 15:20:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    4/22/2013, 15:20: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.100.15_english_livetri.zip).
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantec.com/minitri.flg", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantec.com/minitri.flg", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x802A002B
    4/22/2013, 15:20:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1       Downloading LiveUpdate catalog file
    4/22/2013, 15:20: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.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "http://liveupdate.symantec.com/livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> HttpSendRequest (status 502): Request failed - Gateway or proxy encountered an error on the LiveUpdate server.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: - NOTE - URL: "http://liveupdate.symantec.com/livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x802A002B
    4/22/2013, 15:20:50 GMT -> HR 0x802A002B DECODE: E_HTTP_GATEWAY_ERROR
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
    4/22/2013, 15:20:50 GMT -> EVENT - SERVER SELECTION FAILED EVENT - LiveUpdate failed to connect to server liveupdate.symantec.com at path  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.
    4/22/2013, 15:20:50 GMT -> Progress Update: TRYING_HOST: HostName: "update.symantec.com" URL: "ftp://update.symantec.com/opt/content/onramp" HostNumber: 2
    4/22/2013, 15:20:50 GMT -> Progress Update: DISCONNECT
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 0       Downloading LiveUpdate catalog file
    4/22/2013, 15:20:50 GMT -> LiveUpdate will download the first Mini-TRI file, liveupdate_3.3.100.15_english_livetri.zip
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: PRE_CONNECT: Proxy: "ftp=proxyv.pl:80" Agent: "jLV+CWPZSLHyyiqnNbXqNuXMI08S1V1UQAAAAA" AccessType: 0x3       
    4/22/2013, 15:20:50 GMT -> Progress Update: CONNECTED: Proxy: "ftp=proxyv.pl:80" Agent: "jLV+CWPZSLHyyiqnNbXqNuXMI08S1V1UQAAAAA" AccessType: 0x3       
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "ftp://update.symantec.com/opt/content/onramp/liveupdate_3.3.100.15_english_livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "ftp://update.symantec.com/opt/content/onramp/liveupdate_3.3.100.15_english_livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\liveupdate_3.3.100.15_english_livetri.zip" HR: 0x0       
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
    4/22/2013, 15:20:50 GMT -> C:\ProgramData\Symantec\LiveUpdate\Downloads\liveupdate_3.3.100.15_english_livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
    4/22/2013, 15:20:50 GMT -> C:\ProgramData\Symantec\LiveUpdate\Downloads\liveupdate_3.3.100.15_english_livetri.zip contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
    4/22/2013, 15:20: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.100.15_english_livetri.zip).
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "ftp://update.symantec.com/opt/content/onramp/minitri.flg", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "ftp://update.symantec.com/opt/content/onramp/minitri.flg", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\minitri.flg" HR: 0x0       
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
    4/22/2013, 15:20:50 GMT -> C:\ProgramData\Symantec\LiveUpdate\Downloads\minitri.flg was an HTML response file.  LiveUpdate will ignore this file.
    4/22/2013, 15:20:50 GMT -> C:\ProgramData\Symantec\LiveUpdate\Downloads\minitri.flg contains HTML/DOCTYPE. It is invalid MiniTri, and has been removed
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "0"
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_START: Number of TRI files: 1       Downloading LiveUpdate catalog file
    4/22/2013, 15:20: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.
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_START: Files to download: 1, Estimated total size: 0
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_START: URL: "ftp://update.symantec.com/opt/content/onramp/livetri.zip", Estimated Size: 0, Destination Folder: "C:\ProgramData\Symantec\LiveUpdate\Downloads"
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_FILE_FINISH: URL: "ftp://update.symantec.com/opt/content/onramp/livetri.zip", Full Download Path: "C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip" HR: 0x0       
    4/22/2013, 15:20:50 GMT -> Progress Update: DOWNLOAD_BATCH_FINISH: HR: 0x0       , Num Successful: 1
    4/22/2013, 15:20:50 GMT -> C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip was an HTML response file.  LiveUpdate will ignore this file.
    4/22/2013, 15:20:50 GMT -> C:\ProgramData\Symantec\LiveUpdate\Downloads\livetri.zip contains HTML/DOCTYPE. It is invalid Tri file , and has been removed
    4/22/2013, 15:20:50 GMT -> Progress Update: TRIFILE_DOWNLOAD_END: Number of TRI files: "1"
    4/22/2013, 15:20:50 GMT -> EVENT - SERVER SELECTION SUCCESSFUL EVENT - LiveUpdate connected to server update.symantec.com at path /opt/content/onramp via a FTP connection. The server connection connected with a return code of 1800, Success
    4/22/2013, 15:20:50 GMT -> Progress Update: HOST_SELECTION_ERROR: Error: 0x802A0027
    4/22/2013, 15:20:50 GMT -> LiveUpdate did not find any new updates for the given products.
    4/22/2013, 15:20:50 GMT -> EVENT - SESSION END FAILED EVENT - The LiveUpdate session ran in Silent 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.
    4/22/2013, 15:20:50 GMT -> IE9 support.
    4/22/2013, 15:20:50 GMT -> LiveUpdate is about to execute a PostSession callback for product SESC Virus Definitions Win64 (x64) v11.
    4/22/2013, 15:20:53 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:53 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:53 GMT -> ProductRegCom/luProductReg(PID=2232/TID=2632): Destroyed luProductReg object.
    4/22/2013, 15:20:53 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:53 GMT -> The PostSession callback for product SESC Virus Definitions Win64 (x64) v11 completed with a result of 0x0       
    4/22/2013, 15:20:53 GMT -> Successfully released callback {855BA5F4-6588-4F09-AE61-847E59D08CB0}
    4/22/2013, 15:20:53 GMT -> LiveUpdate has called the last callback for product SESC Virus Definitions Win64 (x64) v11, so LiveUpdate is informing the callback proxy that it can exit.
    4/22/2013, 15:20:53 GMT -> LiveUpdate is about to execute a PostSession callback for product SEPM Content Catalog.
    4/22/2013, 15:20:53 GMT -> The callback proxy executable for product {1CD85198-26C6-4bac-8C72-5D34B025DE35} is exiting with no errors
    4/22/2013, 15:20:53 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:53 GMT -> The PostSession callback for product SEPM Content Catalog completed with a result of 0x0       
    4/22/2013, 15:20:53 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    4/22/2013, 15:20:53 GMT -> ProductRegCom/luProductReg(PID=1876/TID=8136): Destroyed luProductReg object.
    4/22/2013, 15:20:53 GMT -> LiveUpdate has called the last callback for product SEPM Content Catalog, so LiveUpdate is informing the callback proxy that it can exit.
    4/22/2013, 15:20:53 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win32 with moniker {D68BB248-0A02-8790-00E1-DAC2226E34F2}.
    4/22/2013, 15:20:53 GMT -> The callback proxy executable for product {999C2E87-0AB4-F6CD-0051-672E4F7C7C3D} is exiting with no errors
    4/22/2013, 15:20:53 GMT -> The callback proxy for moniker {D68BB248-0A02-8790-00E1-DAC2226E34F2} was successfully registered with LiveUpdate.
    4/22/2013, 15:20:53 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win32.
    4/22/2013, 15:20:53 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win32.
    4/22/2013, 15:20:53 GMT -> ProductRegCom/luProductReg(PID=3728/TID=3504): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:53 GMT -> ProductRegCom/luProductReg(PID=3728/TID=3504): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:54 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:54 GMT -> The PostSession callback for product SESM AntiVirus Client Win32 completed with a result of 0x0       
    4/22/2013, 15:20:54 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=3728/TID=3504): Destroyed luProductReg object.
    4/22/2013, 15:20:54 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
    4/22/2013, 15:20:54 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win64 with moniker {CC28F6AE-0A02-8790-00AC-DD020F2453D3}.
    4/22/2013, 15:20:54 GMT -> The callback proxy executable for product {D68BB248-0A02-8790-00E1-DAC2226E34F2} is exiting with no errors
    4/22/2013, 15:20:54 GMT -> The callback proxy for moniker {CC28F6AE-0A02-8790-00AC-DD020F2453D3} was successfully registered with LiveUpdate.
    4/22/2013, 15:20:54 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win64.
    4/22/2013, 15:20:54 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win64.
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=5636/TID=2284): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=5636/TID=2284): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:54 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:54 GMT -> The PostSession callback for product SESM AntiVirus Client Win64 completed with a result of 0x0       
    4/22/2013, 15:20:54 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=5636/TID=2284): Destroyed luProductReg object.
    4/22/2013, 15:20:54 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
    4/22/2013, 15:20:54 GMT -> LiveUpdate is about to launch a new callback proxy process for product SPC AntiVirus Client Mac with moniker {D4FBB370-104B-4ADD-9D4F-034C8681DA1D}.
    4/22/2013, 15:20:54 GMT -> The callback proxy executable for product {CC28F6AE-0A02-8790-00AC-DD020F2453D3} is exiting with no errors
    4/22/2013, 15:20:54 GMT -> The callback proxy for moniker {D4FBB370-104B-4ADD-9D4F-034C8681DA1D} was successfully registered with LiveUpdate.
    4/22/2013, 15:20:54 GMT -> LiveUpdate successfully launched a new callback proxy process for product SPC AntiVirus Client Mac.
    4/22/2013, 15:20:54 GMT -> LiveUpdate is about to execute a PostSession callback for product SPC AntiVirus Client Mac.
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=7040/TID=7288): Successfully created an instance of an luProductReg object!
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=7040/TID=7288): Path for calling process executable is C:\Program Files (x86)\Symantec\LiveUpdate\LuCallbackProxy.exe.
    4/22/2013, 15:20:54 GMT -> The callback proxy finished executing the callback with a result code of 0x0
    4/22/2013, 15:20:54 GMT -> The PostSession callback for product SPC AntiVirus Client Mac completed with a result of 0x0       
    4/22/2013, 15:20:54 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
    4/22/2013, 15:20:54 GMT -> ProductRegCom/luProductReg(PID=7040/TID=7288): Destroyed luProductReg object.
    4/22/2013, 15:20:54 GMT -> LiveUpdate has called the last callback for product SPC AntiVirus Client Mac, so LiveUpdate is informing the callback proxy that it can exit.
    4/22/2013, 15:20:54 GMT -> The callback proxy executable for product {D4FBB370-104B-4ADD-9D4F-034C8681DA1D} is exiting with no errors
    4/22/2013, 15:20:54 GMT -> ***********************           End of LU Session           ***********************
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    // End LuComServer
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////

    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    // Start LuComServer
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    4/22/2013, 15:36:49 GMT -> LuComServer version: 3.3.100.15
    4/22/2013, 15:36:49 GMT -> LiveUpdate Language: English
    4/22/2013, 15:36:49 GMT -> LuComServer Sequence Number: 20120518
    4/22/2013, 15:36:49 GMT -> OS: Windows 2008R2 Standard Edition, Service Pack: 1, Major: 6, Minor: 1, Build: 7601 (64-bit)
    4/22/2013, 15:36:49 GMT -> System Language:[0x0409], User Language:[0x0409]
    4/22/2013, 15:36:49 GMT -> IE9 support.
    4/22/2013, 15:36:49 GMT -> ComCtl32 version: 6.16
    4/22/2013, 15:36:49 GMT -> IP Addresses: 10.143.140.57
    4/22/2013, 15:36:49 GMT -> Loading C:\ProgramData\Symantec\LiveUpdate\Product.Inventory.LiveUpdate
    4/22/2013, 15:36:49 GMT -> Opened the product inventory at "C:\ProgramData\Symantec\LiveUpdate\Product.Inventory.LiveUpdate".
    4/22/2013, 15:36:49 GMT -> Combined Product Inventory Flags 0, Permanent Flags 0, Permanent Flags Filter 0
    4/22/2013, 15:36:49 GMT -> LiveUpdate flag value for this run is 0
    4/22/2013, 15:36:52 GMT -> LuComServer version: 3.3.100.15
    4/22/2013, 15:36:52 GMT -> LiveUpdate Language: English
    4/22/2013, 15:36:52 GMT -> LuComServer Sequence Number: 20120518
    4/22/2013, 15:36:52 GMT -> OS: Windows 2008R2 Standard Edition, Service Pack: 1, Major: 6, Minor: 1, Build: 7601 (64-bit)
    4/22/2013, 15:36:52 GMT -> System Language:[0x0409], User Language:[0x0409]
    4/22/2013, 15:36:52 GMT -> IE9 support.
    4/22/2013, 15:36:52 GMT -> ComCtl32 version: 6.16
    4/22/2013, 15:36:52 GMT -> IP Addresses: 10.143.140.57
    4/22/2013, 15:36:52 GMT -> Loading C:\ProgramData\Symantec\LiveUpdate\Product.Inventory.LiveUpdate
    4/22/2013, 15:36:52 GMT -> Opened the product inventory at "C:\ProgramData\Symantec\LiveUpdate\Product.Inventory.LiveUpdate".
    4/22/2013, 15:36:52 GMT -> Combined Product Inventory Flags 0, Permanent Flags 0, Permanent Flags Filter 0
    4/22/2013, 15:36:52 GMT -> LiveUpdate flag value for this run is 0
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////
    // End LuComServer
    ////////////////////////////////////////////////////////////////////////////////
    ////////////////////////////////////////////////////////////////////////////////

     



  • 4.  RE: luall.exe problem

    Posted Apr 22, 2013 10:31 PM

    Schedule Luall uses System account and manual will use logged on account.

    Allow the SYSTEM account access to the internet by configuring your proxy's settings.have you set an Account for Liveupdate service in services window?

     

    • The logon account for LiveUpdate in Services should be set to Local System account (Startup Type: Manual)
    • Open the Control Panel: (On 64-bit systems use Control Panel > View x86 Control Panel Icons)
      1. Double-click Symantec LiveUpdate.
      2. Open the tab HTTP.
      3. Select "I want to customize my HTTP settings for LiveUpdate".
      4. Enter the IP address and HTTP port of your Proxy or Firewall.
      5. Apply the changes and close Symantec LiveUpdate.

    if above does not work then check system account permission



  • 5.  RE: luall.exe problem

    Posted Apr 22, 2013 11:28 PM

    hello,

    Please look mithun comments

    Mithun Sanghavi

    Hello,

    Possible Causes: Legacy proxy settings in the registry still persist after environmental changes on client machine.

    Solution

    The legacy proxy settings can be removed by performing the following steps:

    1.   Open the registry (Start->Run->type "regedit").

    2.  Go to HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings\connections

    3.  Delete the registry keys "DefaultConnectionSettings" and "SavedLegacySettings".

    4.  Reboot the machine.

    Note:  These registry keys will automatically regenerate after reboot of machine.

     

    Also, this also could be caused due to incorrect proxy server information in the following registry location: HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\InternetSettings

    Removing the incorrect proxy info from this key and then rebooting allowed the client to communicate normally.

    One important thing to keep in mind is that any incorrect proxy information must also be removed from the following two locations as well:

    HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\SavedLegacySettings

    If the settings are not removed from these two keys, they will repopulate the Internet Settings key after every reboot.

    Remove the incorrect proxy information from all 3 registry locations noted above, then reboot.

     

    Just to add, in many of my cases, where was an issue with the System Account at User Proxy Level. They had to Bypass the Proxy on the server.



  • 6.  RE: luall.exe problem

    Posted Apr 23, 2013 12:12 AM

    Hi

    Please check the Proxy settings

    Regards

     



  • 7.  RE: luall.exe problem

    Posted Apr 23, 2013 12:24 AM

    Check it

    https://www-secure.symantec.com/connect/forums/sepm-liveupdate-has-error-liveupdate-encountered-one-or-more-errors-return-code-4#comment-5355701



  • 8.  RE: luall.exe problem

    Posted Apr 30, 2013 04:54 AM

    Hello

    I did all this step and finaly problem was on proxy .



  • 9.  RE: luall.exe problem

    Posted Apr 30, 2013 05:03 AM

    It's great that your issue resolve.

    What was the issue in proxy, kindly confirm so it will be help to other if this type of issue can occur?



  • 10.  RE: luall.exe problem
    Best Answer

    Posted Apr 30, 2013 05:09 AM

    hello

    The solution is add bypass for website for TCP http 80 and https 443 

    Liveupdate.symantecliveupdate.com

    Liveupdate.symantec.com

    Symantec.com