Endpoint Protection

The Symantec Endpoint Protection Manager database has gone down and needs immediate attention.

I enable service and but in the next hour, it stopped again.

can you post the err.log in the following location ?

Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\DB\

What type of database are you using? Embedded or SQL? 

What type of database are you using? Embedded or SQL? 

I used Embedded 

My log file 

07/10 21:28:02. Fatal error:  disk full when writing to "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.log"
11/10 09:25:27. Cannot open transaction log file -- Can't use log file "sem5.log" since it is shorter than expected
12/12 11:32:01. *** ERROR *** Assertion failed: 201503 (12.0.1.3554)[sem5]
Record 0x1 not present on page 0x0:0x26b
01/04 08:34:06. *** ERROR *** Assertion failed: 200106 (12.0.1.3554)[sem5]
attempting to add row twice
01/04 09:56:05. *** ERROR *** Assertion failed: 200106 (12.0.1.3554)[sem5]
attempting to add row twice
01/04 09:59:06. *** ERROR *** Assertion failed: 200106 (12.0.1.3554)[sem5]
attempting to add row twice
01/04 12:27:55. *** ERROR *** Assertion failed: 200106 (12.0.1.3554)[sem5]
attempting to add row twice
01/04 12:33:21. *** ERROR *** Assertion failed: 200106 (12.0.1.3554)[sem5]
attempting to add row twice

Try using the database tool. Think you might have to adjust the below to dbsrv16 now. But used to work for me when I had embedded database issues. You'll probably find the sem5 log file has got too big. 

1. Stop the Symantec Endpoint Protection Manager and Symantec Embedded Database services.
   2) Rename or delete the current sem5.log (C:\Symantec Endpoint Manager\db)
   3) Click Start > Run and type CMD then click OK 
   4) In the Command Prompt type:
2.     For 64-bit: cd C:\Symantec Endpoint Manager\ASA\win32
   5) Press Enter. This will change directories to the folder containing dbsrv12.exe.
   6) To force the recreation of sem5.log, type:
       dbsrv12 -f "C:\Symantec Endpoint Manager\db\sem5.db"     (There is a space after -f and "C:\...)
   7) Press Enter
   8) Click Start > Run and type services.msc then click OK
   9) Start the Symantec Endpoint Protection Manager and Symantec Embedded Database services

 log file too big aready solve but now I have problem Assertion failed

I already did GeoGeo comment but SEPM  database disconnect on 9 PM

How many clients do you have connected to the SEPM? 

looks like your DB is on dying and might fail on you any time, so it is time for you to perform a Disaster recovery.

I have 10 Clients connected to SEPM

Ok 10 clients shouldn't create an issue. It's either going to be a recovery of the database (disaster recovery or re-install) or raise a case with symantec to see if there's any tools they have to repair the database 

Your log file says "07/10 21:28:02. Fatal error:  disk full when writing" so make sure you have some free space on it first before doing anything else.

Once freed up, use the dbvalidator.bat tool (under Tools) to check the status of your database and report back here with any results.

Log file too big already solve.

here is result of dbvalidator.log

--------------

2016-01-08 09:12:50.996 THREAD 1 INFO: logger initialized ...
2016-01-08 09:12:50.997 THREAD 1 INFO: SEPM Server Home:[C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat]
2016-01-08 09:13:51.382 THREAD 1 INFO: Initialized the database.
2016-01-08 09:14:50.797 THREAD 1 SEVERE: Error occurred.
com.sygate.scm.server.metadata.MetadataException: 
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:965)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:931)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:971)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:997)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:254)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:405)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:318)
    at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:337)
    at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2191)
    at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:119)
    at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:498)
Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Database server not found
    at sybase.jdbc4.sqlanywhere.IDriver.makeODBCConnection(Native Method)
    at sybase.jdbc4.sqlanywhere.IDriver.connect(IDriver.java:772)
    at java.sql.DriverManager.getConnection(DriverManager.java:571)
    at java.sql.DriverManager.getConnection(DriverManager.java:233)
    at sybase.jdbc4.sqlanywhere.ASADataSource.getConnection(ASADataSource.java:317)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:402)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:286)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:271)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:261)
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:963)
    ... 10 more
com.sygate.scm.server.util.ServerException: Unexpected server error.
    at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:422)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:318)
    at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:337)
    at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2191)
    at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:119)
    at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:498)
Caused by: com.sygate.scm.server.metadata.MetadataException: 
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:965)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:931)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:971)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:997)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:254)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:405)
    ... 5 more
Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Database server not found
    at sybase.jdbc4.sqlanywhere.IDriver.makeODBCConnection(Native Method)
    at sybase.jdbc4.sqlanywhere.IDriver.connect(IDriver.java:772)
    at java.sql.DriverManager.getConnection(DriverManager.java:571)
    at java.sql.DriverManager.getConnection(DriverManager.java:233)
    at sybase.jdbc4.sqlanywhere.ASADataSource.getConnection(ASADataSource.java:317)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:402)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:286)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:271)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:261)
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:963)
    ... 10 more

Do you have any idea?

I finished re-install that can fix this issue

Hi,

So you have reinstalled and this is now working now? If so, that's great news!

Please mark the best answer as the solution to close this topic.

Many thanks for letting us know.