Endpoint Protection

 View Only
  • 1.  Embedded Database not running

    Posted Apr 26, 2009 11:42 AM
    I have been running SEPM on a 2003 server for a year and a half now.  Currently I am using the latest version available, MR4 MP1.  Two nights ago I noticed that the green lights were not lit up on the symantec shields in the task bar.  When I investigated the cause I found that the Symantec Endpoint Protection Manager and the Symantec Embedded Database were no longer running on the server.  Restarting either process is futile.
     
    Leading up to the problem nothing was installed or changed on the server.

    In the Windows Event Log I am getting the following Errors when I try to restart the services:

    The Java Virtual Machine has exited with a code of -1, the service is being stopped.
    -
    The description for Event ID ( 1 ) in Source ( ASA 9.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: ASANYs_sem5, Starting service ASANYs_sem5.
    -
    The description for Event ID ( 1 ) in Source ( ASA 9.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: ASANYs_sem5, *** ERROR *** Assertion failed: 101412 (9.0.2.3654)
    Page number on page does not match page requested.
    -
    The description for Event ID ( 1 ) in Source ( ASA 9.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: ASANYs_sem5, Internal database error *** ERROR *** Assertion failed: 101412 (9.0.2.3654)
    Page number on page does not match page requested -- transaction rolled back.
    -
    The description for Event ID ( 1 ) in Source ( ASA 9.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: ASANYs_sem5, Could not start server.
    -



    Below are some of the Symantec Log files:

    scm-log

    2009-04-25 20:05:05.696 SEVERE: ================== Server Environment ===================
    2009-04-25 20:05:05.696 SEVERE: os.name = Windows 2003
    2009-04-25 20:05:05.696 SEVERE: os.version = 5.2
    2009-04-25 20:05:05.696 SEVERE: os.arch = x86
    2009-04-25 20:05:05.696 SEVERE: java.version = 1.5.0_15
    2009-04-25 20:05:05.696 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-04-25 20:05:05.712 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-04-25 20:05:05.712 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-04-25 20:05:05.712 SEVERE: java.home = E:\symantec\jdk\jre
    2009-04-25 20:05:05.712 SEVERE: catalina.home = E:\symantec\tomcat
    2009-04-25 20:05:05.712 SEVERE: java.user = null
    2009-04-25 20:05:05.712 SEVERE: user.language = en
    2009-04-25 20:05:05.712 SEVERE: user.country = US
    2009-04-25 20:05:05.712 SEVERE: scm.server.version = 11.0.4014.26
    2009-04-25 20:05:05.712 SEVERE: Unknown Exception
    org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect)
    at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:855)
    at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:215)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:206)
    at com.sygate.scm.server.servlet.StartupServlet.testConnection(StartupServlet.java:293)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:81)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:371)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:134)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
    at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:557)
    at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:861)
    at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3967)
    at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3912)
    at com.sybase.jdbc2.tds.Tds.login(Tds.java:440)
    at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:254)
    at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:230)
    at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:200)
    at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:134)
    at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
    at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37)
    at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
    at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877)
    at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851)





    I have read through countless posts on this forum.   I have checked for port conflicts, IIS issues and I have run through the database settings.  I have tried to repair and re-install the application but neither can be done because the exisiting database cannot be communicated with.

    Please help.


  • 2.  RE: Embedded Database not running

    Posted Apr 26, 2009 11:42 AM
     


  • 3.  RE: Embedded Database not running

    Posted Apr 26, 2009 02:26 PM
    Usually this symptom means that the database is damaged... you can restore a backup copy of the database or reinstall the whole product if you don't have it.


  • 4.  RE: Embedded Database not running

    Posted Apr 26, 2009 02:58 PM
    Are there any articles on restoring the database? I haven't used the sepm database backup utility in several weeks so I assume I will have to restore it from tape.


  • 5.  RE: Embedded Database not running

    Posted Apr 27, 2009 06:53 AM
    You have two possible options:
    you can run the backup and restore tool in your start menu for a soft restoring of the product or run the Disaster Recovery procedure to reinstall the whole Manager, restoring the database and don't lose the connectivity with the clients (see the appendix of the installation_guide.pdf in CD1).


  • 6.  RE: Embedded Database not running
    Best Answer

    Posted Apr 27, 2009 10:44 AM
    The Symantec restore tool did not work.  I was able to get the software back up and running by restoring all of the files in the DB directory from my last full backup tape.  Then I went into add/remove programs and repaired the installation.  Everything seems to be working now.

    Dustin