SEPM LiveUpdate is not functioning after the server's clock was accidentally moved into the future
|Article:TECH182913|||||Created: 2012-03-02|||||Updated: 2012-03-13|||||Article URL http://www.symantec.com/docs/TECH182913|
After the Symantec Endpoint Protection Manager (SEPM) server's time clock was advanced inadvertently into the future, automatic LiveUpdate will not run. The mini server event log in the console does not show the correct and most current information.
Log time stamps are incorrect and in the future after fixing the SEPM's time date issue.
- SEPM time date stamp was moved into the future and fixed
- After resolving the time/date issue, event going forward are still logged in the future
- Automatic LiveUpdates are not working correctly
- The date on the SEPM machine was set one year into the future
- While the date was wrong LiveUpdate had finished and entered log data with the future time/date stamp
- All events going forward are logged with the future date and cause it to not run
This is expected behavior based on the design. When events are completed they are logged with the time stamp when they happened and are inserted into the database. Subsequent scheduled or timed events such as LiveUpdate use those entries to base the future scheduling on. Events inserted with a future date can skew or prevent them from running as expected. To resolve this issue, there is a tool included in the SEPM tools directory. Please follow the instructions below.
- Locate the SEPM tools directory (...\Symantec Endpoint Protection Manager\Tools\)
- Stop the SEPM service
- Run the tool updatedbtime.bat
- Start the SEPM service
Article URL http://www.symantec.com/docs/TECH182913