Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

SEPM 12.1 Cannot log into management console

Migration User

Migration UserJan 21, 2014 11:23 AM

I am unable to log in through the webconsole.

  • 1.  SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:15 AM

    I am having an issue logging into the SEPM management console. When I type in my credentials I receive the error below.

     1-21-2014 10-08-11 AM.png

    I was able to log into the console fine last Thursday. The console was running slow so I rebooted the server and went to log back in and I receive that error. When I check the SEPM service it shows it as started but when I right-click on it the only option available is Start (see image below). I click on Start and the service says its running but I still cannot log into the console.

    1-21-2014 10-05-33 AM.png

    I have also tried doing a repair of the SEPM. I am running SEPM 12.1.4. How can I fix the console so I can log into it? Thank you.

     



  • 2.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:17 AM

    post the scm-server0.log please you can find it under

    sepm\logs folder.



  • 3.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:18 AM

    Turn on advanced debugging and post the log here for review

    How to debug the Symantec Endpoint Protection Manager

    Download and run the SymHelp tool to see what it shows:

    Troubleshooting computer issues with the Symantec Help support tool



  • 4.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:18 AM

    hi,

    Are you able login through webconsole ?

    Failed to connect to the server" error when logging on to the Symantec Endpoint Protection Manager.

    Article:TECH123142 | Created: 2010-01-10 | Updated: 2011-11-22 | Article URL http://www.symantec.com/docs/TECH123142

     



  • 5.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:20 AM

    Here is the scm-server-0.log.

    2014-01-21 10:12:12.929 THREAD 12 SEVERE: ================== Server Environment ===================
    2014-01-21 10:12:12.929 THREAD 12 SEVERE: os.name = Windows Server 2008 R2
    2014-01-21 10:12:12.929 THREAD 12 SEVERE: os.version = 6.1
    2014-01-21 10:12:12.929 THREAD 12 SEVERE: os.arch = x64
    2014-01-21 10:12:12.929 THREAD 12 SEVERE: java.version = 1.7.0_25
    2014-01-21 10:12:12.929 THREAD 12 SEVERE: java.vendor = Oracle Corporation
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: java.vm.version = 23.25-b01
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: java.user = null
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: user.language = en
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: user.country = US
    2014-01-21 10:12:12.945 THREAD 12 SEVERE: scm.server.version = 12.1.4013.4013
    2014-01-21 10:12:16.788 THREAD 12 SEVERE: Database Schema Version = 12.1.4.0, Server Schema Version = 12.1.4.0
    2014-01-21 10:12:18.617 THREAD 12 SEVERE: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:504)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at com.sygate.scm.server.util.logging.ServerSystemLogRecord.doLog(ServerSystemLogRecord.java:167)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:62)
    at java.util.logging.Logger.log(Logger.java:610)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:244)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:225)
    at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:510)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:136)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    2014-01-21 10:12:19.585 THREAD 12 SEVERE: FIPS mode configuration is false
    2014-01-21 10:12:21.132 THREAD 12 SEVERE: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:504)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at com.sygate.scm.server.util.logging.ServerSystemLogRecord.doLog(ServerSystemLogRecord.java:167)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:62)
    at java.util.logging.Logger.log(Logger.java:610)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:244)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:225)
    at com.sygate.scm.server.licensemanager.LicenseManager.logServerStartRecord(LicenseManager.java:1163)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:187)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    2014-01-21 10:12:21.132 THREAD 12 SEVERE: License state = SEPE_PAID
    2014-01-21 10:12:21.148 THREAD 12 SEVERE: License status on SEPM = Good
    2014-01-21 10:12:21.304 THREAD 12 SEVERE: resetAgentOfflineState=true
    2014-01-21 10:12:21.382 THREAD 12 SEVERE: ================== StartClientTransport ===================
    2014-01-21 10:12:21.382 THREAD 12 SEVERE: [12] Initializing Tomcat ClientTransport Key for Secars...
    2014-01-21 10:12:21.429 THREAD 12 SEVERE: startClientTransport>>resetAgentToOfflineState=true
    2014-01-21 10:12:21.429 THREAD 12 SEVERE: startClientTransport>>start set agent offline
    2014-01-21 10:12:23.148 THREAD 12 WARNING: DatabaseUtilities>>executeUpdateByChunk Exception:java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    2014-01-21 10:12:23.163 THREAD 12 SEVERE:  in: com.sygate.scm.server.servlet.StartupServlet
    com.sygate.scm.server.util.ScmServerError: java.sql.SQLException: Invalid state, the Connection object is closed.
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:250)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699)
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createStatement(ConnectionJDBC2.java:2315)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:257)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:216)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:206)
    ... 18 more
    2014-01-21 10:12:23.195 THREAD 12 SEVERE: DomainId: null
    SiteId: 5457734EAC10013901CC64CEF26CF310
    ServerId: 69302A3CAC10013901E9DF9C7E745D62
    SystemEventId: 1281
    EventDesc: Unexpected server error.
    MessageId: 1
    ErrorCode: 268500992
    com.sygate.scm.server.util.ScmServerError: java.sql.SQLException: Invalid state, the Connection object is closed.
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:250)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699)
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createStatement(ConnectionJDBC2.java:2315)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:257)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:216)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:206)
    ... 18 more
    com.sygate.scm.server.util.ServerException: Unexpected server error.
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:399)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:364)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:360)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:356)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    Caused by: com.sygate.scm.server.util.ScmServerError: java.sql.SQLException: Invalid state, the Connection object is closed.
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:250)
    ... 17 more
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699)
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createStatement(ConnectionJDBC2.java:2315)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:257)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:216)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:206)
    ... 18 more
    2014-01-21 10:12:24.742 THREAD 12 SEVERE: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:504)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at com.sygate.scm.server.util.logging.ServerSystemLogRecord.doLog(ServerSystemLogRecord.java:167)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:62)
    at java.util.logging.Logger.log(Logger.java:610)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:401)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:364)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:360)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:356)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
     


  • 6.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:23 AM

    Check the event viewer for any SQL errors, which this logs appears to be pointing towards. Check for error message 824, if it exists, follow this KB

    http://support.microsoft.com/kb/2015756



  • 7.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:23 AM

    I am unable to log in through the webconsole.



  • 8.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:26 AM

    How much disk space available in D drive ?

    see this if help

    http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=89075



  • 9.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:30 AM

    Did you check the event viewer for error msg 824?



  • 10.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:36 AM

    Seems to be a DB related issue, are you able to connect to the DB as per this document

    http://www.symantec.com/business/support/index?page=content&id=TECH95362



  • 11.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:42 AM

    I do not see an event ID 824 in the event viewer. I do see event ID 4096 for the semsrv though. I posted a screenshot below. I start the SEPM service then about a minute later I see this error in the event viewer.

    1-21-2014 10-38-09 AM.png



  • 12.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:44 AM

    see this articles hope help you.

    Event ID 4096 Java -1 error in event viewer, SEPM service will not stay in started state. "Failed to connect to server" message during login to SEPM.

     

    Article:TECH181655 | Created: 2012-02-17 | Updated: 2012-12-17 | Article URL http://www.symantec.com/docs/TECH181655

     



  • 13.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:45 AM

    Follow this latest article:

    Error semsrv Event Id 4096 , Symantec Endpoint Protection Manager service does not start

    Article:TECH194813  |  Created: 2012-08-13  |  Updated: 2013-05-31  |  Article URL http://www.symantec.com/docs/TECH194813

     



  • 14.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:45 AM

    Hello, 

    Have you tried to login SQL using SQL mgmt studio?

    Regards

    Ajin



  • 15.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:48 AM

    I turned on advanced debugging and here are the results of the scm-server-0.log.

    2014-01-21 10:45:20.563 THREAD 12 SEVERE: ================== Server Environment ===================
    2014-01-21 10:45:20.563 THREAD 12 SEVERE: os.name = Windows Server 2008 R2
    2014-01-21 10:45:20.563 THREAD 12 SEVERE: os.version = 6.1
    2014-01-21 10:45:20.563 THREAD 12 SEVERE: os.arch = x64
    2014-01-21 10:45:20.563 THREAD 12 SEVERE: java.version = 1.7.0_25
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: java.vendor = Oracle Corporation
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: java.vm.version = 23.25-b01
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: java.user = null
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: user.language = en
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: user.country = US
    2014-01-21 10:45:20.579 THREAD 12 SEVERE: scm.server.version = 12.1.4013.4013
    2014-01-21 10:45:23.079 THREAD 12 INFO: Server startup
    2014-01-21 10:45:23.454 THREAD 12 SEVERE: Database Schema Version = 12.1.4.0, Server Schema Version = 12.1.4.0
    2014-01-21 10:45:23.626 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.642 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.642 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.657 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.657 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.657 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.657 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.673 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.673 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.688 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.688 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.688 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.688 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.704 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.704 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.704 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.704 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.720 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.720 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.735 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.735 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.735 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.735 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.751 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.751 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.751 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.751 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.767 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.767 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.767 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.767 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.782 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.782 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.798 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.798 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.798 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.798 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.798 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.813 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.813 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.813 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.829 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.829 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.829 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.829 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.845 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.845 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.845 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.845 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.845 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.845 THREAD 12 FINE: updProcessState: checking...
    2014-01-21 10:45:23.860 THREAD 12 FINE: updProcessState: The process status has been checked.
    2014-01-21 10:45:23.860 THREAD 12 INFO: DomainId: null
    SiteId: 5457734EAC10013901CC64CEF26CF310
    ServerId: 69302A3CAC10013901E9DF9C7E745D62
    SystemEventId: 257
    EventDesc: null
    MessageId: -1
    ErrorCode: -1
    2014-01-21 10:45:25.392 THREAD 12 SEVERE: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:504)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at com.sygate.scm.server.util.logging.ServerSystemLogRecord.doLog(ServerSystemLogRecord.java:167)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:62)
    at java.util.logging.Logger.log(Logger.java:610)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:244)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:225)
    at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:510)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:136)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    2014-01-21 10:45:25.438 THREAD 12 INFO: License state check started
    2014-01-21 10:45:25.704 THREAD 12 FINE: LicenseManager.checkLicenseState(). Initial state = SEPE_PAID
    2014-01-21 10:45:25.704 THREAD 12 INFO: LicenseManager.checkLicenseState(). License changed or license state = UNKNOWN. Starting detailed license status check
    2014-01-21 10:45:25.704 THREAD 12 FINE: LicenseManager.checkLicenseState(). Current state aftr recomputation= SEPE_PAID
    2014-01-21 10:45:25.704 THREAD 12 FINE: CheckCross grade, product type from license state = SEPE
    2014-01-21 10:45:25.735 THREAD 12 FINE: License Expiration = false
    2014-01-21 10:45:25.735 THREAD 12 FINE: LicenseManager.checkLicenseState(). License check sum in the beginning of routine = 90DF06C88D3756782C931EF5A658565B
    2014-01-21 10:45:25.751 THREAD 12 FINE: LicenseManager.checkLicenseState(). License check sum now = 90DF06C88D3756782C931EF5A658565B
    2014-01-21 10:45:25.751 THREAD 12 FINE: LicenseManager.checkLicenseState(). Server did not change license object, no need to save
    2014-01-21 10:45:25.751 THREAD 12 FINER: EEHelper created
    2014-01-21 10:45:25.751 THREAD 12 INFO: EE License Helper Initialized
    2014-01-21 10:45:25.751 THREAD 12 FINE: LicenseManager.checkLicenseState(). License helpers initialized
    2014-01-21 10:45:25.751 THREAD 12 FINE: Updating renewal URLs
    2014-01-21 10:45:25.845 THREAD 12 FINER: Updating generic purchase URL for OD license
    2014-01-21 10:45:25.845 THREAD 12 FINE: Finished updating renewal URLs
    2014-01-21 10:45:25.845 THREAD 12 FINE: LicenseManager.checkLicenseState(). no changes to renewal urls
    2014-01-21 10:45:25.845 THREAD 12 INFO: EELicenseHelper.checkSeatsMapping(). Enterprise assignment algorithm started
    2014-01-21 10:45:25.845 THREAD 12 INFO: EELicenseHelper.checkSeatsMapping(). Enterprise assignment algorithm completed
    2014-01-21 10:45:25.845 THREAD 12 FINE: LicenseManager.checkLicenseState(). license algorithm executed
    2014-01-21 10:45:25.845 THREAD 12 FINEST: computer checksum for sep.slf
    2014-01-21 10:45:25.845 THREAD 12 FINE: LicenseManager.checkLicenseState(). License checksums computed
    2014-01-21 10:45:25.845 THREAD 12 FINE: Deleting marked as deleted license files from disk
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.860 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.876 THREAD 12 FINE: # of files after deletion = 12
    2014-01-21 10:45:25.876 THREAD 12 FINE: Refreshing license files on disk
    2014-01-21 10:45:25.876 THREAD 12 FINEST: Writing overdeployment license
    2014-01-21 10:45:25.876 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.876 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\31FEB424EE043C427826ED681F63DE6E.slf
    2014-01-21 10:45:25.876 THREAD 12 FINEST: No trialware license object exists.
    2014-01-21 10:45:25.876 THREAD 12 FINEST: Writing license chains.
    2014-01-21 10:45:25.876 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.876 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\CD8299510512EFDA531DAB5E2446139B.slf
    2014-01-21 10:45:25.876 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.876 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\7B38A4AF2D0F03CC6AA73410D64D3F85.slf
    2014-01-21 10:45:25.876 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.876 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\BEBA2795354BA5F8D6AE92899CB76796.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\AB21C6FE1F7A1CFF288E43C3B2E35C42.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\EE202B02A27DB13DBEA17CD2947B3F86.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\9BEA5C97F0B99BBF2758ECA73D2F16C2.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\76ABF5CB31AA632EB51A775FF7D7A3ED.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\C7EC95A79D4D1009003E5D8BE1A1D625.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\C2EE547635844A3E31CCCBC89F3F165B.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\697E0F2799AC774183A8A03B8798244A.slf
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Serialized all valid SEP licenses into sep.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: Writing license to file: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license\sep.slf
    2014-01-21 10:45:25.892 THREAD 12 FINER: Fail to create the license output directory: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Inetpub\license
    2014-01-21 10:45:25.892 THREAD 12 FINEST: remove serialized SNAC liense file snac.slf
    2014-01-21 10:45:25.892 THREAD 12 FINEST: computer checksum for sep.slf
    2014-01-21 10:45:25.892 THREAD 12 FINE: Finished refreshing license files
    2014-01-21 10:45:25.892 THREAD 12 FINE: LicenseManager.checkLicenseState(). License files caches on disk
    2014-01-21 10:45:25.907 THREAD 12 INFO: License state check completed. Exiting
    2014-01-21 10:45:26.032 THREAD 12 SEVERE: FIPS mode configuration is false
    2014-01-21 10:45:26.048 THREAD 12 INFO: DomainId: null
    SiteId: 5457734EAC10013901CC64CEF26CF310
    ServerId: 69302A3CAC10013901E9DF9C7E745D62
    SystemEventId: 4877
    EventDesc: Symantec Endpoint Protection Manager server started with paid license.
    MessageId: -1
    ErrorCode: -1
    2014-01-21 10:45:27.579 THREAD 12 SEVERE: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:504)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at com.sygate.scm.server.util.logging.ServerSystemLogRecord.doLog(ServerSystemLogRecord.java:167)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:62)
    at java.util.logging.Logger.log(Logger.java:610)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:244)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:225)
    at com.sygate.scm.server.licensemanager.LicenseManager.logServerStartRecord(LicenseManager.java:1163)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:187)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    2014-01-21 10:45:27.579 THREAD 12 SEVERE: License state = SEPE_PAID
    2014-01-21 10:45:27.579 THREAD 12 SEVERE: License status on SEPM = Good
    2014-01-21 10:45:27.610 THREAD 12 FINE: reset agent grace status query =UPDATE SEM_AGENT SET IS_GRACE=0, TIME_STAMP=?, USN=? WHERE IS_GRACE=1 and DELETED =0 
    2014-01-21 10:45:27.673 THREAD 12 SEVERE: resetAgentOfflineState=true
    2014-01-21 10:45:27.720 THREAD 12 INFO: use transport url:http://localhost:8014/secars/secars.dll
    2014-01-21 10:45:27.720 THREAD 12 SEVERE: ================== StartClientTransport ===================
    2014-01-21 10:45:27.720 THREAD 12 SEVERE: [12] Initializing Tomcat ClientTransport Key for Secars...
    2014-01-21 10:45:27.720 THREAD 12 FINE: Tomcat ClientTransport Key generated
    2014-01-21 10:45:27.720 THREAD 12 SEVERE: startClientTransport>>resetAgentToOfflineState=true
    2014-01-21 10:45:27.720 THREAD 12 SEVERE: startClientTransport>>start set agent offline
    2014-01-21 10:45:29.423 THREAD 12 WARNING: DatabaseUtilities>>executeUpdateByChunk Exception:java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    2014-01-21 10:45:29.423 THREAD 12 SEVERE:  in: com.sygate.scm.server.servlet.StartupServlet
    com.sygate.scm.server.util.ScmServerError: java.sql.SQLException: Invalid state, the Connection object is closed.
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:250)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699)
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createStatement(ConnectionJDBC2.java:2315)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:257)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:216)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:206)
    ... 18 more
    2014-01-21 10:45:29.454 THREAD 12 SEVERE: DomainId: null
    SiteId: 5457734EAC10013901CC64CEF26CF310
    ServerId: 69302A3CAC10013901E9DF9C7E745D62
    SystemEventId: 1281
    EventDesc: Unexpected server error.
    MessageId: 1
    ErrorCode: 268500992
    com.sygate.scm.server.util.ScmServerError: java.sql.SQLException: Invalid state, the Connection object is closed.
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:250)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699)
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createStatement(ConnectionJDBC2.java:2315)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:257)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:216)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:206)
    ... 18 more
    com.sygate.scm.server.util.ServerException: Unexpected server error.
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:399)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:364)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:360)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:356)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    Caused by: com.sygate.scm.server.util.ScmServerError: java.sql.SQLException: Invalid state, the Connection object is closed.
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:234)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:250)
    ... 17 more
    Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1699)
    at net.sourceforge.jtds.jdbc.ConnectionJDBC2.createStatement(ConnectionJDBC2.java:2315)
    at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:257)
    at org.apache.tomcat.dbcp.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.createStatement(PoolingDataSource.java:216)
    at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:206)
    ... 18 more
    2014-01-21 10:45:30.985 THREAD 12 SEVERE: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    java.sql.SQLException: The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000114720000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL.3\MSSQL\DATA\EndpointProtection121_index.ndf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:504)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at com.sygate.scm.server.util.logging.ServerSystemLogRecord.doLog(ServerSystemLogRecord.java:167)
    at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:62)
    at java.util.logging.Logger.log(Logger.java:610)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:401)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:364)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:360)
    at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:356)
    at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:314)
    at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5027)
    at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
    at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
    at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
    at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)
    at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1637)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
    at java.util.concurrent.FutureTask.run(FutureTask.java:166)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:724)
    2014-01-21 10:45:31.063 THREAD 12 INFO: StartupServlet.updateOffLineServerState(): Server is offline now, ID=69302A3CAC10013901E9DF9C7E745D62
     


  • 16.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 11:51 AM

    Try the steps here:

    http://www.symantec.com/docs/TECH194813



  • 17.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 01:08 PM

    I increased the memory useage for Java Virtual Machine used by semsrv and this did not fix the issue. The service is still stopping when I start it.



  • 18.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 01:21 PM

    Did you check the odbc connection as I mentioned earlier? was there any change on your sql server.

    Does it complete if you run the management server configuration wizard?



  • 19.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 01:31 PM

    When I check the System DSN tab in the ODBC Data Source Admin I do not see a SymantecEndpointSecurityDSN. 



  • 20.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 01:44 PM

     

     

    To verify ODBC connection to the SQL database:

    1. Click Start button and select Run.
      • If the Operating System is 32 bit, enter "%systemroot%\system32\odbcad32.exe"
      • If the Operating System is 64 bit, enter "%systemroot%\syswow64\odbcad32.exe"
    2. In the ODBC Data Source Administrator dialog box, click System DSN.
    3. On the System DSN tab, double-click SymantecEndpointSecurityDSN.
    4. In the Server drop-down list, verify that the correct server and instance is selected.
    5. Click Next.
    6. For Login ID, type sa.
    7. In the Password text box, type the password for the database.
    8. This password is the one that you entered for the database when you installed the management server. 
    9. Click Next and make sure that sem5 is selected for the default database.
    10. Click Next.
    11. Click Finish.
    12. Click "Test Data Source" and look for the result that states: TESTS COMPLETED SUCCESSFULLY!

    since you are on 64 bit it should be in the syswow64 directory

    http://www.symantec.com/business/support/index?page=content&id=TECH103990&locale=en_US

     



  • 21.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 02:16 PM

    I opened the ODBC Data Source Administrator and clicked on the System DSN tab and I do not have SymantecEndpointSecurityDSN listed. 

    I ran the Management Server Configuration Wizard again and I am able to finally log into the mangement console. I do notice when I log into it it takes a while for it to load. Is there a way to make the console load faster?



  • 22.  RE: SEPM 12.1 Cannot log into management console

    Posted Jan 21, 2014 02:22 PM

    Nice ! 

    These should help, Hope you have increased the heap size

    Tuning the Performance of the Symantec Endpoint Protection Manager console

     

    http://www.symantec.com/business/support/index?page=content&id=TECH105179