Mitigating solution to the errors - at least we stop messages in the Event Log for the time being till there is a fix.

Symantec knows about this one and they are working on it - No fix ETA yet

Mod Note: Please do not use any profanities in the the forums. For guidlines please see the Discussion Forums Terms and Conditions.

Thank you.

Message Edited by Optimus Prime on 02-15-2008 02:55 PM

I got this from Symantec, however it didn't work. Then they asked me to run a file called SymBatchSEP that they sent me which made a 130MB log file. He didn't seem aware that other users were having the same problem!

First download the latest definitions according to this KB article, do not yet copy the file to the folder mentioned in the article ;

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

Once its downloaded, follow thes steps;

Delete the folders:

C:\Program Files\Common Files\Symantec Shared\SymcData\sesmvirdef32
C:\Program Files\Common Files\Symantec Shared\SymcData\sesmvirdef64

Delete the contents of the LiveUpdate downloads folder.
C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\

4. Copy the downloaded .jdb file to the folder mentioned in above KB article.

As mentioned in the article, the Manager will process the file and update the clients, after this you should not see the messages appear in the Event Viewer anymore.

eagerly awaiting something official from Symantec...perhaps a KB article or a solution posted on the forum

Hey Guys,
I'm having the same issues but, I was able to free up some bandwidth until the issue is resolved.
Go to Clients--> Policies--> Communication Settings.
Change the client mode from Push to Pull and set your heartbeat interval to an hour or two.

This is not a fix! Just a way to stop the bog down of Push mode until the problem is fixed. I hope this helps you guys get through this mess. Just remember to set it back to Push mode (if that's what you used prior to this error)

crud! just realized someone mentioned this earlier in the thread. My apologies!

Message Edited by JTF on 02-13-2008 10:32 AM

Hi all,

Well, i decide to take the hard way and seems to work, or at least i see no more messages in the event viewer.... and the liveupdate from the SEPM seems to work ok again....

I follow tihs note

http://service1.symantec.com/support/ent-security....

I'm still trying to fix the problem with the report page where the virusdef informed is not the correct.

Message Edited by Steven Bright on 02-13-2008 10:46 AM

Message Edited by ADutch1 on 02-13-2008 11:11 AM

I'm having the same issue. Just looking for a reply and potential fix for this issue and to bump the thread.

If this helps anyone, it appeared as though the 2/13/2008 updates didn't fix the error messages initially but, I waited about 20 minutes and the error messages stopped. Keep checking the Event Viewer to verify the update didn't fix the errors because on my end, the errors have finally dissipated.

**Ignore this post. Error messages have returned from the dead**

Message Edited by JTF on 02-13-2008 05:44 PM

Message Edited by Steven Bright on 02-13-2008 08:24 PM

Guys - JimW is correct and we stopped the logs from flooding following similar advice very early on in the thread.
Check the first page of this thread...

Jim if possible keep us posted on this.

TY.

Hi,

On my side, rolling back Decomposer Definitions to 2007.12.20 doesn't fix the problem. But unckecking Updates of Decomposer Definitions successfully stops the error messages.

Confirmation that disabling Decomposer signatures has aleviated Event ID 55 & 58 client errors. 
Waiting for solution from Symantec.
Bump.

Good News. Hope it fixes the problem. Our Clients need a short break :smileywink:

It worked for us as well.

Can we get a post on when the new defs are released so we can download and test them asap?

Thanks

Message Edited by Screen_Name on 02-14-2008 06:31 AM

I'm very glad to hear that a solution is in the works. Standard Event ID 55/58's are showing up but, they are back to the heartbeat intervals (rather than every 1-2 minutes). I can't wait until this little bugger goes the way of the dodo.