Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Unable to connect to server in SEP

Created: 03 Jul 2013 | 10 comments
irtezaahsan's picture

Dear All,

SEP 12.1 is generating an error (Failed to connect to server). because of this i cant login SEPM. please find below the scm-server-0 logs in which some java exceptions arose.

2013-06-26 11:59:21.533 THREAD 38 SEVERE: 
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.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1181)
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:525)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:422)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:407)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:397)
at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:923)
at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:891)
at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:931)
at com.sygate.scm.server.db.util.DbHelper.getInstance(DbHelper.java:84)
at com.sygate.scm.server.db.util.DbHelper.getInstance(DbHelper.java:78)
at com.sygate.scm.server.task.AgentLogCollector.execute(AgentLogCollector.java:78)
at com.sygate.scm.server.task.MonitoredTimerTask.run(MonitoredTimerTask.java:22)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2013-06-26 11:59:21.533 THREAD 38 SEVERE: 
com.sygate.scm.server.metadata.MetadataException: 
at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:925)
at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:891)
at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:931)
at com.sygate.scm.server.db.util.DbHelper.getInstance(DbHelper.java:84)
at com.sygate.scm.server.db.util.DbHelper.getInstance(DbHelper.java:78)
at com.sygate.scm.server.task.AgentLogCollector.execute(AgentLogCollector.java:78)
at com.sygate.scm.server.task.MonitoredTimerTask.run(MonitoredTimerTask.java:22)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
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.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1181)
at org.apache.tomcat.dbcp.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:525)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:422)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:407)
at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:397)
at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:923)
 
I also have attached the snap of error

Regards,

Irteza

 

Operating Systems:

Comments 10 CommentsJump to latest comment

pete_4u2002's picture

does the server has enough space?

is the database service started? if started can you try repair the SEPM and let know if it works/

 

Ambesh_444's picture

Hi,

Pete is right.. You should check your database services. that should be started.

Please check with below steps..

1. Browse to conf.properties by navigating through

%Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties
2. Edit Conf.properties
3. Add scm.db.datasource= jdbc/metadatabase at the last line (There will be a space after the equal sign)
4. Save the file

Execute Management Configuration Wizard.

Once the Management Configuration is complete. Symantec Endpoint Manager services would be started and you should be able to login to SEPM console.

Please go through the below article,

http://www.symantec.com/business/support/index?page=content&id=TECH134782&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D137291690763663F7Bj5YnnT6rDM50223Yp9Te1IjxGzdJnUuf

 

 

 

 

Thank& Regards,

Ambesh

"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

Sumit G's picture

Check the symantec article
Logging on remotely to Symantec Endpoint Protection Manager 12.1 RU2 with an FQDN results in "Failed to connect to the server" and "ErrorCode: 0x80020000"

 

Article:TECH205165  |  Created: 2013-04-16  |  Updated: 2013-06-12  |  Article URL http://www.symantec.com/docs/TECH205165

 

Regards

Sumit G.

Rafeeq's picture

its not able to find the DB

java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Database server not found
 
can you make sure if symatec embedded database service is started.
Sumit G's picture

Check  if the below symantec article help you

Error when logging to Symantec Endpoint Protection Manager: "Failed to connect to server". Unable to start the embedded database service.

 

 

Article:TECH134782  |  Created: 2010-01-07  |  Updated: 2013-05-16  |  Article URL http://www.symantec.com/docs/TECH134782

Check the thread as well

https://www-secure.symantec.com/connect/forums/sepm-failed-connect-server-service-starts-then-stops#comment-8592351

Regards

Sumit G.

AjinBabu's picture

HI, 

Have you checked your DB health status?

Regards

Ajin

GeoGeo's picture

Check that in Data Source ODBC > System DSN > Configure click next and make sure correct autentication is applied (Login ID & Password) once you have tested and confirmed communication try logging into the SEPM.

Please review ideas and vote there could be something useful :)

https://www-secure.symantec.com/connect/security/ideas

 

SameerU's picture

Hi

Can your run repair

Regards

 

irtezaahsan's picture

Hi 

i was running repair but at last when database was configuring in management server windows suddenly disappear and in event logs i have found the error "the java virtual machine has exited with the code of -1".

 

pete_4u2002's picture

the services of sepm is stopped. restart and try login. if the service stops check the scm-server-0.log