Sem5.log symantec log file consuming much space.

                                   Sem5.log - Consuming the huge disk space

You will notice that Symantec folder in program files will EAT all of your disk space.

When you go and further investigate, you will be came to know that Sem5.log file in the path
"C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\" will be the culprit.

What to do now ??? :-(
.
.
.
. no worries :-) 

you can manually recreate  sem5.log and delete the old one.

Procedure for force creation of  sem5.log

• Stop the Symantec Endpoint Protection Manager and Symantec Embedded Database services. 
• Rename the current sem5.log
• Click Start > Run and type CMD then click OK
• Open the command prompt and Type the following to go to the folder containing dbsrv11.exe.
  
  For 32 bit:  CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\
  For 64 bit: CD C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32\   
• Press Enter and now you are redirected to the folder  containing dbsrv11.exe
• To force the recreation of sem5.log, type:
  For 32-bit: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"    
  For 64-bit: dbsrv11 -f "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"   
• Press Enter
• Click Start > Run and type services.msc then click OK 
• Start the Symantec Endpoint Protection Manager and Symantec Embedded Database services.

 Now verify that new SEM5.log file is created and once you confirmed delete the old log.

This will do the magic and free up the space.

Read More [...]

Posted in Microsoft Windows, Symantec

Backup Exec Service is not getting started

Today I came across an issue where Backup Exec Service is not getting started.

·         While I was  trying to start the service it is giving an error “The Backup Exec Server service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs”.

·      

         cause might be this “After running Live Update and the "LUGETUPDATES.exe" process is still running on the Backup Exec Media Server. This may cause the Backup Exec Server Service (Beserver.exe) from starting correctly”.

·        

         Solution for this issue is first we have to kill "LUGETUPDATES.exe" process from task manager and try restarting the “Backup Exec Service”, now the service will rock again. It will start without any issues.

Read More [...]

Posted in Backup Technologies, Microsoft Windows, Symantec