Endpoint Protection

 View Only
Expand all | Collapse all

Receiving the following in SEPM: Failed to connect to the server, Address already in use.

Migration User

Migration UserJan 18, 2010 11:55 AM

Migration User

Migration UserJan 18, 2010 12:07 PM

Migration User

Migration UserJan 18, 2010 12:09 PM

Rafeeq

RafeeqJan 18, 2010 12:09 PM

Migration User

Migration UserJan 18, 2010 02:59 PM

  • 1.  Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 11:33 AM

    Hello Everyone,

    I am experiencing a number of challenges revolving around a few errors I am finding in log files and within SEPM.  The first few are seen in SEPM under Admin -> Servers, in the  box that gives Liveupdate and other communication.  I am seeing the following errors:

    January 18, 2010 10:14:17 AM CST:  Failed to connect to the server.
    Make sure that the server is running and your session has not timed out.
    If you can reach the server but cannot log on, make sure that you provided the correct parameters.
    If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000

    And

    January 18, 2010 10:16:21 AM CST:  Address already in use: connect

    I am not seeing anything negative really happening other than I am not able to run liveupdate manually.  I am able to log in just fine, reporting looks fine, the clients are pulling virus defs from our server and symantec.  However when I look at the scm-server-0.log  I get the following repeated a number of times

    2010-01-18 09:29:45.253 SEVERE: ================== Server Environment ===================
    2010-01-18 09:29:45.253 SEVERE: os.name = Windows 2003
    2010-01-18 09:29:45.253 SEVERE: os.version = 5.2
    2010-01-18 09:29:45.253 SEVERE: os.arch = x86
    2010-01-18 09:29:45.253 SEVERE: java.version = 1.5.0_15
    2010-01-18 09:29:45.253 SEVERE: java.vendor = Sun Microsystems Inc.
    2010-01-18 09:29:45.253 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2010-01-18 09:29:45.253 SEVERE: java.vm.version = 1.5.0_15-b04
    2010-01-18 09:29:45.253 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2010-01-18 09:29:45.253 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2010-01-18 09:29:45.253 SEVERE: java.user = null
    2010-01-18 09:29:45.253 SEVERE: user.language = en
    2010-01-18 09:29:45.253 SEVERE: user.country = US
    2010-01-18 09:29:45.253 SEVERE: scm.server.version = 11.0.3001.2224
    2010-01-18 09:29:47.346 SEVERE: ================== StartClientTransport ===================
    2010-01-18 09:29:52.484 SEVERE: Schedule is started!
    2010-01-18 09:29:53.484 SEVERE: StateCheckpointTask connect to secars failed: SERVICE NOT AVAILABLE
    2010-01-18 09:36:14.843 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.net.BindException: Address already in use: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.Socket.connect(Socket.java:520)
     at java.net.Socket.connect(Socket.java:470)
     at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
     at sun.net.www.http.HttpClient.openServer(HttpClient.java:388)
     at sun.net.www.http.HttpClient.openServer(HttpClient.java:523)
     at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
     at sun.net.www.http.HttpClient.New(HttpClient.java:304)
     at sun.net.www.http.HttpClient.New(HttpClient.java:321)
     at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813)
     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765)
     at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934)
     at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:367)
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Failed to connect to the server.

    Make sure that the server is running and your session has not timed out.
    If you can reach the server but cannot log on, make sure that you provided the correct parameters.
    If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:317)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)

    I have ran http://server/secars/secars?hello,secars from both the server as well as a number of client machines and have gotten an "OK".  Services are all up and running.  I have checked with our Network Admins and they have verified that the address for the server with SEPM is unique.  Ran a number of google searches but couldn't find anything that was close to what I am currently experiencing.

    Thank you



  • 2.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 11:40 AM

    Title: 'Failed to connect to server! ErrorCode [0x80020000] with HTTP 415 Unauthorized in the logs'
    Document ID: 2008021215535348
    > Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2008021215535348?Open&seg=ent


  • 3.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 11:43 AM
    Check this KB out -

    Connection failure when logging into the Symantec Endpoint Protection Manager console after the installation of Symantec IM Manager

    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/4adc83564697c7758825732900049520?OpenDocument


    Thomas




  • 4.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 11:45 AM
    Thanks for the link Prachand, however we do not use Proxy settings.  I am able to log into SEPM just fine, I am seeing the Failed to connect to server in the Admin section under servers, in the live feed box.


  • 5.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 11:54 AM
    try doing a repair of sepm from add/remove programs,
    check if that works
    can you write the entire error mesage you get under servers tab?

    are you using replication?

    Symantec Endpoint Protection Manager: Replication from remote site is unsuccessful

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008091017054048

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008101309471148


  • 6.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 11:55 AM
    Do you have replication enabled?


  • 7.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.
    Best Answer

    Posted Jan 18, 2010 11:59 AM

    Title: 'when selecting "Download LiveUpdate Content", it reports Failed to connect to server and ErrorCode [0x80020000]'
    Document ID: 2009042115191948
    > Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009042115191948?Open&seg=ent


  • 8.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 12:04 PM
    No we are currently not using replication.  The full message from the servers are:

    January 18, 2010 10:57:41 AM CST:  Failed to connect to the server.

    Make sure that the server is running and your session has not timed out.
    If you can reach the server but cannot log on, make sure that you provided the correct parameters.
    If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000  [Site: Site]  [Server: Server]
    January 18, 2010 10:55:24 AM CST:  Address already in use: connect 


    This is the message that keeps getting repeated every three minutes.  I have taken out the site and the server names for security reasons.

    I will try a repair in a few moments



  • 9.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.



  • 10.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 12:07 PM
    Running this right now.


  • 11.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 12:09 PM
    No we do not


  • 12.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 12:09 PM
    let me know if works after a repair...


  • 13.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 12:40 PM
    Thanks Prachand Kumar, the link you provided solved my issue.


  • 14.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 02:59 PM
    This solved the liveupdate challenge.  Thank you


  • 15.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 03:27 PM
    I got permission to perform the repair, and was following the link below

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009030414141748

    However, it looks like the last person in charge didn't save our current version anywhere.  Is this needed to perform the repair, or is it needed in case something were to happen?


  • 16.  RE: Receiving the following in SEPM: Failed to connect to the server, Address already in use.

    Posted Jan 18, 2010 03:37 PM
     You won't need the current version for repair..
    Just make sure you are doing this locally on the server not via RDP.

    Even if you'll need your current version ( not for repair)  you can contact symantec they will be able to provide you any version..