Help - The Symantec Protection Center database has gone down
Hi,
SEP small business edition V 12.0
Received this email yesterday.
I checked scm-server-0.log which was full of errors, here is a snippet:
Everything seems ok in Symantec protection center, the clients get updates ok. Not sure why this is happening.
2013-02-19 12:40:32.705 SEVERE: Unexpected server error.
com.sygate.scm.server.metadata.MetadataException:
at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:705)
at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:676)
at com.sygate.scm.server.metadata.MetadataManager.getLastestUsnForCollection(MetadataManager.java:167)
at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1173)
at com.sygate.scm.server.task.SyncLuConfigTask.syncLuConfig(SyncLuConfigTask.java:55)
at com.sygate.scm.server.task.SyncLuConfigTask.run(SyncLuConfigTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
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.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
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.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:703)
... 7 more
com.sygate.scm.server.util.ServerException: Unexpected server error.
at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1175)
at com.sygate.scm.server.task.SyncLuConfigTask.syncLuConfig(SyncLuConfigTask.java:55)
at com.sygate.scm.server.task.SyncLuConfigTask.run(SyncLuConfigTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: com.sygate.scm.server.metadata.MetadataException:
at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:705)
at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:676)
at com.sygate.scm.server.metadata.MetadataManager.getLastestUsnForCollection(MetadataManager.java:167)
at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1173)
... 4 more
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.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
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.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:703)
... 7 more
2013-02-19 12:40:33.719 SEVERE: Unknown Exception
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.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
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.db.util.DatabaseUtilities.getLatestUSN(DatabaseUtilities.java:485)
at com.sygate.scm.server.task.IISCacheTask.run(IISCacheTask.java:122)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2013-02-19 12:40:33.719 SEVERE: Unknown Exception in: com.sygate.scm.server.task.IISCacheTask
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.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:95)
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.db.util.DatabaseUtilities.getLatestUSN(DatabaseUtilities.java:485)
at com.sygate.scm.server.task.IISCacheTask.run(IISCacheTask.java:122)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Comments 4 Comments • Jump to latest comment
Also, not sure if it is related but WSUS is having a problem connecting to the SQL database.
Any help would be appreciated,
Thanks,
Did you try restarting the SEPM service?
SEP Knowledge Base
Endpoint SWAT
Yes I did which I believe resulted in another email stating that the database has gone down.
I can't recall the event log items at the moment, but will post more when I am back into that server.
Hello,
Upon checking the Logs, we see the below errors:
... 7 more
com.sygate.scm.server.util.ServerException: Unexpected server error.
at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1175)
at com.sygate.scm.server.task.SyncLuConfigTask.syncLuConfig(SyncLuConfigTask.java:55)
at com.sygate.scm.server.task.SyncLuConfigTask.run(SyncLuConfigTask.java:33)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
....
...........
com.sygate.scm.server.metadata.MetadataManager.getLastestUsnForCollection(MetadataManager.java:167)
at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1173)
... 4 more
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:557)
Suggestions:
1) Make sure the embedded database service is running. If that service isn't running then you'll get Failed to Connect to Server.
If it is running, you should be able to do a netstat -anbo, and see that dbsrv9.exe is listening on a TCP port.
2) Restart the server machine and try logging in..
3) Check the Application Logs in the Event Viewer from the Logs and work on the Solution step provided in the Thread by Sandra below:
https://www-secure.symantec.com/connect/forums/sep-management-console-and-services-not-working
4) Try the Disaster Recovery steps -
About preparing for disaster recovery
http://www.symantec.com/docs/HOWTO16243
Managing disaster recovery.
http://www.symantec.com/docs/HOWTO16244
If that does not resolve, Check these Threads below with Similar Issue:
https://www-secure.symantec.com/connect/pt-br/forums/failed-connect-server-13
https://www-secure.symantec.com/connect/forums/embedded-database-not-running
https://www-secure.symantec.com/connect/forums/server-port-you-chose-not-used-database-server
Hope that helps!!
Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | MCTS | STS | ITIL v3
Twitter: @mithun_sanghavi
Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<&a
Would you like to reply?
Login or Register to post your comment.