Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

FAILED TO CONNECT TO SERVER.

Migration User

Migration UserAug 14, 2012 04:41 PM

Try by manually starting SEPM services..
Migration User

Migration UserAug 14, 2012 05:17 PM

Plese attach scm.server.0.log
NRaj

NRajAug 15, 2012 08:39 AM

Check the disk space on the DB.
Migration User

Migration UserAug 15, 2012 09:17 AM

Yes, usually the transaction log is full :-)

  • 1.  FAILED TO CONNECT TO SERVER.

    Posted Aug 14, 2012 03:11 PM

    I connected to my SEPM fine about 3 days ago. Came back from the weekend, and Monday I am unable to connect to SEPM.

    Error message: Failed to connect to databse.  Make sure the server is running and your session has not timed out. I fyou can reach the server, but cannot log in, make sure that your have provided the correct parameters. If you are experiencing network issues, please contact your network administrator.

    I am running this SEPM on a Server 2008 64-Bit platform.

    I have run the DBvalidator and this is the log:

     

    2012-08-14 13:25:08.876 THREAD 1 INFO: logger initialized ...
    2012-08-14 13:25:08.876 THREAD 1 INFO: SEPM Server Home:[D:\Program File\Tools\..\tomcat]
    2012-08-14 13:26:17.953 THREAD 1 INFO: Initialized the database.
    2012-08-14 13:27:17.701 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]Database server 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]Database server 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
     

     

    Please help. DEsperate right now, as none of my clients are connecting to the database server my network is vulnerable.  The client are showing:

    Status - Not connected

    Error- Unable to connect to server.



  • 2.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 14, 2012 04:41 PM

    Try by manually starting SEPM services..



  • 3.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 14, 2012 05:09 PM

    I've tried manually starting the SEPM Services, but still same problem.

    Anything else I can try???

     



  • 4.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 14, 2012 05:17 PM

    Plese attach scm.server.0.log



  • 5.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 04:10 AM

    so can anyone in the client / workstation use SSMS to connect to the database server ?



  • 6.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 08:39 AM

    Check the disk space on the DB.



  • 7.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 09:17 AM

    Yes, usually the transaction log is full :-)



  • 8.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 09:36 AM

    There is over 31 GB of space left of installtion drive.

    No one can connect to the database server. 

    This is the smc.server.o log.

     


    2012-08-14 16:07:09.113 THREAD 1 SEVERE: ================== Server Environment ===================
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: os.name = Windows Server 2008
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: os.version = 6.0
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: os.arch = x86
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: java.version = 1.6.0_24
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: java.vm.version = 19.1-b02
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: java.home = D:\Program File\jre
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: catalina.home = D:\Program File\tomcat
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: java.user = null
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: user.language = en
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: user.country = US
    2012-08-14 16:07:09.113 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
    2012-08-14 16:08:09.938 THREAD 1 SEVERE: 
    org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory ([Sybase][ODBC Driver][SQL Anywhere]Database server not found)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
    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.getDBConnection(DatabaseUtilities.java:2561)
    at com.sygate.scm.server.db.util.DatabaseUtilities.testConnection(DatabaseUtilities.java:2518)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:128)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
    at org.apache.catalina.core.StandardService.start(StandardService.java:525)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
    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:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
    Caused by: java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Database server not found
    at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
    at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
    at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
    at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)
    at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)
    ... 35 more
    2012-08-14 16:08:09.938 THREAD 1 SEVERE:  in: com.sygate.scm.server.servlet.StartupServlet
    com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:129)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
    at org.apache.catalina.core.StandardService.start(StandardService.java:525)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
    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:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
    2012-08-14 16:08:09.969 THREAD 1 SEVERE: DomainId: null
    SiteId: null
    ServerId: 2A2F14EAC86464C10071145B4B72A5DB
    SystemEventId: 1281
    EventDesc: Unexpected server error.
    MessageId: 1
    ErrorCode: 268500992
    com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:129)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
    at org.apache.catalina.core.StandardService.start(StandardService.java:525)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
    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:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
    com.sygate.scm.server.util.ServerException: Unexpected server error.
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:359)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:333)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:261)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
    at org.apache.catalina.core.StandardService.start(StandardService.java:525)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
    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:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
    Caused by: com.sygate.scm.server.util.ScmServerError: Failed to connect to database after tried 20 times, please start the database!
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:129)
    ... 26 more
    2012-08-14 16:08:13.011 THREAD 1 SEVERE: SEM: Connect to database failed
    java.sql.SQLException: SEM: Connect to database failed
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:466)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:58)
    at java.util.logging.Logger.log(Logger.java:481)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:361)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:333)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:261)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
    at org.apache.catalina.core.StandardService.start(StandardService.java:525)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
    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:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
    Caused by: java.lang.NullPointerException
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:421)
    ... 31 more
     


  • 9.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 09:49 AM

    Please repair the SEPM and run Management Server Wizard Console

    Regards

     



  • 10.  RE: FAILED TO CONNECT TO SERVER.

    Broadcom Employee
    Posted Aug 15, 2012 10:21 AM

    Hi,

    Click Start, Administrative Tools, ODBC. [Note : For 64 bit OS (by default) C:\Windows\SysWoW64\Odbcad32.exe]

    1. Click on System DSN
    2. Select SymantecEndpointProtectionDSN and click on Configure
    3. Under ODBC tab, click Test Connection [It would give an error : Connection failed,Integrated login...]
    4. Click on Login Tab
    5. Enter the credentials [User name : dba and the Password]
    6. Click on Database tab
    7. Enter the Database name as sem5
    8. Click ODBC tab and Test Connection - Should show Connection Successful.
    9. Start the Symantec Endpoint Protection Manager service and login to the manager console.

    Step 2:


    1. Stop all Services for Symantec
    2. Rebooted machine
    3. Restart service & check .


  • 11.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 11:42 AM

    Same error - Cannot connet to database.

    Windows application logs on the Server are giving this error:

     

     

    SQLANYs_sem5
          *** ERROR *** Assertion failed: 200114[sem5] (11.0.1.2472) Can't find values for row 1c1:6 in index 'I_SEM_AGENT_COMPUTER_ID_PLUS'

     



  • 12.  RE: FAILED TO CONNECT TO SERVER.

    Broadcom Employee
    Posted Aug 15, 2012 11:50 AM

    Hi,

    The following steps have been shown to resolve this issue. Note that these steps assume the default installation directories for the SEPM:

    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).

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



  • 13.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 15, 2012 12:49 PM

    Tried the dbsrv11. Same error. Tried running it from the installation Drive. See this log from the SQL ANywhere:

     

     

    SQL Anywhere Network Server Version 11.0.1.2472
     
    OEM Authenticated Edition, licensed only for use with authenticated OEM applications.
     
     
    Copyright © 2001-2009, iAnywhere Solutions, Inc.
    Portions copyright © 1988-2009, Sybase, Inc. All rights reserved.
    Use of this software is governed by the Sybase License Agreement. Refer to http://www.sybase.com/softwarelicenses
     
     
    4 logical processor(s) on 1 physical processor(s) detected.
    Processor limit (licensed processors): 16
    Maximum number of physical processors the server will use: 1
    This server is licensed to:
        Symantec
        Symantec
    Running Windows 2008 Build 6001 Service Pack 1 on X86_64
    Server built for X86 processor architecture
    2048K of memory used for caching
    Minimum cache size: 2048K, maximum cache size: 3579584K
    Using a maximum page size of 8192 bytes
    Starting database "sem5" (D:\Program File\ASA\win32\sem5.db) at Wed Aug 15 2012 12:32
    Performance warning: Database file "D:\Program File\ASA\win32\sem5.db" consists of 49 disk fragments
    Transaction log: sem5.log
    Starting checkpoint of "sem5" (sem5.db) at Wed Aug 15 2012 12:32
    Finished checkpoint of "sem5" (sem5.db) at Wed Aug 15 2012 12:32
    Database "sem5" (sem5.db) started at Wed Aug 15 2012 12:32
    This database is licensed for use with:
        Application: Symantec Endpoint Protection Manager
        Company: Symantec Corp
    Database server started at Wed Aug 15 2012 12:32
    Trying to start SharedMemory link ...
        SharedMemory link started successfully
    Trying to start TCPIP link ...
    Starting on port 2638
    Cache size adjusted to 3248K
        TCPIP link started successfully
    Now accepting requests


  • 14.  RE: FAILED TO CONNECT TO SERVER.
    Best Answer

    Posted Aug 16, 2012 05:04 AM

    Database server not found

     

    Your SEPM is unable to connect to the database. Try running a repair on SEPM, if still no success

    Please perform DR:-

     

     

    Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

     
     

    How to perform Disaster Recovery without Database backup/Restore



  • 15.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 16, 2012 09:12 AM

    DataBase Backup and Restore doesn't work as the connection to the DATABASE failed.

    I have tried the SEPM repair, but still same error.

    My worry is that the uninstall and reinstall rarely works.  Them I may have to rebuild my server which I do not want to do. 

     

     



  • 16.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 16, 2012 03:59 PM

    DataBase Backup and Restore doesn't work as the connection to the DATABASE failed.

    I have tried the SEPM repair, but still same error.

    My worry is that the uninstall and reinstall rarely works.  Them I may have to rebuild my server which I do not want to do. 

     

     



  • 17.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 17, 2012 03:02 AM

    What version of SEPm are you using? If it's 12 then you would get the clients back on the SEPM.

    But Yes, you would loose the database and the policies that the old SEPM had.

     



  • 18.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 17, 2012 03:52 AM

    Have you checked the user that you are using to access the database?

    Sometimes this can relate when user has expired permissions, that he dont even see the database.

    In case you could simply verify creating for a test a new user with appropriate permissions in the database and change the ODBC settings again or run the management configuration wizzard again, but take care you have a backup of at least your server keys.

    cheers, toby



  • 19.  RE: FAILED TO CONNECT TO SERVER.

    Broadcom Employee
    Posted Aug 17, 2012 06:59 AM

    Hi,

    You should try this article.

    How to perform Disaster Recovery without Database backup/Restore
     


  • 20.  RE: FAILED TO CONNECT TO SERVER.

    Posted Aug 17, 2012 10:01 AM

    The process described by Homer Simpson.

    Only different is you must add the domain ID saved in the backup.txt as described in the Disaster Recovery 

    link.

    Then the SEPM recognized all the endpoints which were already connected to the manager.

    The unfortunate thing is that all policy that were edited or added now have to be re-entered.

    The SEPM however, is not sending emails notifications. Also the link to Latest Security Updates does not work either.  It comes up with an about blank page (browser used is IE9).

    Anyone with a solution to the this one?

     

    Thanks again homer Simpson and everyone else who post comments.

     

    TJ



  • 21.  RE: FAILED TO CONNECT TO SERVER.

    Broadcom Employee
    Posted Aug 17, 2012 10:13 AM

    Hi,

    Actually we can export and import policies however you could not login to the SEPM so it wasn't possible.

    Could you please mention about which link you are talking about?



  • 22.  RE: FAILED TO CONNECT TO SERVER.