Endpoint Protection

 View Only
Expand all | Collapse all

SEPM failed to connect to server

  • 1.  SEPM failed to connect to server

    Posted Apr 12, 2010 11:26 AM
    I've been tasked with installing a fresh version of Symantec Endpoint Protection Manager 11.0.5 on a backup windows server 03 R2 which we will then migrate our existing older symantec antivirus to. I have a fresh install of SEPM running with the embedded database. Upon completing the management server configuration wizard it takes me to the management console logon screen. When I attempt to log on with the admin account and password created during the wizard, using the default server port localhost:8443, I get the error that SEPM has failed to connect to the server. I've configured IIS as per the instructions in the support document Symantec offers. I also cannot remotely connect to the console via the web server port 9090. I've been reading through a lot of these forum posts and it seems like I'm not the only one with this error. I've tried following the advice of the other posts but to no avail. Any ideas why this might be happening or what I need to configure to allow access to the server? Thanks for your support.


  • 2.  RE: SEPM failed to connect to server

    Posted Apr 12, 2010 11:35 AM



    Can you try logging in locally  with the ip adress of the machine on which SEPM is installed.

    Insted of localhost:8443  type the ip address of the machine : 8443

    Check the logs under C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs

    catalina.out
    scm-server-0.log


  • 3.  RE: SEPM failed to connect to server

    Posted Apr 12, 2010 12:01 PM
    Well when I try to log in with the ip address of our server instead of localhost it still gives me the same error, adding the optional domain we're in didn't help either. When I go to the logs file under tomcat in the SEPM folder found in program files I see the following: install_log.err, install_log.out, LuCatalog.log, smbinstall.err, and smbinstall.out. I see no catalina.out file or scm-server-0.log. The logs I do see however I am unable to open, they bring up the browse for a program to open them window when clicked on.


  • 4.  RE: SEPM failed to connect to server

    Posted Apr 12, 2010 12:15 PM
    Do a repair of sepm from add/remove clients
    in the iis; 
    under directory security; make sure that IP address is allowed for all
    check windows authentication under access tab
    follow this document. i think you need to add network service..

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

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


  • 5.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 09:50 AM

    Hello Rafeeq,

    Thanks for the advice, but when I  tried all the steps in those support forms I am still unable to connect to the management console. Network Service was already added in all the locations the forms suggested. I have gone into the ISS and made the appropriate changes as well. But sttill I am given the error that SEPM failed to connect to the server when I try to log in. I have uninstalled and reinstalled SEPM a couple times trying to catch what part I might be configuring wrong, but there are so few steps in the wizard I don't believe I could have.



  • 6.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 10:05 AM
    any files in here?

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

    try uninstalling IIS
    reinstall
    repair sepm from add/remove programs.
    try to log in again.


  • 7.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 10:39 AM
    When I go to the logs file under tomcat in the SEPM folder found in program files I see the following: install_log.err, install_log.out, LuCatalog.log, smbinstall.err, and smbinstall.out.

    I've uninstalled and reinstalled IIS and run the repair from add/remove but I'm still getting the same error when attempting to log onto the management console.

    Do I need to install the client or the integration component on the server?


  • 8.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 10:44 AM
    When I check services running, I see the embedded database is started but the Symantec Endpoint Protection Manager is not. When I attempt to start it, it tells me it started and then stopped because some services stop automatically if they have no work to do.


  • 9.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 10:45 AM
    no ; its not needed.
    is it a 64 bit box?
    if yes then try this..
    http://support.microsoft.com/kb/894435

    i
    nstalling SEPM on a RDP session?


  • 10.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 10:52 AM
    I'm running on a 32 bit '03 Server and installing from the network. The files are located on the other server.


  • 11.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 11:04 AM
    Do you see symantec embedded dB service running or listed in the services.msc?

    start - all programs
    syamtnec endpoint
    run the management server configuration wizard

    remove sepm
    copy the file local to the box
    run it locally.
    you should find the logs.



  • 12.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 11:04 AM
    Do you see symantec embedded dB service running or listed in the services.msc?

    start - all programs
    syamtnec endpoint
    run the management server configuration wizard

    remove sepm
    copy the file local to the box
    run it locally.
    you should find the logs.



  • 13.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 11:37 AM
    yes, the embedded DB is started in the services.msc. I uninstalled SEPM and moved the file containing the setup files onto the local machine, however this did not allow me to log into the management console. I am still facing the Failed to Connect to Server error when I attempt to log on.

    The logs which I can see in the C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs folder are the same as before:  install_log.err, install_log.out, LuCatalog.log, smbinstall.err, and smbinstall.out


  • 14.  RE: SEPM failed to connect to server

    Posted Apr 13, 2010 12:36 PM
    I'm going to reformat our server, since we don't really have anything necessary on it. Hopefully with a fresh server we won't run into these problems when installing SEPM


  • 15.  RE: SEPM failed to connect to server
    Best Answer

    Posted Apr 20, 2010 12:45 PM

    Reformatting the server solved our problems. Must have been something on that old server which was interferring with SEPM. Running into a small issue with deploying the clients now however, but hopefully that will be resolved soon.