Video Screencast Help

SEPM 12 embedded database rebuild fails

Created: 04 Oct 2011 • Updated: 11 Oct 2011 | 8 comments
This issue has been solved. See solution.

this is a SEPM 12 installation

a week ago we started getting this error in the Server Application eventlog (win server 2003):

==========================================

Event Type: Error
Event Source: SQLANY 11.0
Event Category: None
Event ID: 1
Date:  04/10/2011
Time:  12:45:38
User:  N/A
Computer: BHS-MS-003
Description:
The description for Event ID ( 1 ) in Source ( SQLANY 11.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SQLANYs_sem5, *** ERROR *** Assertion failed: 100904[sem5] (11.0.1.2472)
Failed to redo a database operation (id=4, page_no=0x6a, offset=0xe83) - Error: Cannot access file 'C:\Program Files\Symantec\Symantec Endpo.

=====================

Event Type: Error
Event Source: SQLANY 11.0
Event Category: None
Event ID: 1
Date:  04/10/2011
Time:  12:45:39
User:  N/A
Computer: BHS-MS-003
Description:
 The following information is part of the event: SQLANYs_sem5, Internal database error *** ERROR *** Assertion failed: 100904[sem5] (11.0.1.2472)
Failed to redo a database operation (id=4, page_no=0x6a, offset=0xe83) - Error: Cannot access file 'C:\Program Files\Symantec\Symantec Endpo -- transaction rolled back.

=============================
Event Type: Error
Event Source: SQLANY 11.0
Event Category: None
Event ID: 1
Date:  04/10/2011
Time:  12:45:39
User:  N/A
Computer: BHS-MS-003
Description:
The following information is part of the event: SQLANYs_sem5, Could not start server.

=================================================

The  Endpoint Protection Manager service will start, but after the Embedded Database service fails to start the Endpoint Protection Manager sevrice stops.

I cannot login to the database.

I initially discovered the problem when I tried to login. I couldn't so ended up running resetpass.bat - however this failed becuase a connection to the database could not be made. That's when I dug deeper into event logs.

I have tried to run the rebuild process described here:

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

but at Step 6 (running the unload command)  I get the error ***** SQL error: Request to start/stop database denied

I suspect this is a password problem for the DBA account. The technician who did the original install assures me that he used the default password (which I take to be "admin") but that doesn't work.

I have no backups of the databse or settings (stupid I know).

what are my options from here please?

Comments 8 CommentsJump to latest comment

Chetan Savade's picture

Hi,

1) Navigate to C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\ within Windows Explorer.

2) Locate the sem5.log and rename it to sem5.log.old

3) Open a command prompt  and navigate to the following location: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32

4) Issue the following command: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db

5) Start the Symantec Embedded Database service through the service control manager (services.msc). 

Check this article for more details

http://www.symantec.com/docs/TECH169664 

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

jon_manager's picture

thanks - close but no cigar!

The dbsrv11 -f process ran and a little window popped up as that was happening. Once that was complete I restarted Protection Manager service (ok) and then embedded database which started and immediately closed.

Event log has a different message:

SQLANYs_sem5, Unable to initialize requested communication links

Chetan Savade's picture

Hi,

Run the dbvalidator.bat general installation path would be C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools\dbvalidator.bat

After executing batch file logs will be created at following location by name dbvalidator.log

C:\Program Files\Symantec\Symantec Endpoint Protection Manager \tomcat\logs\dbvalidator

Please share log file with us

Also try to repair your SEPM through add/remove programs.

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

jon_manager's picture

I'm trying the installation repair now. Here is th eoutput from dbvalidator and scm-server log files

dbvalidator.log

========================

2011-10-04 16:24:30.172 THREAD 1 INFO: logger initialized ...
2011-10-04 16:24:30.188 THREAD 1 INFO: SEPM Server Home:[C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat]
2011-10-04 16:24:53.828 THREAD 1 INFO: Initialized the database.
2011-10-04 16:25:14.202 THREAD 1 SEVERE: Error occurred.
com.sygate.scm.server.metadata.MetadataException:
 at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:899)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:865)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:905)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:931)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:234)
 at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)
 at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)
 at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:348)
 at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2068)
 at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:120)
 at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:547)
Caused by: java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Specified database not found
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
 at java.sql.DriverManager.getConnection(DriverManager.java:582)
 at java.sql.DriverManager.getConnection(DriverManager.java:207)
 at ianywhere.ml.jdbcodbc.jdbc3.ASADataSource.getConnection(ASADataSource.java:313)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:520)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:402)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:392)
 at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:897)
 ... 10 more
com.sygate.scm.server.util.ServerException: Unexpected server error.
 at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:379)
 at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)
 at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:348)
 at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2068)
 at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:120)
 at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:547)
Caused by: com.sygate.scm.server.metadata.MetadataException:
 at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:899)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:865)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:905)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:931)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:234)
 at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)
 ... 5 more
Caused by: java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Specified database not found
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
 at java.sql.DriverManager.getConnection(DriverManager.java:582)
 at java.sql.DriverManager.getConnection(DriverManager.java:207)
 at ianywhere.ml.jdbcodbc.jdbc3.ASADataSource.getConnection(ASADataSource.java:313)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:520)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:402)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:392)
 at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:897)
 ... 10 more
=================================

scm-server log

=================================

2011-10-04 16:24:28.969 THREAD 1 SEVERE: ================== Server Environment ===================
2011-10-04 16:24:29.156 THREAD 1 SEVERE: os.name = Windows 2003
2011-10-04 16:24:29.156 THREAD 1 SEVERE: os.version = 5.2
2011-10-04 16:24:29.172 THREAD 1 SEVERE: os.arch = x86
2011-10-04 16:24:29.172 THREAD 1 SEVERE: java.version = 1.6.0_24
2011-10-04 16:24:29.172 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2011-10-04 16:24:29.172 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2011-10-04 16:24:29.172 THREAD 1 SEVERE: java.vm.version = 19.1-b02
2011-10-04 16:24:29.188 THREAD 1 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jre
2011-10-04 16:24:29.188 THREAD 1 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat
2011-10-04 16:24:29.188 THREAD 1 SEVERE: java.user = null
2011-10-04 16:24:29.203 THREAD 1 SEVERE: user.language = en
2011-10-04 16:24:29.203 THREAD 1 SEVERE: user.country = GB
2011-10-04 16:24:29.203 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
2011-10-04 16:24:53.781 THREAD 1 SEVERE:
java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Specified database not found
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
 at java.sql.DriverManager.getConnection(DriverManager.java:582)
 at java.sql.DriverManager.getConnection(DriverManager.java:207)
 at ianywhere.ml.jdbcodbc.jdbc3.ASADataSource.getConnection(ASADataSource.java:313)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:520)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:402)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:392)
 at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2849)
 at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2829)
 at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2659)
 at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:98)
 at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:547)
2011-10-04 16:25:14.202 THREAD 1 SEVERE:
java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Specified database not found
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
 at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
 at java.sql.DriverManager.getConnection(DriverManager.java:582)
 at java.sql.DriverManager.getConnection(DriverManager.java:207)
 at ianywhere.ml.jdbcodbc.jdbc3.ASADataSource.getConnection(ASADataSource.java:313)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:520)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:402)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:392)
 at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:897)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:865)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:905)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:931)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:234)
 at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)
 at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)
 at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:348)
 at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2068)
 at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:120)
 at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:547)
==========================

Elisha's picture

Do you have a database backup from before this issue started happening?  If so I would recommend using that backup and restoring the database back to what it was.

jon_manager's picture

Elisha - please see the bottom of my first post - no backups are available :-(

pete_4u2002's picture

looks like you need to reinstall SEPM with only certificate backup.

SOLUTION
jon_manager's picture

the repair itself was 'successful', but when the Configuration management process automatically ran I couldn't get past the embedded database startup problem. the same error is repeated in the eventlog : Unable to initialize requested communication links 

pete - what do you mean by 'reinstall SEPM with only certificate backup'?