larger SEM5.db for SEP 11

Hi,
if the connectiion is DB is working fine, then there is issue with the LU of the SEPM.

Manually initiate the LU from the sepm console, let us know the outcome. you may also check by dropping the jdb file on the SEPM to check if the SEPM definitions are corrupted.

Pete!

 today i just realise that the Client is update itself to 25  may. but then, from the manager console, it show the virus definition is 21 may. The client should update from the server and not from client side. i not sure what had happen? is it we need to restart the server to let it become fresh?

hi,
you mean the client has policy only to update the definition from SEPM?

Is the LU enabled on client ?

you may try rebooting the SEPM, however as stated earlier, manually initiate the LU from the sepm console, let us know the outcome. you may also check by dropping the jdb file on the SEPM to check if the SEPM definitions are corrupted.

Pete!

 LU is not anable on client mode. i had reboot the SEPM and i manually downloa dthe jdb to manager to let it update its own virus definition. today, i saw the monitoring. it state that there is 1 computer with the 25 may virus definition. others still the same. until monitoring. i cant the 25 may virus definition on the client mode. not sure whether this 25 may refer to the endpoint manager or not. and my server itself has its own client mode. it is state as 26 may virus definition. it is so weird. which i not sure how to do now.

 My monitoring status all the clients is using 21 MAY definition.  but then, my clients all have the latest virus definition. what had happen? is it the communication problems with the manager and the client? what should i do? 

this problems occurs, because i had move the symantec sem5.db from C drive to D Drive.  after test communication, everything is fine. does any1 can help on this matter. i will really appreciate. thanks you.

hi,

in my opiniion you open a support case with Symantec.

It's my guess, the clients are communicating with the server since you said "The client should update from the server and not from client side." , that menas it only gets the definitin from server.

The issue migt be processing of the logs on the server and from server to DB.Hence there is no update on the SEPM console!!!

Cheers
Pete!

 how am i going to open a support case from symantec ?

Hi

I can u please tell wether ur clients are offline or still connected to SEPM.

I think there is absolutly no need to open a case for it. There is many such Liveupdate isues has been solved in this community. You need to elaborate and explain ur issue propely. It will be ressolved.

Ajit

plz tell what is size (GB) of sem5.db file and which verstion u have installed... MR2 or MR3 or MR4.
which is you have installed...