Endpoint Protection

The SEPM failed to download latest definition, that's always errir message even tried to download it manually from 'download definition'

Any clue ?

Hi,

Please let us know the error message you get when you try to download
if you get Error code 4 , thats means its not able to connect to symantec and download
most of the times firewall or proxy isssue.
Please let us know the error u r getting, if error 4 follow the below document please

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007121710290448

hope this helps

Rafeeq

if you facing different issue you may copy the content of log.liveupdate here , experts will suggest you to overcome the problem.

cheers
Pete

Ok try this & let us know where excatly it is failing..

- Go control panal -Symantec Liveudpate ..
- Set liveupdate to interactive Mode.
- Go start - Run & type luall.exe..
- Follow the wizard..

This wizard will tell you where excatly it is failing is it failing to download or install..
Also make sure that in the download list the SEPM is listed..

Do you ahve a proxy in downloading an updates if so try to by pass the proxy then initiate a download update and observe how is the result.

attached the log, pls advise anyone :


7/24/2009, 0:35:24 GMT -> LuComServer version: 3.3.0.85
7/24/2009, 0:35:24 GMT -> LiveUpdate Language: English
7/24/2009, 0:35:24 GMT -> LuComServer Sequence Number: 20090320
7/24/2009, 0:35:24 GMT -> OS: Windows XP Professional, Service Pack: 3, Major: 5, Minor: 1, Build: 2600 (32-bit)
7/24/2009, 0:35:24 GMT -> System Language:[0x0409], User Language:[0x0409]
7/24/2009, 0:35:24 GMT -> IE 7 Support
7/24/2009, 0:35:24 GMT -> ComCtl32 version: 6.0
7/24/2009, 0:35:24 GMT -> IP Addresses: ::1, XXXXXXXXXX
7/24/2009, 0:35:24 GMT -> Loading C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Product.Inventory.LiveUpdate
7/24/2009, 0:35:24 GMT -> Opened the product inventory at "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Product.Inventory.LiveUpdate".
7/24/2009, 0:35:24 GMT -> Account launching LiveUpdate is not a logged in user's account
7/24/2009, 0:35:24 GMT -> Combined Product Inventory Flags 0, Permanent Flags 0, Permanent Flags Filter 0
7/24/2009, 0:35:24 GMT -> LiveUpdate flag value for this run is 0
7/24/2009, 0:35:24 GMT -> **** Starting a Silent LiveUpdate Session ****
7/24/2009, 0:35:24 GMT -> *********************** Start of New LU Session ***********************
7/24/2009, 0:35:25 GMT -> The command line is -S
7/24/2009, 0:35:25 GMT -> EVENT - SESSION START EVENT - The LiveUpdate session is running in Silent Mode.
7/24/2009, 0:35:25 GMT -> Check for updates to: Product: LiveUpdate, Version: 3.3.0.85, Language: English. Mini-TRI file name: liveupdate_3.3.0.85_english_livetri.zip
7/24/2009, 0:35:25 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM Content Catalog with moniker {7073FE74-CAB0-42cc-B839-9808FCB47909}.
7/24/2009, 0:35:25 GMT -> Starting Callback Proxy Worker thread.
7/24/2009, 0:35:25 GMT -> The callback proxy for moniker {7073FE74-CAB0-42cc-B839-9808FCB47909} was successfully registered with LiveUpdate.
7/24/2009, 0:35:25 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Content Catalog.
7/24/2009, 0:35:25 GMT -> LiveUpdate is about to execute a PreSession callback for product SESM Content Catalog.
7/24/2009, 0:50:28 GMT -> ProductRegCom/luProductReg(PID=2196/TID=3652): Successfully created an instance of an luProductReg object!
7/24/2009, 0:50:28 GMT -> ProductRegCom/luProductReg(PID=2196/TID=3652): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 0:50:40 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 0:50:40 GMT -> The PreSession callback for product SESM Content Catalog completed with a result of 0x0
7/24/2009, 0:50:40 GMT -> Progress Update: TRYING_HOST: HostName: "liveupdate.symantecliveupdate.com" URL: "http://liveupdate.symantecliveupdate.com" HostNumber: 0
7/24/2009, 0:50:40 GMT -> LiveUpdate did not find any new updates for the given products.
7/24/2009, 0:50:40 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 1801, The user canceled the LiveUpdate session
7/24/2009, 0:50:40 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Content Catalog.
7/24/2009, 0:50:40 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 0:50:40 GMT -> The PostSession callback for product SESM Content Catalog completed with a result of 0x0
7/24/2009, 0:50:40 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 0:50:40 GMT -> ProductRegCom/luProductReg(PID=2196/TID=3652): Destroyed luProductReg object.
7/24/2009, 0:50:40 GMT -> LiveUpdate has called the last callback for product SESM Content Catalog, so LiveUpdate is informing the callback proxy that it can exit.
7/24/2009, 0:50:40 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win32 with moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264}.
7/24/2009, 0:50:40 GMT -> The callback proxy executable for product {7073FE74-CAB0-42cc-B839-9808FCB47909} is exiting with no errors
7/24/2009, 0:50:40 GMT -> The callback proxy for moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} was successfully registered with LiveUpdate.
7/24/2009, 0:50:40 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win32.
7/24/2009, 0:50:40 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win32.
7/24/2009, 0:58:47 GMT -> ProductRegCom/luProductReg(PID=2968/TID=3236): Successfully created an instance of an luProductReg object!
7/24/2009, 0:58:47 GMT -> ProductRegCom/luProductReg(PID=2968/TID=3236): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:00:08 GMT -> ProductRegCom/luProductReg(PID=2968/TID=3236): Destroyed luProductReg object.
7/24/2009, 1:01:06 GMT -> ProductRegCom/luProductReg(PID=2136/TID=3168): Successfully created an instance of an luProductReg object!
7/24/2009, 1:01:06 GMT -> ProductRegCom/luProductReg(PID=2136/TID=3168): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:02:32 GMT -> ProductRegCom/luProductReg(PID=2136/TID=3168): Destroyed luProductReg object.
7/24/2009, 1:05:42 GMT -> ProductRegCom/luProductReg(PID=188/TID=2276): Successfully created an instance of an luProductReg object!
7/24/2009, 1:05:42 GMT -> ProductRegCom/luProductReg(PID=188/TID=2276): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 1:05:42 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 1:05:42 GMT -> The PostSession callback for product SESM AntiVirus Client Win32 completed with a result of 0x0
7/24/2009, 1:05:42 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 1:05:42 GMT -> ProductRegCom/luProductReg(PID=188/TID=2276): Destroyed luProductReg object.
7/24/2009, 1:05:42 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
7/24/2009, 1:05:42 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win64 with moniker {E4052532-F65C-4007-B620-DBEE893C2B2A}.
7/24/2009, 1:05:42 GMT -> The callback proxy executable for product {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} is exiting with no errors
7/24/2009, 1:05:43 GMT -> The callback proxy for moniker {E4052532-F65C-4007-B620-DBEE893C2B2A} was successfully registered with LiveUpdate.
7/24/2009, 1:05:43 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win64.
7/24/2009, 1:05:43 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win64.
7/24/2009, 1:20:44 GMT -> ProductRegCom/luProductReg(PID=4008/TID=2644): Successfully created an instance of an luProductReg object!
7/24/2009, 1:20:44 GMT -> ProductRegCom/luProductReg(PID=4008/TID=2644): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 1:20:44 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 1:20:44 GMT -> The PostSession callback for product SESM AntiVirus Client Win64 completed with a result of 0x0
7/24/2009, 1:20:44 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 1:20:44 GMT -> ProductRegCom/luProductReg(PID=4008/TID=2644): Destroyed luProductReg object.
7/24/2009, 1:20:44 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
7/24/2009, 1:20:44 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}.
7/24/2009, 1:20:44 GMT -> The callback proxy executable for product {E4052532-F65C-4007-B620-DBEE893C2B2A} is exiting with no errors
7/24/2009, 1:20:44 GMT -> The callback proxy for moniker {A6BA2770-E351-4694-AB02-5358E0F9CDBE} was successfully registered with LiveUpdate.
7/24/2009, 1:20:44 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win32.
7/24/2009, 1:20:44 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win32.
7/24/2009, 1:35:44 GMT -> ProductRegCom/luProductReg(PID=1748/TID=2940): Successfully created an instance of an luProductReg object!
7/24/2009, 1:35:44 GMT -> ProductRegCom/luProductReg(PID=1748/TID=2940): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 1:35:44 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 1:35:44 GMT -> The PostSession callback for product SESM Network Access Control Client Win32 completed with a result of 0x0
7/24/2009, 1:35:44 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 1:35:44 GMT -> ProductRegCom/luProductReg(PID=1748/TID=2940): Destroyed luProductReg object.
7/24/2009, 1:35:44 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.
7/24/2009, 1:35:44 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}.
7/24/2009, 1:35:44 GMT -> The callback proxy executable for product {A6BA2770-E351-4694-AB02-5358E0F9CDBE} is exiting with no errors
7/24/2009, 1:35:45 GMT -> The callback proxy for moniker {C6ACF447-A89C-42d7-A954-E31003AE0B26} was successfully registered with LiveUpdate.
7/24/2009, 1:35:45 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win64.
7/24/2009, 1:35:45 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win64.
7/24/2009, 1:50:45 GMT -> ProductRegCom/luProductReg(PID=3872/TID=2624): Successfully created an instance of an luProductReg object!
7/24/2009, 1:50:45 GMT -> ProductRegCom/luProductReg(PID=3872/TID=2624): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 1:50:45 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 1:50:45 GMT -> The PostSession callback for product SESM Network Access Control Client Win64 completed with a result of 0x0
7/24/2009, 1:50:45 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 1:50:45 GMT -> ProductRegCom/luProductReg(PID=3872/TID=2624): Destroyed luProductReg object.
7/24/2009, 1:50:45 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.
7/24/2009, 1:50:45 GMT -> The callback proxy executable for product {C6ACF447-A89C-42d7-A954-E31003AE0B26} is exiting with no errors
7/24/2009, 1:50:46 GMT -> *********************** End of LU Session ***********************
////////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////
// End LuComServer
////////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////

////////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////
// Start LuComServer
////////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////
7/24/2009, 1:53:12 GMT -> LuComServer version: 3.3.0.85
7/24/2009, 1:53:12 GMT -> LiveUpdate Language: English
7/24/2009, 1:53:12 GMT -> LuComServer Sequence Number: 20090320
7/24/2009, 1:53:12 GMT -> OS: Windows XP Professional, Service Pack: 3, Major: 5, Minor: 1, Build: 2600 (32-bit)
7/24/2009, 1:53:12 GMT -> System Language:[0x0409], User Language:[0x0409]
7/24/2009, 1:53:12 GMT -> IE 7 Support
7/24/2009, 1:53:12 GMT -> ComCtl32 version: 6.0
7/24/2009, 1:53:12 GMT -> IP Addresses: ::1, XXXXXXXX
7/24/2009, 1:53:12 GMT -> Loading C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Product.Inventory.LiveUpdate
7/24/2009, 1:53:12 GMT -> Opened the product inventory at "C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Product.Inventory.LiveUpdate".
7/24/2009, 1:53:12 GMT -> Account launching LiveUpdate is not a logged in user's account
7/24/2009, 1:53:12 GMT -> Combined Product Inventory Flags 0, Permanent Flags 0, Permanent Flags Filter 0
7/24/2009, 1:53:12 GMT -> LiveUpdate flag value for this run is 0
7/24/2009, 1:53:12 GMT -> **** Starting a Silent LiveUpdate Session ****
7/24/2009, 1:53:12 GMT -> *********************** Start of New LU Session ***********************
7/24/2009, 1:53:12 GMT -> The command line is -S
7/24/2009, 1:53:12 GMT -> EVENT - SESSION START EVENT - The LiveUpdate session is running in Silent Mode.
7/24/2009, 1:53:12 GMT -> Check for updates to: Product: LiveUpdate, Version: 3.3.0.85, Language: English. Mini-TRI file name: liveupdate_3.3.0.85_english_livetri.zip
7/24/2009, 1:53:12 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM Content Catalog with moniker {7073FE74-CAB0-42cc-B839-9808FCB47909}.
7/24/2009, 1:53:12 GMT -> Starting Callback Proxy Worker thread.
7/24/2009, 1:53:12 GMT -> The callback proxy for moniker {7073FE74-CAB0-42cc-B839-9808FCB47909} was successfully registered with LiveUpdate.
7/24/2009, 1:53:12 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Content Catalog.
7/24/2009, 1:53:12 GMT -> LiveUpdate is about to execute a PreSession callback for product SESM Content Catalog.
7/24/2009, 1:53:19 GMT -> ProductRegCom/luProductReg(PID=2288/TID=3316): Successfully created an instance of an luProductReg object!
7/24/2009, 1:53:19 GMT -> ProductRegCom/luProductReg(PID=2288/TID=3316): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:53:19 GMT -> ProductRegCom/luProductReg(PID=2288/TID=3316): Destroyed luProductReg object.
7/24/2009, 1:54:19 GMT -> ProductRegCom/luProductReg(PID=2568/TID=2804): Successfully created an instance of an luProductReg object!
7/24/2009, 1:54:19 GMT -> ProductRegCom/luProductReg(PID=2568/TID=2804): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:54:19 GMT -> ProductRegCom/luProductReg(PID=2568/TID=2804): Destroyed luProductReg object.
7/24/2009, 1:55:19 GMT -> ProductRegCom/luProductReg(PID=3324/TID=384): Successfully created an instance of an luProductReg object!
7/24/2009, 1:55:19 GMT -> ProductRegCom/luProductReg(PID=3324/TID=384): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:55:19 GMT -> ProductRegCom/luProductReg(PID=3324/TID=384): Destroyed luProductReg object.
7/24/2009, 1:56:19 GMT -> ProductRegCom/luProductReg(PID=3064/TID=560): Successfully created an instance of an luProductReg object!
7/24/2009, 1:56:19 GMT -> ProductRegCom/luProductReg(PID=3064/TID=560): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:56:19 GMT -> ProductRegCom/luProductReg(PID=3064/TID=560): Destroyed luProductReg object.
7/24/2009, 1:57:18 GMT -> ProductRegCom/luProductReg(PID=2952/TID=3852): Successfully created an instance of an luProductReg object!
7/24/2009, 1:57:18 GMT -> ProductRegCom/luProductReg(PID=2952/TID=3852): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:57:18 GMT -> ProductRegCom/luProductReg(PID=2952/TID=3852): Destroyed luProductReg object.
7/24/2009, 1:58:18 GMT -> ProductRegCom/luProductReg(PID=1736/TID=3600): Successfully created an instance of an luProductReg object!
7/24/2009, 1:58:18 GMT -> ProductRegCom/luProductReg(PID=1736/TID=3600): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:58:18 GMT -> ProductRegCom/luProductReg(PID=1736/TID=3600): Destroyed luProductReg object.
7/24/2009, 1:59:19 GMT -> ProductRegCom/luProductReg(PID=2260/TID=4028): Successfully created an instance of an luProductReg object!
7/24/2009, 1:59:19 GMT -> ProductRegCom/luProductReg(PID=2260/TID=4028): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 1:59:19 GMT -> ProductRegCom/luProductReg(PID=2260/TID=4028): Destroyed luProductReg object.
7/24/2009, 2:00:19 GMT -> ProductRegCom/luProductReg(PID=3244/TID=3148): Successfully created an instance of an luProductReg object!
7/24/2009, 2:00:19 GMT -> ProductRegCom/luProductReg(PID=3244/TID=3148): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:00:19 GMT -> ProductRegCom/luProductReg(PID=3244/TID=3148): Destroyed luProductReg object.
7/24/2009, 2:01:19 GMT -> ProductRegCom/luProductReg(PID=3548/TID=568): Successfully created an instance of an luProductReg object!
7/24/2009, 2:01:19 GMT -> ProductRegCom/luProductReg(PID=3548/TID=568): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:01:19 GMT -> ProductRegCom/luProductReg(PID=3548/TID=568): Destroyed luProductReg object.
7/24/2009, 2:02:19 GMT -> ProductRegCom/luProductReg(PID=2108/TID=2872): Successfully created an instance of an luProductReg object!
7/24/2009, 2:02:19 GMT -> ProductRegCom/luProductReg(PID=2108/TID=2872): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:02:19 GMT -> ProductRegCom/luProductReg(PID=2108/TID=2872): Destroyed luProductReg object.
7/24/2009, 2:03:19 GMT -> ProductRegCom/luProductReg(PID=2812/TID=3552): Successfully created an instance of an luProductReg object!
7/24/2009, 2:03:19 GMT -> ProductRegCom/luProductReg(PID=2812/TID=3552): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:03:19 GMT -> ProductRegCom/luProductReg(PID=2812/TID=3552): Destroyed luProductReg object.
7/24/2009, 2:04:19 GMT -> ProductRegCom/luProductReg(PID=3340/TID=2140): Successfully created an instance of an luProductReg object!
7/24/2009, 2:04:19 GMT -> ProductRegCom/luProductReg(PID=3340/TID=2140): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:04:19 GMT -> ProductRegCom/luProductReg(PID=3340/TID=2140): Destroyed luProductReg object.
7/24/2009, 2:05:19 GMT -> ProductRegCom/luProductReg(PID=1776/TID=3288): Successfully created an instance of an luProductReg object!
7/24/2009, 2:05:19 GMT -> ProductRegCom/luProductReg(PID=1776/TID=3288): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:05:19 GMT -> ProductRegCom/luProductReg(PID=1776/TID=3288): Destroyed luProductReg object.
7/24/2009, 2:06:19 GMT -> ProductRegCom/luProductReg(PID=4004/TID=2216): Successfully created an instance of an luProductReg object!
7/24/2009, 2:06:19 GMT -> ProductRegCom/luProductReg(PID=4004/TID=2216): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:06:19 GMT -> ProductRegCom/luProductReg(PID=4004/TID=2216): Destroyed luProductReg object.
7/24/2009, 2:07:19 GMT -> ProductRegCom/luProductReg(PID=124/TID=3944): Successfully created an instance of an luProductReg object!
7/24/2009, 2:07:19 GMT -> ProductRegCom/luProductReg(PID=124/TID=3944): Path for calling process executable is C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\sesmcontinst.exe.
7/24/2009, 2:07:19 GMT -> ProductRegCom/luProductReg(PID=124/TID=3944): Destroyed luProductReg object.
7/24/2009, 2:08:15 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Successfully created an instance of an luProductReg object!
7/24/2009, 2:08:15 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 2:08:15 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {01BAFA03-6B97-4906-B1E0-D8EFAEEFC618}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:16 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {14AEB036-9BBE-42c1-BA01-B948F11C4BAE}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:17 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {352B4220-A20F-4474-ABB7-A652097EF26C}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:19 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {4884EB8B-77E8-457b-9096-6E9FFE1DC0CA}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:20 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {5B79C00A-F811-449a-8E40-FBB5C297E20B}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:21 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {7EC7284A-7033-45bb-86BD-10A3D1251AFD}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:22 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {9D30944B-771E-4d55-8AF4-FD12CD8EBB51}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:23 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {A25A92D9-B0AD-48de-BBD0-29DC3CEF8FFC}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:23 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {A261B05B-5B02-4f6e-BEFE-688C713FF74C}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:23 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {AC3C3154-0CC4-4fbc-8BBF-AACF4FFD4CC3}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:24 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {B259F24D-C28B-48e9-B8CD-C0AD23D516AA}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:24 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {BB1D2DAC-7DED-4879-90B4-E3DAF2CD5E83}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:25 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {BCBBDC5B-6687-478b-9BEA-46E095D03164}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:25 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {C2A0F497-BA4F-4692-A37D-2EAA69900EE0}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:25 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {C41CDA09-1D42-41c6-A8FC-2257EC441FF4}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:26 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {CF6C189A-CD24-4338-AD65-E495DDB30DE3}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:27 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {DEF4748D-6773-4919-9F62-9BA130334D9B}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:27 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {E89D0525-8788-4824-A412-43C9D0B3E1D1}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:28 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {F4FDEEDA-115D-4140-8E24-DD696AE38029}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:28 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Deleting Property for Moniker = {FD4D935E-EA7F-4529-A14C-7E6C79E65BD7}, PropertyName = LU_SESSION_OPTOUT
7/24/2009, 2:08:28 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 2:08:28 GMT -> The PreSession callback for product SESM Content Catalog completed with a result of 0x0
7/24/2009, 2:08:28 GMT -> Progress Update: TRYING_HOST: HostName: "liveupdate.symantecliveupdate.com" URL: "http://liveupdate.symantecliveupdate.com" HostNumber: 0
7/24/2009, 2:08:28 GMT -> LiveUpdate did not find any new updates for the given products.
7/24/2009, 2:08:28 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 1801, The user canceled the LiveUpdate session
7/24/2009, 2:08:28 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Content Catalog.
7/24/2009, 2:08:28 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 2:08:28 GMT -> The PostSession callback for product SESM Content Catalog completed with a result of 0x0
7/24/2009, 2:08:28 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 2:08:28 GMT -> ProductRegCom/luProductReg(PID=4016/TID=2060): Destroyed luProductReg object.
7/24/2009, 2:08:28 GMT -> LiveUpdate has called the last callback for product SESM Content Catalog, so LiveUpdate is informing the callback proxy that it can exit.
7/24/2009, 2:08:28 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win32 with moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264}.
7/24/2009, 2:08:28 GMT -> The callback proxy executable for product {7073FE74-CAB0-42cc-B839-9808FCB47909} is exiting with no errors
7/24/2009, 2:08:29 GMT -> The callback proxy for moniker {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} was successfully registered with LiveUpdate.
7/24/2009, 2:08:29 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win32.
7/24/2009, 2:08:29 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win32.
7/24/2009, 2:08:32 GMT -> ProductRegCom/luProductReg(PID=1028/TID=2704): Successfully created an instance of an luProductReg object!
7/24/2009, 2:08:32 GMT -> ProductRegCom/luProductReg(PID=1028/TID=2704): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 2:08:32 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 2:08:32 GMT -> The PostSession callback for product SESM AntiVirus Client Win32 completed with a result of 0x0
7/24/2009, 2:08:32 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 2:08:32 GMT -> ProductRegCom/luProductReg(PID=1028/TID=2704): Destroyed luProductReg object.
7/24/2009, 2:08:32 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win32, so LiveUpdate is informing the callback proxy that it can exit.
7/24/2009, 2:08:32 GMT -> LiveUpdate is about to launch a new callback proxy process for product SESM AntiVirus Client Win64 with moniker {E4052532-F65C-4007-B620-DBEE893C2B2A}.
7/24/2009, 2:08:32 GMT -> The callback proxy executable for product {C1CE7FFE-E00E-4314-8C6A-A0F10055C264} is exiting with no errors
7/24/2009, 2:08:32 GMT -> The callback proxy for moniker {E4052532-F65C-4007-B620-DBEE893C2B2A} was successfully registered with LiveUpdate.
7/24/2009, 2:08:32 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM AntiVirus Client Win64.
7/24/2009, 2:08:32 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM AntiVirus Client Win64.
7/24/2009, 2:08:35 GMT -> ProductRegCom/luProductReg(PID=124/TID=3552): Successfully created an instance of an luProductReg object!
7/24/2009, 2:08:35 GMT -> ProductRegCom/luProductReg(PID=124/TID=3552): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 2:08:35 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 2:08:35 GMT -> The PostSession callback for product SESM AntiVirus Client Win64 completed with a result of 0x0
7/24/2009, 2:08:35 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 2:08:35 GMT -> ProductRegCom/luProductReg(PID=124/TID=3552): Destroyed luProductReg object.
7/24/2009, 2:08:35 GMT -> LiveUpdate has called the last callback for product SESM AntiVirus Client Win64, so LiveUpdate is informing the callback proxy that it can exit.
7/24/2009, 2:08:35 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}.
7/24/2009, 2:08:35 GMT -> The callback proxy executable for product {E4052532-F65C-4007-B620-DBEE893C2B2A} is exiting with no errors
7/24/2009, 2:08:35 GMT -> The callback proxy for moniker {A6BA2770-E351-4694-AB02-5358E0F9CDBE} was successfully registered with LiveUpdate.
7/24/2009, 2:08:35 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win32.
7/24/2009, 2:08:35 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win32.
7/24/2009, 2:08:38 GMT -> ProductRegCom/luProductReg(PID=2612/TID=3464): Successfully created an instance of an luProductReg object!
7/24/2009, 2:08:38 GMT -> ProductRegCom/luProductReg(PID=2612/TID=3464): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 2:08:38 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 2:08:38 GMT -> The PostSession callback for product SESM Network Access Control Client Win32 completed with a result of 0x0
7/24/2009, 2:08:38 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 2:08:38 GMT -> ProductRegCom/luProductReg(PID=2612/TID=3464): Destroyed luProductReg object.
7/24/2009, 2:08:38 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.
7/24/2009, 2:08:38 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}.
7/24/2009, 2:08:38 GMT -> The callback proxy executable for product {A6BA2770-E351-4694-AB02-5358E0F9CDBE} is exiting with no errors
7/24/2009, 2:08:38 GMT -> The callback proxy for moniker {C6ACF447-A89C-42d7-A954-E31003AE0B26} was successfully registered with LiveUpdate.
7/24/2009, 2:08:38 GMT -> LiveUpdate successfully launched a new callback proxy process for product SESM Network Access Control Client Win64.
7/24/2009, 2:08:38 GMT -> LiveUpdate is about to execute a PostSession callback for product SESM Network Access Control Client Win64.
7/24/2009, 2:08:41 GMT -> ProductRegCom/luProductReg(PID=3948/TID=1872): Successfully created an instance of an luProductReg object!
7/24/2009, 2:08:41 GMT -> ProductRegCom/luProductReg(PID=3948/TID=1872): Path for calling process executable is C:\Program Files\Symantec\LiveUpdate\LuCallbackProxy.exe.
7/24/2009, 2:08:41 GMT -> The callback proxy finished executing the callback with a result code of 0x0
7/24/2009, 2:08:41 GMT -> The PostSession callback for product SESM Network Access Control Client Win64 completed with a result of 0x0
7/24/2009, 2:08:41 GMT -> Successfully released callback {530DF3AD-6936-3214-A83B-27B63C7997C4}
7/24/2009, 2:08:41 GMT -> ProductRegCom/luProductReg(PID=3948/TID=1872): Destroyed luProductReg object.
7/24/2009, 2:08:41 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.
7/24/2009, 2:08:42 GMT -> The callback proxy executable for product {C6ACF447-A89C-42d7-A954-E31003AE0B26} is exiting with no errors
7/24/2009, 2:08:42 GMT -> *********************** End of LU Session

Hi from the log its evident that

7/24/2009, 0:50:40 GMT -> LiveUpdate did not find any new updates for the given products.
7/24/2009, 0:50:40 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 1801, The user canceled the LiveUpdate session

it says that liveupdate did not find new defs, have you followed these steps before we go further
you may re-register the liveudpate with the manager( repair of sepm will also do this )
liveupdate somehow thinks that it has the latest defs,


follow this link and it should resolve the issue
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008041516215948

try to directly connecting to the internet and let see how it goes

If manual downloading of definition fails, is it a newly installed SEPM? when was the last time you've a successful updates?

Hi Happytohelp,

Everytime I tried to run luall.exe, a small message window prompted - 'live update is currently running, pls wait for live update to complete before continuing', and I hv to press a few time cancel button to get rid on this.

any idea ?

You said when your try to run the luall.exe it gives you a small pop up liveupdate is currently running
Did you try to kill the luall.exe process from the taskmanager & then try to run the luall.exe from the run window.

Hi Rafeeq,

Ya I tried to re-register the liveupdate but it seems not working. I'm trying to follow instruction from your posted article, will update if any problem soon.

Thanks.

yes, killed the process and the only option is to 'retry ' or 'cancel'. Retry will not work all the time.
 

But did the retry ever worked?
if yes whats the error that it gave your?

I will hv to cancel and sometimes it prompt to insert the SEPM installastion cd for liveupdate installation.

Can you check the event logs & see if there any Msi error related to SEP.

here you go:

1.Product: Symantec Endpoint Protection Manager -- Configuration failed.

2.Detection of product '{F21BC620-4230-41D7-8505-36ED42263B35}', feature 'Bin', component '{711CBE62-401D-47AC-8919-4C0029EC66DD}' failed. The resource 'C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\temp\UploadTemp\' does not exist.

3.Detection of product '{F21BC620-4230-41D7-8505-36ED42263B35}', feature 'Bin' failed during request for component '{30A7BFCA-129A-4CB7-8E26-FDCA7C932E98}'

4.Product: Symantec Endpoint Protection Manager -- Error 1706.No valid source could be found for product Symantec Endpoint Protection Manager. The Windows Installer cannot continue.

 

Hi Jim,

If the Download through LiveUpdate worked before, try the following:

Download the latests Definitions file

http://www.symantec.com/business/security_response/definitions/download/detail.jsp?gid=savce

(rename it to .jdb)

Insert it manually into the SEPM following this article:

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007100820002048

It may be the case, that a set of damaged definitions is blocking LiveUpdate.
This will be in most cases solved by this workaround.
After that, let me know, if the normal sheduled download of LiveUpdate worked again.

Rafeeq,


I follow your attached link till steps no. 5, everytime I run luall.exe, the screen will show "the liveupdate is running, pls wait until it complete". I can't proceed further from there.

 

Yes,Im all the while doing manual update into SPEM since I had this liveupdate issue. It works fine but not yesterday after I perform action listed in:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008041516215948

The *.jdb just stucked in \Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\content\incoming folder. I waited for hours and still not updating.
I noticed this error message from SEPM console:
Rapid Response content failed to install. [Site: Endpoint Test Site] [Server: XXXXXXXX]


Any idea will be appreciated.

Can you check the content of the symcdata folder
under C:\program files\common files\Symantec Shared\Symcdata\  there will be sesmvirdef32 & 64 bit folder check the content of these folder there should be some dated folder just delete this folders.

OR if Symcdata folder does not have the sesmvirdef32 & 64 bit folder then create these folder manually over there.

Yes, i've deleted all dated folder and left only 4 folders, which is:
- binhub        - incoming      - definfo.dat       - usage.dat

but I still getting "Rapid Response content failed to install. [Site: Endpoint Test Site] [Server: XXXXXXXX]" from sepm console 

Finally, my liveupdate works after several attempt to reinstall.

Thanks all for the feedback.

Good to see your issue is finally resolved.
Can you please mark the solution to thei thread.:)