Endpoint Protection

 View Only
Expand all | Collapse all

Unable to connect to SEPM after reinstallation

Migration User

Migration UserMar 19, 2013 07:53 AM

Migration User

Migration UserMar 21, 2013 01:26 PM

  • 1.  Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 07:38 AM

    Hi,

    I reinstalled SEMP 11 and now it is not opening. I get error: "Failed to connect to server. Make sure that the server is running and your session has not timed out."

    I checked IIS restrictions and check anonymous logon. Everything seems fine.

    What could be wrong?

    thanks



  • 2.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 07:50 AM

    run the management server configuration wizard once.

    check the port number... whats port for db did you chose?

    post the event viewer message and server-0.log found under sepm\logs folder.



  • 3.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 07:53 AM

    Hi

    Try repairing of SEPM

    Regards

     



  • 4.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 07:59 AM

    Agreed with Rafeeq comments. Please run management server configuration wizard on the server.



  • 5.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 08:18 AM

    I can not find logs folders under:

    C:\Program Files\Symantec\Symantec Endpoint Protection Manager

    I run reconfigure server with 8443 and 9090 ports. I used Embendded database. Reconfiguration finished successfully.

    After reconfiguration same thing. I can open Reporting site:
    http://localhost:8014/reporting/login/login.php

    But it fails on http://localhost:8014/ with error 403 forbidden.

    Cant understand whats wrong



  • 6.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 08:29 AM

    under IIS take out the anonymous user and put in currently logged in admin id and password and check.

    if that does not work give full access to authenticated users to sepm installation folder.

     



  • 7.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 08:43 AM

    same thing.

    we have another server for replication and on that server this site also is not working:
    http://localhost:8014/

    But wahts is wrong that I can not start the current one?

    could it be somethnig wrong with DB? But ports are operating:

    C:\Documents and Settings\user>netstat -an | find "2638"
      TCP    0.0.0.0:2638           0.0.0.0:0              LISTENING
      TCP    127.0.0.1:2712         127.0.0.1:2638         TIME_WAIT



  • 8.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 09:20 AM

    On services.msc I can find only two services:

    Symantec Embedded Database - ASANYs_sem5
    Symantec Endpoint Protection Manager - semsrv (which is stoping after I start it)

    Should it be more services?



  • 9.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 10:20 AM

    you are able to open reproting ? able to log in ? or its just the web page?

    localhost:8443 might be becauase  virtual directories do not have browse permission.

    it will be under tomcat logs, plesae follow these documents.

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



  • 10.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 12:16 PM

    could it be the problem of tomcat, as there is tomcat installed already on the server. But I need to prove that to the client if tomcat can couse this root issue. Tomcat was installed before SEMP reinstallation and SEPM worked.

    I will check logs

    thank you in advance,



  • 11.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 19, 2013 12:26 PM

    tomcat and sepm uses the same port 8005 then. 

    run the management server config wizard and change the port

    Netstat -ano > port.ext

    check the port numbers like 8443 and 8005 

    You will find the process ID using that port number. Then in the task manager add a column for PID and see who is using the port

     



  • 12.  RE: Unable to connect to SEPM after reinstallation

    Broadcom Employee
    Posted Mar 19, 2013 01:19 PM

    Hi,

    Please mention OS version details where SEPM is installed.

    There are different steps to resolve this issue.

    Check these public KB's as well:

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

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

    Symantec Endpoint Protection Manager service stops with a Java -1 error in the event log

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

    Java -1 Errors and HTTP 500 errors when connecting to the Symantec Endpoint Protection Manager on a Windows Server 2008 64 bit

    http://www.symantec.com/business/support/index?page=content&id=TECH96006&key=55357&actp=LIST



  • 13.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 07:52 AM

    Hi,

    it is windows server 2003 and SEMP 11. I still get error:

    The Java Virtual Machine has exited with a code of 1, the service is being stopped.
    Event ID 4096

    is any way to solve this?



  • 14.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 07:59 AM
    I can not find that servers are listening on ports: TCP ports 8443, 9090 netstat -ano | find "9090" netstat -ano | find "8443" are empty


  • 15.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 07:59 AM
    I followed this link, does not helped: http://www.symantec.com/business/support/index?page=content&id=TECH123142&locale=en_US


  • 16.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 08:05 AM
    This is what I got from catalina.out 2013.3.21 14.00.56 org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-9090 2013.3.21 14.00.57 org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8443 Starting service SCM Apache Tomcat/4.1.37-LE-jdk1.4 Has valid SAV license Info>> No SNAC license file in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: ================== Server Environment =================== 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: os.name = Windows 2003 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: os.version = 5.2 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: os.arch = x86 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: java.version = 1.5.0_15 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: java.vendor = Sun Microsystems Inc. 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: java.vm.name = Java HotSpot(TM) Server VM 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: java.vm.version = 1.5.0_15-b04 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: java.user = null 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: user.language = lt 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: user.country = LT 2013.3.21 14.00.59 com.sygate.scm.server.util.ServerLogger writeHeader SEVERE: scm.server.version = 11.0.4202.75 2013.3.21 14.01.06 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=protocolHandler,className=org.apache.coyote.http11.Http11Protocol 2013.3.21 14.01.06 org.apache.commons.modeler.Registry findManagedBean FINE: Looking for descriptor 2013.3.21 14.01.06 org.apache.commons.modeler.Registry findManagedBean FINE: Introspecting 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public java.net.InetAddress org.apache.coyote.http11.Http11BaseProtocol.getAddress() 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public java.util.Iterator org.apache.coyote.http11.Http11BaseProtocol.getAttributeNames() 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public void org.apache.coyote.http11.Http11BaseProtocol.setAddress(java.net.InetAddress) class java.net.InetAddress 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public void org.apache.coyote.http11.Http11BaseProtocol.setAdapter(org.apache.coyote.Adapter) interface org.apache.coyote.Adapter 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public org.apache.coyote.Adapter org.apache.coyote.http11.Http11BaseProtocol.getAdapter() 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute sSLImplementation public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getSSLImplementation() public void org.apache.coyote.http11.Http11BaseProtocol.setSSLImplementation(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute serverSoTimeout public int org.apache.coyote.http11.Http11BaseProtocol.getServerSoTimeout() public void org.apache.coyote.http11.Http11BaseProtocol.setServerSoTimeout(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute compression public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getCompression() public void org.apache.coyote.http11.Http11BaseProtocol.setCompression(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute keystore public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getKeystore() public void org.apache.coyote.http11.Http11BaseProtocol.setKeystore(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute socketCloseDelay public int org.apache.coyote.http11.Http11BaseProtocol.getSocketCloseDelay() public void org.apache.coyote.http11.Http11BaseProtocol.setSocketCloseDelay(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute compressableMimeType public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getCompressableMimeType() public void org.apache.coyote.http11.Http11BaseProtocol.setCompressableMimeType(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxKeepAliveRequests public int org.apache.coyote.http11.Http11BaseProtocol.getMaxKeepAliveRequests() public void org.apache.coyote.http11.Http11BaseProtocol.setMaxKeepAliveRequests(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute compressionMinSize public int org.apache.coyote.http11.Http11BaseProtocol.getCompressionMinSize() public void org.apache.coyote.http11.Http11BaseProtocol.setCompressionMinSize(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute disableUploadTimeout public boolean org.apache.coyote.http11.Http11BaseProtocol.getDisableUploadTimeout() public void org.apache.coyote.http11.Http11BaseProtocol.setDisableUploadTimeout(boolean) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute keytype public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getKeytype() public void org.apache.coyote.http11.Http11BaseProtocol.setKeytype(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute keypass public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getKeypass() public void org.apache.coyote.http11.Http11BaseProtocol.setKeypass(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute name public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getName() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute backlog public int org.apache.coyote.http11.Http11BaseProtocol.getBacklog() public void org.apache.coyote.http11.Http11BaseProtocol.setBacklog(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute domain public java.lang.String org.apache.coyote.http11.Http11Protocol.getDomain() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxSavePostSize public int org.apache.coyote.http11.Http11BaseProtocol.getMaxSavePostSize() public void org.apache.coyote.http11.Http11BaseProtocol.setMaxSavePostSize(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute reportedname public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getReportedname() public void org.apache.coyote.http11.Http11BaseProtocol.setReportedname(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute protocol public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getProtocol() public void org.apache.coyote.http11.Http11BaseProtocol.setProtocol(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute ciphers public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getCiphers() public void org.apache.coyote.http11.Http11BaseProtocol.setCiphers(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute keepAlive public boolean org.apache.coyote.http11.Http11BaseProtocol.getKeepAlive() public void org.apache.coyote.http11.Http11BaseProtocol.setKeepAlive(boolean) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute clientauth public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getClientauth() public void org.apache.coyote.http11.Http11BaseProtocol.setClientauth(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute socketFactory public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getSocketFactory() public void org.apache.coyote.http11.Http11BaseProtocol.setSocketFactory(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxThreads public int org.apache.coyote.http11.Http11BaseProtocol.getMaxThreads() public void org.apache.coyote.http11.Http11BaseProtocol.setMaxThreads(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute soTimeout public int org.apache.coyote.http11.Http11BaseProtocol.getSoTimeout() public void org.apache.coyote.http11.Http11BaseProtocol.setSoTimeout(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute secure public boolean org.apache.coyote.http11.Http11BaseProtocol.getSecure() public void org.apache.coyote.http11.Http11BaseProtocol.setSecure(boolean) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxHttpHeaderSize public int org.apache.coyote.http11.Http11BaseProtocol.getMaxHttpHeaderSize() public void org.apache.coyote.http11.Http11BaseProtocol.setMaxHttpHeaderSize(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute keyAlias public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getKeyAlias() public void org.apache.coyote.http11.Http11BaseProtocol.setKeyAlias(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute strategy public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getStrategy() public void org.apache.coyote.http11.Http11BaseProtocol.setStrategy(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute restrictedUserAgents public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getRestrictedUserAgents() public void org.apache.coyote.http11.Http11BaseProtocol.setRestrictedUserAgents(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute threadPriority public int org.apache.coyote.http11.Http11BaseProtocol.getThreadPriority() public void org.apache.coyote.http11.Http11BaseProtocol.setThreadPriority(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute minSpareThreads public int org.apache.coyote.http11.Http11BaseProtocol.getMinSpareThreads() public void org.apache.coyote.http11.Http11BaseProtocol.setMinSpareThreads(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute server public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getServer() public void org.apache.coyote.http11.Http11BaseProtocol.setServer(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute socketBuffer public int org.apache.coyote.http11.Http11BaseProtocol.getSocketBuffer() public void org.apache.coyote.http11.Http11BaseProtocol.setSocketBuffer(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute port public int org.apache.coyote.http11.Http11BaseProtocol.getPort() public void org.apache.coyote.http11.Http11BaseProtocol.setPort(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute algorithm public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getAlgorithm() public void org.apache.coyote.http11.Http11BaseProtocol.setAlgorithm(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute protocols public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getProtocols() public void org.apache.coyote.http11.Http11BaseProtocol.setProtocols(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxSpareThreads public int org.apache.coyote.http11.Http11BaseProtocol.getMaxSpareThreads() public void org.apache.coyote.http11.Http11BaseProtocol.setMaxSpareThreads(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute soLinger public int org.apache.coyote.http11.Http11BaseProtocol.getSoLinger() public void org.apache.coyote.http11.Http11BaseProtocol.setSoLinger(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute objectName public javax.management.ObjectName org.apache.coyote.http11.Http11Protocol.getObjectName() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute timeout public int org.apache.coyote.http11.Http11BaseProtocol.getTimeout() public void org.apache.coyote.http11.Http11BaseProtocol.setTimeout(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute tcpNoDelay public boolean org.apache.coyote.http11.Http11BaseProtocol.getTcpNoDelay() public void org.apache.coyote.http11.Http11BaseProtocol.setTcpNoDelay(boolean) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute noCompressionUserAgents public java.lang.String org.apache.coyote.http11.Http11BaseProtocol.getNoCompressionUserAgents() public void org.apache.coyote.http11.Http11BaseProtocol.setNoCompressionUserAgents(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Setting name: org.apache.coyote.http11.Http11Protocol 2013.3.21 14.01.06 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.06 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.coyote.http11.Http11Protocol@1248f2b scm:type=protocolHandler,className=org.apache.coyote.http11.Http11Protocol 2013.3.21 14.01.06 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=ThreadPool,name=http-9090 2013.3.21 14.01.06 org.apache.commons.modeler.Registry findManagedBean FINE: Looking for descriptor 2013.3.21 14.01.06 org.apache.commons.modeler.Registry findManagedBean FINE: Introspecting 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public java.util.Enumeration org.apache.tomcat.util.threads.ThreadPool.getThreads() 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource initMethods FINE: Unsupported type public org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable org.apache.tomcat.util.threads.ThreadPool.getMonitor() 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute name public java.lang.String org.apache.tomcat.util.threads.ThreadPool.getName() public void org.apache.tomcat.util.threads.ThreadPool.setName(java.lang.String) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute minSpareThreads public int org.apache.tomcat.util.threads.ThreadPool.getMinSpareThreads() public void org.apache.tomcat.util.threads.ThreadPool.setMinSpareThreads(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute currentThreadsBusy public int org.apache.tomcat.util.threads.ThreadPool.getCurrentThreadsBusy() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute daemon public boolean org.apache.tomcat.util.threads.ThreadPool.getDaemon() public void org.apache.tomcat.util.threads.ThreadPool.setDaemon(boolean) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute threadStatus public java.lang.String[] org.apache.tomcat.util.threads.ThreadPool.getThreadStatus() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute sequence public int org.apache.tomcat.util.threads.ThreadPool.getSequence() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute currentThreadCount public int org.apache.tomcat.util.threads.ThreadPool.getCurrentThreadCount() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxSpareThreads public int org.apache.tomcat.util.threads.ThreadPool.getMaxSpareThreads() public void org.apache.tomcat.util.threads.ThreadPool.setMaxSpareThreads(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxThreads public int org.apache.tomcat.util.threads.ThreadPool.getMaxThreads() public void org.apache.tomcat.util.threads.ThreadPool.setMaxThreads(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute threadParam public java.lang.String[] org.apache.tomcat.util.threads.ThreadPool.getThreadParam() null 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute threadPriority public int org.apache.tomcat.util.threads.ThreadPool.getThreadPriority() public synchronized void org.apache.tomcat.util.threads.ThreadPool.setThreadPriority(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Setting name: org.apache.tomcat.util.threads.ThreadPool 2013.3.21 14.01.06 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.06 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.tomcat.util.threads.ThreadPool@1735b26 scm:type=ThreadPool,name=http-9090 2013.3.21 14.01.06 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=GlobalRequestProcessor,name=http-9090 2013.3.21 14.01.06 org.apache.commons.modeler.Registry findManagedBean FINE: Looking for descriptor 2013.3.21 14.01.06 org.apache.commons.modeler.Registry findManagedBean FINE: Introspecting 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute requestCount public synchronized int org.apache.coyote.RequestGroupInfo.getRequestCount() public synchronized void org.apache.coyote.RequestGroupInfo.setRequestCount(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxTime public synchronized long org.apache.coyote.RequestGroupInfo.getMaxTime() public synchronized void org.apache.coyote.RequestGroupInfo.setMaxTime(long) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute bytesSent public synchronized long org.apache.coyote.RequestGroupInfo.getBytesSent() public synchronized void org.apache.coyote.RequestGroupInfo.setBytesSent(long) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute bytesReceived public synchronized long org.apache.coyote.RequestGroupInfo.getBytesReceived() public synchronized void org.apache.coyote.RequestGroupInfo.setBytesReceived(long) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute processingTime public synchronized long org.apache.coyote.RequestGroupInfo.getProcessingTime() public synchronized void org.apache.coyote.RequestGroupInfo.setProcessingTime(long) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute errorCount public synchronized int org.apache.coyote.RequestGroupInfo.getErrorCount() public synchronized void org.apache.coyote.RequestGroupInfo.setErrorCount(int) 2013.3.21 14.01.06 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Setting name: org.apache.coyote.RequestGroupInfo 2013.3.21 14.01.06 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.coyote.RequestGroupInfo@190b72c scm:type=GlobalRequestProcessor,name=http-9090 2013.3.21 14.01.07 org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-9090 2013.3.21 14.01.07 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=protocolHandler,className=org.apache.coyote.http11.Http11Protocol 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.07 org.apache.commons.modeler.Registry registerComponent FINE: Unregistering existing component scm:type=protocolHandler,className=org.apache.coyote.http11.Http11Protocol 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.coyote.http11.Http11Protocol@1e6f0ef scm:type=protocolHandler,className=org.apache.coyote.http11.Http11Protocol 2013.3.21 14.01.07 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=ThreadPool,name=http-8443 2013.3.21 14.01.07 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=RequestProcessor,worker=http-9090,name=HttpRequest0 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.07 org.apache.commons.modeler.Registry findManagedBean FINE: Looking for descriptor 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.tomcat.util.threads.ThreadPool@1db9f45 scm:type=ThreadPool,name=http-8443 2013.3.21 14.01.07 org.apache.commons.modeler.Registry findManagedBean FINE: Introspecting 2013.3.21 14.01.07 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=GlobalRequestProcessor,name=http-8443 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute virtualHost public java.lang.String org.apache.coyote.RequestInfo.getVirtualHost() null 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute bytesSent public long org.apache.coyote.RequestInfo.getBytesSent() public void org.apache.coyote.RequestInfo.setBytesSent(long) 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.coyote.RequestGroupInfo@1b59919 scm:type=GlobalRequestProcessor,name=http-8443 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute method public java.lang.String org.apache.coyote.RequestInfo.getMethod() null 2013.3.21 14.01.07 org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8443 StandardServer.await: create[8005]: java.net.BindException: Address already in use: JVM_Bind java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.<init>(ServerSocket.java:185) at org.apache.catalina.core.StandardServer.await(StandardServer.java:501) at org.apache.catalina.startup.Catalina.start(Catalina.java:493) at org.apache.catalina.startup.Catalina.execute(Catalina.java:371) at org.apache.catalina.startup.Catalina.process(Catalina.java:134) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute remoteAddr public java.lang.String org.apache.coyote.RequestInfo.getRemoteAddr() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute requestBytesSent public long org.apache.coyote.RequestInfo.getRequestBytesSent() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute contentLength public int org.apache.coyote.RequestInfo.getContentLength() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute workerThreadName public java.lang.String org.apache.coyote.RequestInfo.getWorkerThreadName() public void org.apache.coyote.RequestInfo.setWorkerThreadName(java.lang.String) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute bytesReceived public long org.apache.coyote.RequestInfo.getBytesReceived() public void org.apache.coyote.RequestInfo.setBytesReceived(long) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute requestProcessingTime public long org.apache.coyote.RequestInfo.getRequestProcessingTime() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute globalProcessor public org.apache.coyote.RequestGroupInfo org.apache.coyote.RequestInfo.getGlobalProcessor() public void org.apache.coyote.RequestInfo.setGlobalProcessor(org.apache.coyote.RequestGroupInfo) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute protocol public java.lang.String org.apache.coyote.RequestInfo.getProtocol() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute currentQueryString public java.lang.String org.apache.coyote.RequestInfo.getCurrentQueryString() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxRequestUri public java.lang.String org.apache.coyote.RequestInfo.getMaxRequestUri() public void org.apache.coyote.RequestInfo.setMaxRequestUri(java.lang.String) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute requestBytesReceived public long org.apache.coyote.RequestInfo.getRequestBytesReceived() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute serverPort public int org.apache.coyote.RequestInfo.getServerPort() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute stage public int org.apache.coyote.RequestInfo.getStage() public void org.apache.coyote.RequestInfo.setStage(int) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute requestCount public int org.apache.coyote.RequestInfo.getRequestCount() public void org.apache.coyote.RequestInfo.setRequestCount(int) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute maxTime public long org.apache.coyote.RequestInfo.getMaxTime() public void org.apache.coyote.RequestInfo.setMaxTime(long) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute processingTime public long org.apache.coyote.RequestInfo.getProcessingTime() public void org.apache.coyote.RequestInfo.setProcessingTime(long) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute currentUri public java.lang.String org.apache.coyote.RequestInfo.getCurrentUri() null 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Introspected attribute errorCount public int org.apache.coyote.RequestInfo.getErrorCount() public void org.apache.coyote.RequestInfo.setErrorCount(int) 2013.3.21 14.01.07 org.apache.commons.modeler.modules.MbeansDescriptorsIntrospectionSource createManagedBean FINE: Setting name: org.apache.coyote.RequestInfo 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.coyote.RequestInfo@3acc67 scm:type=RequestProcessor,worker=http-9090,name=HttpRequest0 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Getting new thread data 2013.3.21 14.01.07 org.apache.commons.modeler.Registry registerComponent FINE: Managed= scm:type=RequestProcessor,worker=http-8443,name=HttpRequest1 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean <init> FINE: default constructor 2013.3.21 14.01.07 org.apache.commons.modeler.BaseModelMBean preRegister FINE: preRegister org.apache.coyote.RequestInfo@bd4e3c scm:type=RequestProcessor,worker=http-8443,name=HttpRequest1 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Getting new thread data Stopping service SCM 2013.3.21 14.01.07 org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-9090 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.coyote.http11.Http11BaseProtocol destroy INFO: Stopping Coyote HTTP/1.1 on http-8443 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate 2013.3.21 14.01.07 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run FINE: Terminate WebappClassLoader: Lifecycle error : CL stopped java.lang.Exception: Stack trace at java.lang.Thread.dumpStack(Thread.java:1158) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1426) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at com.sygate.scm.server.task.AgentLogCollector.run(AgentLogCollector.java:110) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462)


  • 17.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 08:07 AM
    scm-server-0.log: 2013-03-21 14:00:59.906 SEVERE: ================== Server Environment =================== 2013-03-21 14:00:59.921 SEVERE: os.name = Windows 2003 2013-03-21 14:00:59.921 SEVERE: os.version = 5.2 2013-03-21 14:00:59.921 SEVERE: os.arch = x86 2013-03-21 14:00:59.921 SEVERE: java.version = 1.5.0_15 2013-03-21 14:00:59.921 SEVERE: java.vendor = Sun Microsystems Inc. 2013-03-21 14:00:59.921 SEVERE: java.vm.name = Java HotSpot(TM) Server VM 2013-03-21 14:00:59.921 SEVERE: java.vm.version = 1.5.0_15-b04 2013-03-21 14:00:59.921 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre 2013-03-21 14:00:59.921 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat 2013-03-21 14:00:59.921 SEVERE: java.user = null 2013-03-21 14:00:59.921 SEVERE: user.language = lt 2013-03-21 14:00:59.921 SEVERE: user.country = LT 2013-03-21 14:00:59.921 SEVERE: scm.server.version = 11.0.4202.75 2013-03-21 14:01:00.312 INFO: Server startup 2013-03-21 14:01:03.515 FINE: updProcessState: checking... 2013-03-21 14:01:03.593 FINE: updProcessState: The process status has been checked. 2013-03-21 14:01:03.593 FINE: updProcessState: checking... 2013-03-21 14:01:03.640 FINE: updProcessState: The process status has been checked. 2013-03-21 14:01:05.218 SEVERE: ================== StartClientTransport =================== 2013-03-21 14:01:06.406 FINE: Task scheduled 2013-03-21 14:01:06.406 SEVERE: Schedule is started!


  • 18.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 08:36 AM

    Another way you could try to find out what port the SEPM is listening on is to look through Task Manager for the semsrv.exe process, update Task Manager to show the Process ID, then search for the PID in netstat as below:

    netstat -pano tcp | findstr <PIDforSemsrv.exe>

    See if that comes back with anything.

    On another note, Symantec generally recommend against installing the SEPM on a server already running tomcat.  IIRC it can generate some unpredicatable behaviour, hence why the LUA and SEPM should not be on the same box (as both use tomcat).

    Also, your version of SEP is almost 4 years old now, have you considered upgrading? SEP11MR4MP2 went EOL back in 2011 and goes EOSL (no Symantec support at all) in January next year.



  • 19.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 08:42 AM
    Yes I know all this regarding nestat. I founds ports 9090 and 8443 are only available when you start SEMP. But now I can not start SEMP I have another server that has same configuration with tomcat installed in it and SEPM works. This server fails after reinstallation. Support is not the issue, issue is that I can not start SEMP, and why ?


  • 20.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 08:53 AM

    I didn't see anything in the logs you posted that suggest why it failed to start.  Any more from the scm-server-0.log?  The one you posted was surpisringly short.



  • 21.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:06 AM

    I did post in my first post to check for port 8005. You have checked all other ports from netstat but not this one.

    from the log what you have posted I do see

    ==============

     create[8005]: java.net.BindException: Address already in use: JVM_Bind
    java.net.BindException: Address already in use: JVM_Bind

    ============

    Run the management server config wizard and change this port to 8006. start the sepm service..

     

    That should fix..



  • 22.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:08 AM
    followed these steps: 1.Stop the Symantec Endpoint Protection Manager service 2.Open the file C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties and find the line which reads scm.log.loglevel=WARNING and change it to scm.log.loglevel=FINEST. If this line does not exist, add scm.log.loglevel=FINEST to the bottom of the file. To debug SEPM notifications, also add: scm.mail.troubleshoot=1 To debug SEPM proxy authentication, also add: scm.proxy.debug=1 Now I see in conf.properties: scm.log.loglevel=finest scm.server.name=srv scm.server.id=040AA043AC18170400D2B44B45E6672C scm.mail.troubleshoot=1 scm.proxy.debug=1 and scm-server-01 logs is: 2013-03-21 15:04:22.703 SEVERE: ================== Server Environment =================== 2013-03-21 15:04:22.718 SEVERE: os.name = Windows 2003 2013-03-21 15:04:22.718 SEVERE: os.version = 5.2 2013-03-21 15:04:22.718 SEVERE: os.arch = x86 2013-03-21 15:04:22.718 SEVERE: java.version = 1.5.0_15 2013-03-21 15:04:22.718 SEVERE: java.vendor = Sun Microsystems Inc. 2013-03-21 15:04:22.718 SEVERE: java.vm.name = Java HotSpot(TM) Server VM 2013-03-21 15:04:22.718 SEVERE: java.vm.version = 1.5.0_15-b04 2013-03-21 15:04:22.718 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre 2013-03-21 15:04:22.718 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat 2013-03-21 15:04:22.718 SEVERE: java.user = null 2013-03-21 15:04:22.718 SEVERE: user.language = lt 2013-03-21 15:04:22.718 SEVERE: user.country = LT 2013-03-21 15:04:22.718 SEVERE: scm.server.version = 11.0.4202.75 2013-03-21 15:04:22.765 INFO: Server startup 2013-03-21 15:04:27.656 FINE: updProcessState: checking... 2013-03-21 15:04:27.671 FINE: updProcessState: The process status has been checked. 2013-03-21 15:04:27.687 FINE: updProcessState: checking... 2013-03-21 15:04:27.687 FINE: updProcessState: The process status has been checked. 2013-03-21 15:04:29.218 SEVERE: ================== StartClientTransport =================== 2013-03-21 15:04:30.546 FINE: Task scheduled 2013-03-21 15:04:30.546 SEVERE: Schedule is started! I missed something?


  • 23.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:12 AM
    Rafeeq, in Management server Configuration wizard is not possible to change that port as you can change 8443 and 9090. Is any other way to change it?


  • 24.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:14 AM

    YOu could follow the steps in this article:

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



  • 25.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:20 AM

    Messaged you the steps

    let me know if this was success.



  • 26.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:29 AM
    situation is clear, now I got that he is not able to comunicate with reporting services,


  • 27.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:33 AM

    Best check that the Symanetc Web Server site in IIS is started



  • 28.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:37 AM
    I got: The server received an invalid response from another server while attempting to fulfill the request.


  • 29.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:37 AM
    all services are started. I tried to connect to http://localhost:8014/reporting/login/login.php?MSG= It asked me to enter new password and now it is searching and searching with no results. Is it sothnig wrong with iis? Still no errors in event logs


  • 30.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 09:38 AM

    do a repair of sepm.

    check if you have enahanced security is enabled in IE

    fix the database connectivity

    this has to do with IIS reporting virtual directory make sure you have integrated windows authentication option checked ,.



  • 31.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:05 AM
    I tried to repair SEPM. How to fix database connectivity? Should I follow this? http://www.symantec.com/connect/forums/bad-gateway-error but it worked before


  • 32.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:13 AM
    maybe is something to do with another server. I am not sure if these servers were in cluster with comon SQL DB or just with replication. How can I found this? thanks


  • 33.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:13 AM

    fresh install right, just uninstall sepm. install again

    change the port to 8006

    everything should work fine.  DB connectivty document from this document

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

    check the Database Assessment

     


  • 34.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:21 AM

    if there is any replication then it wil be listed under servers tab of SEPM.



  • 35.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:37 AM
    reinstalled SEMP same thing, tired already of this problem


  • 36.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:44 AM

    Any new log entries in the scm-server-0.log file?

    Also, it might be worth you enabling IIS logging, to see if anything is going awry on that side.



  • 37.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 10:48 AM

    There are few things which I would like to mention here

    1) The version what you are installing is 11.0.4. this version is very very old. ( not sure if this is project requirement so that you need to install this version)

    2) whenever you install SEPM you should be on the console session 0. 

    if via RDP then it should be mstsc /console.

    3)Make sure the package is copied locally and not run from shared drive

    4) Reporting service is most of the time coz of IIS permissons. Is the DB connection Successful? what happens when you try to browse the reporting virtual directory in IIS?

    is the anonymous account enabled in your AD? most of the times it will be disabled in IE

    Not sure if you have already tried. If you put admin account instead of anonymous user Everything should work. There are few permission testing tool from MS which can do the job



  • 38.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 11:09 AM
    4) Reporting service is most of the time coz of IIS permissons. Is the DB connection Successful? what happens when you try to browse the reporting virtual directory in IIS? How to check DB connection from IIS to SQL DB? Anonymous Account in AD?? I am not using it, what does mean "Disabled IE"?


  • 39.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 11:19 AM

    Anonymous Account in AD?? I am not using it,

    -> IUSR_Computer name account in IIS for symatnec web server

    Whats the result of this step... whats the database you are using SQL or Embedded? which one did  you select during install?

     

    Database Assessment


    • Verify communication to the embedded (Sybase) database.
      Verify that the "Symantec Embedded Database" service is running and that the "dbsrv9.exe" process is listening on TCP port 2638.
      • Test the ODBC connection.
        1. Click StartControl Panel
        2. Open Administrator Tools
        3. Double-click Data Sources (ODBC)
        4. Select the System DSN tab
        5. Double-click the SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
          • Name: SymantecEndpointSecurityDSN
          • Description:<Anything><anything></anything>
          • Server: Servername\InstanceName (Can be blank as it is localized, otherwise specify default "sem5")
          • Login ID: dba
          • Password: <password></password><password>

            Note: If the “Encrypt password” box on the Login tab is not checked, your password will be stored as plain text in the Windows registry.

             
        6. Leave the default settings for the remaining items and click Finish
        7. Click Test Data Source, and verify that it states "Success"
        8. Click OK

      Verify communication to the Remote (SQL) Database.
      • Verify that you have specified a named instance during installation and configuration. Example: \\<server name=""></server><server name>\<instance name><instance name=""></instance>
      • Verify SQL Server is running and properly configured.
      • Verify the network connections between Symantec Endpoint Protection Manager and the SQL database.
      • Test the ODBC connection.
        1. Click StartControl Panel
        2. Open Administrator Tools
        3. Double-click Data Sources (ODBC)
        4. Select the System DSN tab
        5. Double-click SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:
          • Name: SymantecEndpointSecurityDSN
          • Description:<Anything><anything></anything>
          • Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
          • Login ID: sa
          • Password: <password></password><password>

             
        6. Leave the defaults for the rest of the items and click Finish
        7. Click Test Data Source on the next page and ensure it states "Success"
        8. Click OK


        • For 64bit ODBC communication follow the link below.

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



  • 40.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 11:29 AM
    I was able to connect, but not sure which connection paramaters symantec is using, as for example SQL instance is not default and user should be for SA


  • 41.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 11:45 AM

    Now it is installed with embendded DB, but before uninstalling Symantec asked me to remove SQL DB from server, but it could not connect to DB so I skiped DB removal. It seems that symantec can not cumunicate with DB, how to configure right connection to SQL server? just through ODBC?



  • 42.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 11:56 AM

    You are confusing me :).. forget about sQL now. You have installed with embedded DB? and you were able to connect using the ODBC as mentioned in the above document.

    for Embedded it will be DBA and password will be your SepM password. if this was successful . please post the screen shot.

     



  • 43.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:16 PM
    OK, I installed SEPM with Microsoft SQL 2005 database. I replicated it succesfully with other site. Everything was fine until I tried to run console. Console error: Unable to connect with the reporting component http://localhost:8014/reporting/login/Login_verify.php error: Bad Gateway ------------------------------------------------------------------------------- The server received an invalid response from another server while attempting to fulfill the request. Is any solution for this? thanks,


  • 44.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:23 PM
    could you tel what is the solution for this case 281755991 this guy say that this is permissions problem, but what permissions to change ? https://www-secure.symantec.com/connect/forums/sepm-unable-communicate-reporting-component Also, I want to mention, that I was able to open console when I installed server with embendded DB. But before all this destroyment made by me SEPM was running on MS SQL server.


  • 45.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:23 PM

    Closest I can find is this article

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

    But your earlier posts suggest you;ve already checked through the permissions for the site, right?



  • 46.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:26 PM

    Yes, I checked, these permissions are ok,



  • 47.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:30 PM

    If he's talking about the NTFS permissions for the folder that the Symantec Web Site in IIS is pointing to, then it should be the below directory:

    %ProgramFiles%\Symantec\Symantec Endpoint Protection Manager\Inetpub

    The Reporting sub-folder is in this location, but if you've already checked the NTFS permissions for this then I'd suggest enabling IIS logging



  • 48.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:32 PM

    have you checked the database connection yet? ..........

     



  • 49.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:35 PM
    no he is talking about other directories "not the Symantec ones" what else permissions I can change? one more question, if I open ODBC I see my windows logon user in user tab. Then I configured SQL I entered SQL sa. How can I be sure that symantec uses SA and successfully connect to DB? what else can I do? thanks


  • 50.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 01:57 PM

    That is coz you might have set SeM5.db to use integrated windows authentication. 

    Once you mention Sa and password. it will try to connect to sql db. Its only based on these accounts it will try to connect.

    DB connectivity is the first thing to check and you never checked that so far.

    All the best with your issue.

     

     



  • 51.  RE: Unable to connect to SEPM after reinstallation

    Posted Mar 21, 2013 03:54 PM

     

    could you clear, what exactly user name and password Symantec is using connect to DB? 
     
    Those that I used during Symantec DB configuration? I used SA user and password.
     
     
     
    Also I run SEMP on windows 2003 Domain Controller can this be the cause of the issue?  
     
     
     
    Also want to mention. After successfull configuration with SQL server I started SEMP for the first time and it failed with Unable to comunicat error. Then I tried to login reporting services through http and it force me to change password. But after this I got Bad Gateway error on report site.