SEPM Shown Wrong Date.

[Migration User]

Hi Team,

My SEPM server is updated as per shedule and client also takong update from server.

But on Dashborad latest SEPM Manager date has shown past day.

 

[Migration User]

Can you share screen shot ?

[Rafeeq]

Try this document

Clients cannot send data back to Symantec Endpoint Protection Manager

 

Article:TECH105348

|

Created: 2008-01-09

|

Updated: 2009-01-30

|

Article URLhttp://www.symantec.com/docs/TECH105348

 Browse to \Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agentinfo

2. Look for any .err files or tmp files & Dat files

3. If you find anything which is not processed by sepm then it might be the reason for the client data loss

4. Stop SEPM services from services.msc 

5. Delete all the files inside the location \Program Files\Symantec\Symantec Endpoint Protection Manager\data\inbox\agentinfo

6. Restart the SEPM services.

 

[Migration User]

I have cheked in my sepm 12.1.4 same problem showing SEP client are upto date but Latest on Manager Showing 01/31/2014 r2 May be some problem for symantec side.waiting for next update...

 

 

[Migration User]

Yes same problem We are geeting .

[Migration User]

What SEPM version are you using ?

In My SEPM 11 it's working fine but SEPM 12.1.4 showing wrong date.

[Migration User]

SEPM 12.1 Ru1

 

[Migration User]

& SEPM 12.1 Ru3 got isuue

But It IS not isuue on Ru2

[Migration User]

I think SEPM 12.1.3 and SEPM 12.1.4 are using same virus defination we can wait till next virus defination

http://www.symantec.com/security_response/definitions.jsp?pid=sep1213

[Migration User]

Hi

I think there is a issue with Symantec because we are receiving a call from alll our sites with same problem.  Need to get it checked with Symantec

Regards

 

[Migration User]

Even i am facing the same problem on SEPM 12.1.2,  showing old definition on console but distribution function is working fine.

[solitare]

I'm using SEPM 12.1.4013.4013 and facing the same problem...

[Migration User]

There is some issue in symantec Side,Hopefully will be resolved automatic.

One of another thread raised

https://www-secure.symantec.com/connect/forums/sepm-latest-manager-date-not-changing

[ℬrίαη]

If you need to be updated on status, you can open a support call.

[Mick2009]

Hello all,

The latest certified definitions available at this moment are 2/2/2014 rev. 3 (defs version 160202c).  There is a page that always displays this latest certified version: http://www.symantec.com/security_response/definitions/certified/

If the definitions within an organization are reflecting that information, I would not worry about what is displayed in the SEPM main page.  Treat that as a temporary cosmetic issue and rest assured that the clients have the latest available protection. 

If the clients are not showing that they have 2/2/2014 rev. 3 (or whatever is latest at the moment), then I recommend running LiveUpdate from the SEPM.  If that does not successfully download and apply these latest certified definitions, then using a Rapid Release .jdb file to bring the SEPM up-to-date is an option.

 

How to update definitions for Symantec Endpoint Protection Manager (SEPM) using a .jdb file
 http://www.symantec.com/docs/TECH102607

Hope this helps!

Mick

[Ramji Iyyer]

Hi all,

Its the same issue which occured in 2010.

https://www-secure.symantec.com/connect/forums/official-status-sepm-definitions-stay-31-12-2009-last-updated-04-jan-2010

Log a call with Symantec support with screen shots.

Symantec support will take care.

Relax plz as the definitons are getting updated. No need to panic. 

Regards...

Ramji Iyyer

 

 

 

 

 

[Migration User]

Hi all, We have the same issue ocurring in our SEPM (12 Ru2 MP1) and we already log a call to the Symantec Support. We're wating for a answer. Thanks!

[Migration User]

Hi Everyone,

I have checked now problem are solved,SEPM showing currect virus defination date.

[Migration User]

Hi

The issue has been resolved now and it should show now as per the following

Latest from Symantec: 3/2/2014 rev 19
Latest from Manager: 3/2/2014 rev 19

[Steven Kintakas]

Would be great to hear from Symantec as to what happened, as this thread pretty much confirms this issue WAS a somewhat widespread problem, and we did raise a support case, and thus far have received no answers as to what caused this.

This kind of thing doesn't just randomly happen, at the same time, to dozens and dozens of independantly run SEP environments under our care, or to so many others who have also posted here.