LiveUpdate error - SescLU Event 13

Greetings!

I have numerous servers running both Symantec SAV10 and SEP clients (we're in the middle of migrating) that are being inundated with the following error in the Application Event Log:

Event Type:  Error
Event Source:  SescLU
Event Category:  None
Event ID:  13
Date:  4/29/2010
Time:  5:47:56 AM
User:  N/A
Computer:  <server name>
Description:
LiveUpdate returned a non-critical error.  Available content updates may have failed to install.

I've been unable to isolate a root cause/resolution.  Has anyone ran into this issue?  If so, please share your knowledge.

Thank you,
Exemplar
 
LVL 6
ExemplarAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
konduriCommented:
Hi,
Verify that the new content package has been downloaded to Symantec Endpoint Protection Manager by checking that it is listed under the LiveUpdate Content policy
Verify that you have the content type in question set to "use latest available" in the LiveUpdate Content policy
Verify that intermediate steps in the content flow are up and running
If the content type that is failing is not AV Definitions or IPS Signatures, try deleting the cached revisions of that content under c:\Program Files\Symantec\Symantec Endpoint Protection\ContentCache. This will force a full package to come down via your enabled content channel(s) rather than a delta package.

0
 
jhalapradeepCommented:
Hi,

Please check this symantec forum. The solution for this issue is provided in here

http://www.symantec.com/connect/forums/liveupdate-returned-non-critical-error-available-content-updates-may-have-failed-install-0

Regards,
Pradeep Jhala
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
jhalapradeepCommented:
Hi,

Also check this public article for troubleshooting such kind of issues:

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

Regards,
Pradeep Jhala
0
 
ExemplarAuthor Commented:
Thanks for the comments and ideas.  I will review your suggestions and see if they apply as soon as possible.  Many of the servers with this issue are in production enviroments and painstaking coordination may be necessary to apply the possible fixes.

I will let you know.

Thanks again,
Exemplar
0
 
NicksedCommented:
Please let us know how you get on I am having the same issue and will be reading the possible solutions and trying them over the next few days. I will update the thread.
Thanks all

Nick
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.