Endpoint Protection

 View Only

  • 1.  SEPM service keeps stopping

    Posted Feb 11, 2010 05:46 AM
     My SEPM service keeps stopping. I need to check the embedded database, but I can not find the dbvalidator.bat tool in the tools folder. Can anyone tell me from where I can download it.


  • 2.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 05:50 AM
    pls paste the scm-server-0.log with is present in Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\logs 


  • 3.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 05:50 AM
    pls helps paste the scm-server-0.log with is present in Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\logs 


  • 4.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 06:01 AM
     Here it is:

    2010-02-11 11:28:53.218 SEVERE: ================== Server Environment ===================
    2010-02-11 11:28:53.218 SEVERE: os.name = Windows 2003
    2010-02-11 11:28:53.218 SEVERE: os.version = 5.2
    2010-02-11 11:28:53.218 SEVERE: os.arch = x86
    2010-02-11 11:28:53.218 SEVERE: java.version = 1.5.0_14
    2010-02-11 11:28:53.218 SEVERE: java.vendor = Sun Microsystems Inc.
    2010-02-11 11:28:53.218 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2010-02-11 11:28:53.218 SEVERE: java.vm.version = 1.5.0_14-b03
    2010-02-11 11:28:53.218 SEVERE: java.home = D:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2010-02-11 11:28:53.218 SEVERE: catalina.home = D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2010-02-11 11:28:53.218 SEVERE: java.user = null
    2010-02-11 11:28:53.218 SEVERE: user.language = en
    2010-02-11 11:28:53.218 SEVERE: user.country = US
    2010-02-11 11:28:53.218 SEVERE: scm.server.version = 11.0.1000.1375
    2010-02-11 11:28:53.296 INFO: Server startup
    2010-02-11 11:28:56.437 SEVERE: Unknown Exception
    com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -189: Unable to find in index 'I_SYSTEM_STATE_USN' for table 'SYSTEM_STATE'
    at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:2538)
    at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:1922)
    at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
    at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:201)
    at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:182)
    at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1611)
    at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1594)
    at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:89)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
    at com.sygate.scm.server.metadata.StateMetadataCollection.updateMetadata(StateMetadataCollection.java:102)
    at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:303)
    at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:668)
    at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:2406)
    at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:78)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:888)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:776)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3363)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3586)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:707)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
    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:156)
    2010-02-11 11:28:56.500 SEVERE: Unexpected server error. in: com.sygate.scm.server.servlet.StartupServlet
    com.sygate.scm.server.metadata.MetadataException: ASA Error -189: Unable to find in index 'I_SYSTEM_STATE_USN' for table 'SYSTEM_STATE'
    at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:306)
    at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:668)
    at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:2406)
    at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:78)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:888)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:776)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3363)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3586)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:707)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
    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:156)
    Caused by: com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -189: Unable to find in index 'I_SYSTEM_STATE_USN' for table 'SYSTEM_STATE'
    at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:2538)
    at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:1922)
    at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
    at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:201)
    at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:182)
    at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1611)
    at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1594)
    at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:89)
    at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
    at com.sygate.scm.server.metadata.StateMetadataCollection.updateMetadata(StateMetadataCollection.java:102)
    at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:303)
    ... 22 more
    com.sygate.scm.server.util.ServerException: Unexpected server error.
    at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:670)
    at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:2406)
    at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:78)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:888)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:776)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3363)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:3586)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:707)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1141)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:316)
    at org.apache.catalina.core.StandardService.start(StandardService.java:450)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:2143)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:463)
    at org.apache.catalina.startup.Catalina.execute(Catalina.java:350)
    at org.apache.catalina.startup.Catalina.process(Catalina.java:129)
    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:156)
     


  • 5.  RE: SEPM service keeps stopping

    Broadcom Employee
    Posted Feb 11, 2010 06:11 AM

    i believe the database is corrupted, do you have the backup? if ys try restoring else may need to build new SEPM.

     

    contact support may be they will help in repairing the DB.
     



  • 6.  RE: SEPM service keeps stopping

    Broadcom Employee
    Posted Feb 11, 2010 06:12 AM
    said becuase of reading this entry

    "
    Caused by: com.sybase.jdbc2.jdbc.SybSQLException: ASA Error -189: Unable to find in index 'I_SYSTEM_STATE_USN' for table 'SYSTEM_STATE'"


  • 7.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 06:14 AM
    I think it is better to upgrade to RU5 (11.0.5). Refer below doc

    Migrating to Symantec Endpoint Protection 11.0 RU5



  • 8.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 06:17 AM

    Check for hidden files as well

    If an issue is suspected with the Symantec Endpoint Protection Manager database, the "Database Validation" tool can be used to assist in diagnosing the problem.

    The batch file, "dbvalidator.bat", is located by default in the following location:
    C:\Program Files\Symantec\SymantecEndpoint Protection Manager\Tools.

    This tool creates a log file with the following name:
    "dbvalidator.log", which is placed in the C:\Program Files\Symantec\SymantecEndpoint Protection Manager\tomcat\logs folder.

    You can run the "dbvalidator.bat" file with or without the Y option.  If you use the Y option, the entire database XML file is inserted into the log file. This XML provides more diagnostic information, but it may contain passwords to the servers and Enforcers in your network. For example, it may contain the passwords to your mail server, LDAP server, or RADIUS server. If you do not want this information to be known outside the environment, you should run the batch file without the Y option.

    To run the Database Validation tool:
    Go to Start> Run.
    Type CMD.
    Click Ok.
    Change directory to your tools installation folder, by typing:
    cd C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools


    Type one of the following commands to run the batch file:
    dbvalidator.bat
    dbvalidator.bat Y

    If you add the Y option, the entire database XML file is also put into the log file, which is by default located here: \Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\dbvalidator.log. This file may contain server and Enforcer passwords.

    One of the following messages is displayed at the command prompt dependent upon whether the database has passed validation or not:
     If the database is valid, you see the following message:
    "Database validation passed."
     If the database is invalid, you see the following message:
    "Database validation failed.  Please check the log file for more details."
     If an error occurs, you see the following message:
    "Some error occurred.  Please check the log file for more details."


  • 9.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 06:59 AM
    I can not find the dbvalidator.bat tool in the C:\Program Files\Symantec\SymantecEndpoint Protection Manager\Tools. Can anyone tell me where I can download it?


  • 10.  RE: SEPM service keeps stopping

    Posted Feb 11, 2010 07:07 AM
    Have a look in CD1\SEPM\Data1 folder in some versions you will get this file there..