Endpoint Protection

 View Only
Expand all | Collapse all

Failed to connect to server. Make sure that the server is running and your session has not timed out

Migration User

Migration UserSep 19, 2010 04:33 AM

  • 1.  Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 19, 2010 04:25 AM

    Hello

    My SEPM was working fine till last week, Today when i tried to login to SEPM i get the error"Failed to connect to server. Make sure that the server is running and your session has not timed out
    "

    I folllowed this kb , still no go

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

    Any help?



  • 2.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 19, 2010 04:27 AM

    In the event viwer are you getting a Java-1 or java 1 error

    Also, please paste the scm server0.log



  • 3.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 19, 2010 04:29 AM

    It is java 1, I am will post the scm .server0.log in a min



  • 4.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 19, 2010 04:30 AM

    Go to  \Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\conf\server.xml
     

    Right-click the server.xml file and click Edit to modify the file:

    Look for port 8005, change the port to another unused port:
    port="8006"

    Save the changes to the "server.xml" file.

    Start the SEPM service.

    Attempt to login to the SEPM.



  • 5.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 19, 2010 04:33 AM

    Pranchand , it is still the same



  • 6.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out
    Best Answer

    Posted Sep 19, 2010 04:35 AM

    Please restart the IIS service and then SEPM service.

    If possible  Reboot the server, I think it will take care of the issue.



  • 7.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 19, 2010 04:37 AM

    Restarted the services , still the same, i am in the process of rebooting, It is also the exchange server, it will take 20 mins for this.



  • 8.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 20, 2010 12:45 AM

    Can you paste/attach the scm-server-0.log which is present in Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\logs?



  • 9.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out



  • 10.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Broadcom Employee
    Posted Sep 20, 2010 02:47 AM

    post the scm-server-0.log from the SEPM after you get the error message. This log will be found at C:\Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\logs.



  • 11.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 20, 2010 04:26 AM

    hi tech-no,

    had the same issue before, appeared to be an IIS problem.

    just to check, have you verified that SEPM service is running? if it's not, try to start it and observe if will remain started just for at least 15secs. In my case, it stops after just a couple of seconds after starting it. This was what caused the failure connecting to server..



  • 12.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 20, 2010 04:36 AM

    Changing The tomcat port ideally resolved the Java 1 error, i am not sure why it did not work in this case. The reboot should do the trick , else please get the scm serevr0.log



  • 13.  RE: Failed to connect to server. Make sure that the server is running and your session has not timed out

    Posted Sep 20, 2010 06:19 AM

    Verify the 

     

    If the Database is on-line, run appropriate ODBC test for your SEPM and 32/64-bit Operating System:

      • 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>

            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.</password>
             
        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 that you have specified a named instance during installation and configuration. Example: \\<server name>\<instance name><server name=""><instance name=""></instance></server>
      • 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 more info

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