Endpoint Protection

My 11.0.5 SEPM has stopped downloading just the 64-bit antivirus definition updates with the last good one on 11/19/14!  After I manually fire off a Download in my SEPM, I don't even see an x64 AV entry in the list which seems to indicate it's not posted on Symantec's website.  I've seen situations where the 64 or 32-bit defs don't update although they're still both listed in the Downloads status window unlike this time.  Anyone else see this as well on your SEP 11 server?

Did you try the JDB file?

Download .jdb files to update definitions for Endpoint Protection Manager

Sometimes it will be for 32 sometimes it will be for 64. please follow this document

https://www-secure.symantec.com/connect/articles/how-clear-corrupt-virus-definitions-sepm

you are with very old version, 11.0.5 had loads of issues. SEP 11 is reaching E0L next year better to plan for 12 upgrade at the earliest

No...I didn't try this yet because as I mentioned, unlike other times where I've seen this problem, I'd see both the 32 and 64-bit AV defs in the Downloads list.  The fact that I don't see the x64 one at all made me think that it's not even being offered on Symantec's end.

11.x is going EOL but not til Jan 2015 and even then you will still receive defs a little while longer.

Tried dropping in the jdb although it created a 141120039 folder (thought it would've been "141121xxx" instead with today's date) which just contains full.zip.  I can open the zip file but SEPM isn't doing the extraction for some reason.

open the sepm

under admin servers tab, if u hight light the local host at the bottom it would the processing messages. do you see those? if not try clearing the defs as I mentioned in the post and then drop the jdb again.

if it has created folder , 99% it would update.give it some time

Yes...I do see processing messages but don't see the AV ones.  I wonder if I don't fix this problem before upgrading to SEP 12 whether it'll carry forward or not.  I'm leaning towards fixing it first and came across http://www.symantec.com/business/support/index?page=content&id=TECH104721 as another possible resolution.  Any comments on this procedure?

Resolved the problem!  It's a somewhat obscure issue that has to do with a database limitation in SQL 2005.  Check out the following tech article for more details.

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