Endpoint Protection

 View Only
Expand all | Collapse all

Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

Migration User

Migration UserNov 22, 2010 04:46 PM

Migration User

Migration UserNov 22, 2010 04:48 PM

Migration User

Migration UserNov 23, 2010 01:28 AM

Migration User

Migration UserNov 24, 2010 03:07 PM

  • 1.  Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 04:12 PM

    Hello,

    My SEPM 11.0.5 embedded DB went down, and so did my Windows 2003 Server.

    So I had to do the Disaster Recovery Procedures described by Symantec.

    After Restoring the last database backup to the new fresh installation of SEPM and using the SEPM service configuration manager (as instructed by symantec),

    Whenever I try to login locally to SEPM, I keep getting the error messages "Failed to Connect to Server", and the SEPM service changes its state from Running to Stopped.

    Even at restarting the SEPM service, the same event occurs.

    Now I can`t neither login to SEPM, nor restore the communication between SEPM and SEP clients, and all of my SEP clients became unmanaged.

    SEPM Version = 11.0.5.33

    New Server OS = Windows Server 2008

    Database = Embedded (Backups are 1 GB to 6.5 GB in size -may be that is why it went down ?- )


    Thanks in advance.u



  • 2.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 04:17 PM

    Check in Services if Symantec Endpoint Protection Manager Service is started. If stopped try starting the service and see if you are able to login.

    Below is an article that has the respons why you can get this error message.

    Title: 'Symantec Endpoint Protection Manager service stops with a Java -1 error in the event log'
    Web URL: http://www.symantec.com/business/support/index?page=content&id=TECH102415&locale=en_US



  • 3.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 04:18 PM

    Try running Management server configuration Wizard once..



  • 4.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 04:45 PM

    I had already tried starting the service, but as soon as I attemot to login, I get that error message and the service is stopped again without my intervention.



  • 5.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 04:46 PM

    Already did so, didn`t work out.



  • 6.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 04:48 PM

    Please post the scm-server0.log



  • 7.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 05:05 PM

    I can`t access it remotely from home right now, I will post it tomorrow.



  • 8.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 22, 2010 11:23 PM

    Small clarification.Your new SEPM and old SEPM versions are exactly same ,right?

    Also you imported/copied the certificate files also,then run the management configuration wizard right?



  • 9.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 23, 2010 12:00 AM

    After installtion, what happens if you do not restore the database? Are you able to log in, without restoring datbase?

    Also, you have two backup database files...did you try using both?



  • 10.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 23, 2010 01:07 AM

    Right.

    After I imported the certificate files, I restarted the SEPM service, I only ran the Mgmt Configuration after I restored the backup (the same ordered sequence described by Symantec Disaster Recovery Best Practice).



  • 11.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 23, 2010 01:08 AM

    Yes, if I don`t restore the database, I`m able to login normally, but of course without my previous configuration or Client Communication.

    I`ve tried restoring multiple database backups, and all end up with the same result.



  • 12.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 23, 2010 01:12 AM

    After importing the certificate files did you run the management server configuration wizard?

    If no run it.



  • 13.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 23, 2010 01:28 AM

    I will try it and inform you of the results.



  • 14.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 05:48 AM

    I can`t locate the scm-server0.log log file, could you tell me its default location ?



  • 15.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 09:07 AM

    Here it`s ;

    2010-11-24 12:53:19.880 SEVERE: ================== Server Environment ===================
    2010-11-24 12:53:19.880 SEVERE: os.name = Windows Server 2008
    2010-11-24 12:53:19.880 SEVERE: os.version = 6.0
    2010-11-24 12:53:19.880 SEVERE: os.arch = x86
    2010-11-24 12:53:19.880 SEVERE: java.version = 1.6.0_14
    2010-11-24 12:53:19.880 SEVERE: java.vendor = Sun Microsystems Inc.
    2010-11-24 12:53:19.880 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2010-11-24 12:53:19.895 SEVERE: java.vm.version = 14.0-b16
    2010-11-24 12:53:19.895 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2010-11-24 12:53:19.895 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2010-11-24 12:53:19.895 SEVERE: java.user = null
    2010-11-24 12:53:19.895 SEVERE: user.language = en
    2010-11-24 12:53:19.895 SEVERE: user.country = US
    2010-11-24 12:53:19.895 SEVERE: scm.server.version = 11.0.5002.333
    2010-11-24 12:53:22.688 SEVERE: ================== StartClientTransport ===================
    2010-11-24 12:53:22.922 SEVERE: Schedule is started!
    2010-11-24 12:53:29.926 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:38)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
        at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
        at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:276)
        at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:831)
        at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:804)
        at com.sygate.scm.server.metadata.MetadataManager.getLastestUsnForCollection(MetadataManager.java:167)
        at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1315)
        at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:224)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
    2010-11-24 12:53:29.926 SEVERE: Unexpected server error. in: com.sygate.scm.server.task.PackageTask
    com.sygate.scm.server.metadata.MetadataException:
        at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:833)
        at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:804)
        at com.sygate.scm.server.metadata.MetadataManager.getLastestUsnForCollection(MetadataManager.java:167)
        at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1315)
        at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:224)
        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:38)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
        at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
        at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:276)
        at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:831)
        ... 6 more
    com.sygate.scm.server.util.ServerException: Unexpected server error.
        at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1317)
        at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:224)
        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:833)
        at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:804)
        at com.sygate.scm.server.metadata.MetadataManager.getLastestUsnForCollection(MetadataManager.java:167)
        at com.sygate.scm.server.configmanager.ConfigManager.getLatestUsnForCollection(ConfigManager.java:1315)
        ... 3 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:38)
        at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
        at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
        at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
        at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
        at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:276)
        at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:831)
        ... 6 more
    2010-11-24 12:53:48.475 SEVERE: PackageTask.publishPackages: Could not retrieve physicalFile. So skipping ID: 5FD4C2B2C52AC7CB8591454F941A22F8
    2010-11-24 12:53:48.475 SEVERE: Unexpected server error.
    com.sygate.scm.server.metadata.MetadataException
        at com.sygate.scm.server.metadata.MetadataManager.getFile(MetadataManager.java:475)
        at com.sygate.scm.server.configmanager.ConfigManager.getFile(ConfigManager.java:1323)
        at com.sygate.scm.server.task.PackageTask.publishPackages(PackageTask.java:569)
        at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:286)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.server.util.ServerException: Unexpected server error.
        at com.sygate.scm.server.configmanager.ConfigManager.getFile(ConfigManager.java:1325)
        at com.sygate.scm.server.task.PackageTask.publishPackages(PackageTask.java:569)
        at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:286)
        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.getFile(MetadataManager.java:475)
        at com.sygate.scm.server.configmanager.ConfigManager.getFile(ConfigManager.java:1323)
        ... 4 more
    2010-11-24 12:53:48.475 SEVERE: Failed to create a folder to which to publish the package in: com.sygate.scm.server.task.PackageTask
    com.sygate.scm.server.util.ServerException: Failed to create a folder to which to publish the package
        at com.sygate.scm.server.task.PackageTask.publishPackages(PackageTask.java:654)
        at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:286)
        at java.util.TimerThread.mainLoop(Timer.java:512)
        at java.util.TimerThread.run(Timer.java:462)
    2010-11-24 12:53:58.599 SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.RequestHandler
    com.sygate.scm.server.util.ScmServerError: Can't read local server from database!
        at com.sygate.scm.server.consolemanager.AdminAuthenticator.authenticate(AdminAuthenticator.java:134)
        at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.doLogin(LoginHandler.java:161)
        at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.getCredential(LoginHandler.java:119)
        at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.handleRequest(LoginHandler.java:50)
        at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:114)
        at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:78)
        at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:79)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:638)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:720)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:139)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:198)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2460)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:119)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:157)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
        at java.lang.Thread.run(Thread.java:619)
    2010-11-24 12:53:58.646 SEVERE: Shuting down server ...



  • 16.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 01:03 PM

    At what port was SEPM installed earlier ? 8014 or 80 ?

    Can you check it on the Program files\symantec\symantec endpoint protection\sylink.xml file of any client



  • 17.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 03:07 PM

    It was 8014.



  • 18.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 03:11 PM

    and  you have re-installed it on same port correct?

     

    Also in Symantec endpoint protection manager/db

    Stop Embedded database service and rename rename sem5.log to sem5.logOld



  • 19.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 03:18 PM

    What error do you get when you run the Management server configuration wizard ?

    The log says "Can't read local server from database!"

    So run the wizard and make sure SEPM connects to database.



  • 20.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"
    Best Answer



  • 21.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 04:06 PM

    Yes I reinstalled it on the same port.

    Only the OS was changed from Windwos Server 2003 to 2008, and even if the certificate was corrupted, the stoppage of SEPM service everytime I try to login after any backup restore is weired.

    I did change the name of the sem5.log to sem5.logold.



  • 22.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 04:26 PM

    I get no error from running the Management Server Configuration Wizard, it authenticates normally, and I see the screens of initializing and configuring the database.



  • 23.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 04:47 PM

    I ran it several times, however it only worked when I followed ;

    https://www-secure.symantec.com/connect/articles/failed-connect-server-sessionhas-timed-out

    When I changed the management server name to its IP, I finally got to access the SEPM again.



  • 24.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 04:58 PM

    The first link really helped, Only after changing the Mgmt Server name to its IP everything worked fine.

    One last question ; The Mgmt server name configured in the Mgmt Server Configuration Wizard was similar - even in spelling - to the Mgmt server name, so why was changing it to the IP required ????

     

    Thanks for your help Vikram, Arvind and Vishal.



  • 25.  RE: Unable to Login to SEPM after Previous Database Backup Restore "Failed to Connect to Server"

    Posted Nov 24, 2010 05:05 PM

    Sometimes it does happen..Database is not able to resolve the name to IP to connect during restore.