Endpoint Protection Small Business Edition

I have a client running Server 2008 R2 with SEPM 12.1

I got a notification that the embedded database had stopped. On logging in remotely I found the server very short of disk space, but when I checked out the SEPM folders I discovered that both the sem5.db file and the sem5.log files are both missing - completely vanished. The users claim not to have done anything and having run 2 undelete utilities neither of them could find the files either. Very odd. Last time I checked them about a month ago they were 5 GB and 1 GB in size respectively.

I have tried running a repair of the program 3 times. Each time it has said that the repair completed successfully, but when it then starts the Reconfiguration wizard, even with different options taken each time it fails to complete with the message that  the embedded database could not be started. The repair is not creating or recreating the missing files even though it says that it is going to.

When is a repair not a repair - when its a Symantec repair!!

We do not have a backup of these files.

Is there any way to get the program working again without having to do a complete uninstall and reinstall?

If we do have to do that, will I also have to reinstall on all the clients as well?

 

Not sure how it could go missing...no you won't need to re-install clients, just replace the sylink on them to get them pointed back to the SEPM after doing a new install.

Restoring client-server communications with Communication Update Package Deployment

You can do a search for sem5.db.. I belive its been deleted not sure who did that

best bet is to install a fresh copy of SEPM

use this method to get all your clients under new sepm

http://www.symantec.com/business/support/index?page=content&id=TECH199124

Hi,

Thank you for posting in Symantec community.

5GB database size is OK but 1GB size for sem5.log file is too high.

This is odd scenerio where database file and log files are missing.

I believe you will have to reinstall SEPM. 

Reinstall of client is not necessary, can restore the communication using Sylink.xml.

 

Have you checked the files are hidden? Go to tools and edit conf.properties, change value for group creation from false to true Take backup of the server private key and conf.properties You can reinstall sepm with same private key after new db created and replace the conf.properties and run configuration again so client can able to connect to same DB.