How to periodically free up the space used by the sem5.log in EPSBE 12.1 RU1
***Important*** The issue is fixed with MP1.
Problem
With EPSBE 12.1 RU1, there is no option to truncate the sem5.log which is constantly increasing in size.
Solution
Create a batch file to automatically delete the current sem5.log and add it to the Windows Task Scheduler.
IMPORTANT: THIS IS NOT OFFICIAL OR SUPPORTED
1) How to create the batch file
1. Open notepad.exe,
2. Copy/paste the following into the notepad:
net stop semsrv
net stop SQLANYs_sem5
attrib -r "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
del "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
net start SQLANYs_sem5
net start semsrv
Note: following your OS, you might need to change the folder path adequately.
3. Save it as a .bat file.
2) How to create the scheduled task
1. Go to Start > All programs > Accessories > System Tools
2. Click on Task Scheduler,
3. Task Scheduler Library,
4. Create Task... from the Actions pane:
5. From the General tab, enter a name and select Run with highest privileges:
6. From the Triggers tab, click on New and set the time to run the task:
7. From the Actions tab, click New and add the bat file:
8. Finally, clickOK,
9. The task is now created:
10. Close the Task Scheduler.
IMPORTANT: THIS IS NOT OFFICIAL OR SUPPORTED
Comments 16 Comments • Jump to latest comment
This work-around is helpful!
Thanks & Regards,
AR Sharma, CISSP
IBM Certified System Admin- Lotus Domino V7
ITIL V2 Certified
Hi Sharma,
Thank you for your comment! Very appreciated.
Best regards,
Shulk
Nice but one que. Is there any Impact removing Sem5.log?
Regards,
S2S
Please don't forget to mark your thread solved with whatever answer helped you.
Considering that SEP SBE 12.1 RU1 was released back in November, it's pretty sad this won't be fixed till April. Every RU1 manager I have installed is exhibiting this behavior.
Thanks for posting your script Shulk.
Hi All,
A good news regarding the Sem5.log! There is no need to wait MP1 since we have release a fix tool to correct this issue.
Don't hesitate to contact us and we will provide you the fix tool.
Thanks to all for your patience and understanding ;)
Best regards,
Shulk
The good news is that this appears to work (I have my doubts since dbsrv -f also worked... for a week). The bad news is you need to call Symantec, create a new case, convince the rep to send you the tool, and receive an email with the attachment missing because it was flagged for security reasons.
It did tell me the attachment name (database_truncate.zip), which I googled, downloaded, then uploaded to virustotal. The zip file is password protected, which happens to be the same password as Symantec Antivirus' default uninstall password.
Enjoy.
I called Symantec support and opened a new case. They denied there was any such tool available. Is there something I can give them to reference this?
Hi Jason,
Could you provide me your case number in private message ?
Best regards,
Shulk
Symantec's Official Article on the subject:
With thanks and best regards,
Mick
good article
Hi Mick2009,
Correct - anyway, both articles are now no longer up to date since the Fix Tool, which re-enable the database log truncation and re-indexing, has been released.
My article was published some time before the Fix Tool has been announced and the purpose of it was to help our customers until either the fix or MP1 comes out.
Best regards,
Shulk
Please do continue to create such articles, Shulk!
With thanks and best regards,
Mick
The release which fixes this truncation issue for SEP SBE 12.1 RU1 is now available. Please upgrade to SEP 12.1 RU1 MP1 and the embedded database will automatically truncate its log.
With thanks and best regards,
Mick
Best regards,
Shulk
Hi Sulk,
and what we can do on Sepm 11.0.6 using sql as database?
thanks
Hi Vevc,
Make sure that the db maintenance tasks are enabled, either within SQL or the SEPM.
This KB should help you out:
http://www.symantec.com/docs/HOWTO55340
Best regards,
Shulk
Would you like to reply?
Login or Register to post your comment.