Endpoint Protection

 View Only
Expand all | Collapse all

Unable to login to Symantec Endpoint Protection Manager

Migration User

Migration UserOct 13, 2011 10:22 AM

Migration User

Migration UserOct 13, 2011 02:32 PM

Migration User

Migration UserOct 17, 2011 10:42 AM

Migration User

Migration UserOct 17, 2011 04:56 PM

Migration User

Migration UserOct 18, 2011 09:30 AM

Migration User

Migration UserOct 18, 2011 09:35 AM

  • 1.  Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 05, 2011 05:05 PM

    I am not able to login to SEPM. I have attached the  Catalina.out ,scm-server-0.log and db.err files 

    Attachment(s)

    txt
    catalina.out_.txt   21 KB 1 version
    txt
    scmserver1.txt   142 KB 1 version
    txt
    dberr.txt   2 KB 1 version


  • 2.  RE: Unable to login to Symantec Endpoint Protection Manager

    Trusted Advisor
    Posted Oct 06, 2011 01:45 PM

    Hello,

    What version of SEPM have you installed?

    What OS is it installed on?

    Is SEPM installed with Embedded Database OR SQL Database?

    What version of Java installed?

    After Looking at the scm-server-0.log, we found as below:

     

    	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    2011-10-03 12:05:08.472 SEVERE: Unknown Exception during logging
    org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect)
    	at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225)
    	at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)

     

     

    	at java.lang.reflect.Method.invoke(Method.java:597)
    	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    Caused by: java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
    	at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:557)
    	at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:861)
    	at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3967)

     

    Suggestions:

    1) Start the Services

    1. Click Start
    2. Click All Programs
    3. Click Administrative Tool
    4. Click Services
    5. Find the Symantec Embedded Database service, right-click it, and click Start
    6. Find the Symantec Endpoint Protection Manager service, right-click it, and click Start
    7. Wait thirty seconds and then Refresh the screen. Confirm that both services have stayed started.
      1. If either service has stopped, then you will be unable to login to the Symantec Endpoint Protection Manager Console. Further troubleshooting will be required to determine why the service(s) will not stay started.
    8. If both services have stayed started, login to the Symantec Endpoint Protection Manager Console

    2) Check if there is a Loopback Address (127.0.0.1) entry in the Windows HOST file assigned to the Localhost entry. If not, Make sure to insert the Loopback Address and Repair the SEPM

    Hope that helps!!

     



  • 3.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 06, 2011 06:43 PM

    It looks like your embeded database trasaction log is the problem, as indicated by the following error in your dberr.txt file:
    Database cannot be started -- sem5.log is an invalid transaction log

    Please try the steps below to remove the trasaction log and force it to be re-created:

    1. Verify if there is any running instance of dbsrv9 in the Task Manager > Processes tab. If yes, then end that process
    2. Start the Embedded database service. ( If this does not resolve the issue, then follow the steps listed below )
    3. Go to "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\" and rename sem5.log to sem5.log.old for SEP11 and 12.1 ( Please use "Program Files (x86)" instead of "Program Files" if it is a 64 bit machine.
    4. And for SEP 12 RTM Go to "C:\Program Files\Symantec\Symantec Protection Centre\db\" and rename sem5.log to sem5.log.old Click Start, click on Run and Type “CMD” then click OK
    5. In the Command Prompt type: "CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\" and press Enter this will change directories to the folder containing dbsrv9.exe for SEP 11 and dbsrv11.exe for SEP 12
    6. To force the recreation of sem5.log. Type: dbsrv9 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" and press Enter for SEP 11 and Type: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" and press Enter for SEP 12.1
    7. And for SEP 12 To force the recreation of sem5.log. Type: dbsrv9 -f "C:\Program Files\Symantec\Symantec Protection Center\db\sem5.db" and press Enter . 
    8. Click Start, click on Run and Type “services.msc” then click OK and start the Symantec Embedded Database Service
    9. Start the Symantec Endpoint Protection Manager service or Symantec Protection Center 
    10. If it stays started then go ahead and log into the Symantec Endpoint Protection Manager or Symantec Protection Center and everything should now be working properly
    11. If the Symantec Endpoint Protection Manager or Symantec Protection Center service fails to start then run Management Server Configration Wizard in order to log in to the Symantec Endpoint Protection Manager or Symantec Protection Center. 


  • 4.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 10, 2011 04:50 PM

    Yes . Sem5.db is corrupted

    I tried the steps you mentioned . When I typed   dbsrv9 -f "C:\Program Files\Symantec\Symantec Protection Center\db\sem5.db" , I am getting 'dbsrv9 is not recognized as an external or internal command,

    operable program or batch file 

    The version is SEPM 11 and the OS is Windows 2003 R2. Symantec Embedded Database is not starting



  • 5.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 10, 2011 10:45 PM

    E:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32>dbsrv9 -f E:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db

    I am getting an ERROR message "Must specify a database with -a or -f options"

    I tried database backup and restore but the backup fails with Error: "Could not connect to the database. Cannot backpup the site "



  • 6.  RE: Unable to login to Symantec Endpoint Protection Manager

    Broadcom Employee
    Posted Oct 10, 2011 11:55 PM

    check if adding quotes help

    dbsrv9 -f "E:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db"



  • 7.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 11, 2011 01:17 PM

    I am able to start both Embedded Database and SEPM now but not able to login to the console. Is there a way to reset the password



  • 8.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 11, 2011 01:34 PM
    run SEPM\Tools\resetpass.bat However what error do you get while logging in ? Failed to connect...or Account locked... ?


  • 9.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 11, 2011 01:39 PM

    How do I know whether I am connecting to the correct port on login (localhost:8440)



  • 10.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 11, 2011 01:46 PM

    By default its 8445; unless you changed it

    netstat -ano

    what port do u see as listening?



  • 11.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 11, 2011 03:38 PM
      |   view attached

    I have attached the error message while logging in. In the Event Viewer log I am getting the following

    Event Type: Error
    Event Source: semsrv
    Event Category: None
    Event ID: 4096
    Description:
    The Java Virtual Machine has exited with a code of -1, the service is being stopped.
     

    I followed these steps for fixing the error. But it didn't work

    1. Click Start, click Run, type gpedit.msc, and then click OK.
    2. Under Local Computer Policy, expand Computer Configuration, expand Windows Settings, expand Security Settings, and then expand Local Policies.
    3. In the left pane, click User Rights Assignment.
    4. In the right pane, double-click Deny access to this computer from the network.
    5. Click guest and remove.
    6. Click OK two times.
    7. Exit the Group Policy Object Editor
    8. Click Start, click Run, type gpupdate /force, and then click OK.
    9.  Click Start, click Run, type iisreset, and then click OK.


  • 12.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 11, 2011 03:54 PM

    check the ODBC CONNECTION as per this document

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



  • 13.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 12, 2011 02:51 PM

    I checked the ODBC connection. Connection failed: Invalid username and password

    What is the default password



  • 14.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 12, 2011 10:56 PM

    Here are the TCP ports Listening.

    Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       2000
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       772
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       516
      TCP    0.0.0.0:2301           0.0.0.0:0              LISTENING       3028
      TCP    0.0.0.0:2381           0.0.0.0:0              LISTENING       3028
      TCP    0.0.0.0:2638           0.0.0.0:0              LISTENING       5376
      TCP    0.0.0.0:2639           0.0.0.0:0              LISTENING       6004
      TCP    0.0.0.0:3164           0.0.0.0:0              LISTENING       2000
      TCP    0.0.0.0:3166           0.0.0.0:0              LISTENING       2000
      TCP    0.0.0.0:3169           0.0.0.0:0              LISTENING       2000
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       4440
      TCP    0.0.0.0:5555           0.0.0.0:0              LISTENING       1920
      TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING       2412
      TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING       2412
      TCP    0.0.0.0:8530           0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:8531           0.0.0.0:0              LISTENING       4
      TCP    127.0.0.1:1054         0.0.0.0:0              LISTENING       4796
      TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING       1808
      TCP    127.0.0.1:5152         127.0.0.1:1890         CLOSE_WAIT      1808
      TCP    172.16.8.32:80         172.16.13.23:1209      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.13.23:1210      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.13.23:1211      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.13.23:1212      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.17.25:3758      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.17.25:3759      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.24.97:1840      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.24.97:1841      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.25:1166      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.25:1168      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.120:3732     TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.120:3733     TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.120:3734     TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.120:3736     TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.49.5:1201       TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.49.5:1203       TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.49.5:1204       TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.49.5:1206       TIME_WAIT       0
      TCP    172.16.8.32:135        172.16.8.32:4920       ESTABLISHED     772
      TCP    172.16.8.32:139        0.0.0.0:0              LISTENING       4
      TCP    172.16.8.32:1381       172.16.8.115:135       ESTABLISHED     1424
      TCP    172.16.8.32:1382       172.16.8.115:1025      ESTABLISHED     1424
      TCP    172.16.8.32:1400       172.16.8.103:389       ESTABLISHED     2160
      TCP    172.16.8.32:1475       172.16.8.101:389       ESTABLISHED     2160
      TCP    172.16.8.32:1635       172.16.8.32:80         TIME_WAIT       0
      TCP    172.16.8.32:1636       172.16.8.32:8530       TIME_WAIT       0
      TCP    172.16.8.32:1637       172.16.8.32:8530       TIME_WAIT       0
      TCP    172.16.8.32:1644       172.16.14.25:139       TIME_WAIT       0
      TCP    172.16.8.32:1645       172.16.14.25:139       TIME_WAIT       0
      TCP    172.16.8.32:1646       172.16.14.25:139       TIME_WAIT       0
      TCP    172.16.8.32:3389       172.16.9.187:64698     ESTABLISHED     4440
      TCP    172.16.8.32:4100       172.16.8.115:389       CLOSE_WAIT      2000
      TCP    172.16.8.32:4848       172.16.14.23:139       ESTABLISHED     4
      TCP    172.16.8.32:4920       172.16.8.32:135        ESTABLISHED     3236
      TCP    172.16.8.104:80        172.16.13.23:1208      TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.13.23:1213      TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.17.25:3757      TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.24.97:1842      TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.32.25:1165      TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.32.120:3731     TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.32.120:3735     TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.49.5:1202       TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.49.5:1205       TIME_WAIT       0



  • 15.  RE: Unable to login to Symantec Endpoint Protection Manager

    Broadcom Employee
    Posted Oct 13, 2011 12:58 AM

    looks like the SEPM is hosted on port 80, since the ODBC has failed it will not connect. The password would the one you might have entered during the installation of SEPM. This is embedded DB, mostly it is the same credentials as that of SEPM



  • 16.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 13, 2011 10:22 AM

    Is it possible to reset the password



  • 17.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 13, 2011 10:39 AM

    You can, when u have access to the sepm console

    the user ID is DBA

    password is your first time password what you used during the SEPM install.

    try that and let us know if u are able to connect



  • 18.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 13, 2011 02:32 PM

    I am not able to connect



  • 19.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 14, 2011 02:35 PM

    I am able to connect to ODBC now but able to log on to SEPM.

    When running the Support tool, I am getting the following errors

    1. No IIS web sites were found with a port matching that configured for the Symantec Endpoint Protection Manager. Check the report "Is the Symantec Endpoint Protection Manager using its configured ports?"

    2.

    Error No applications are using Tomcat's configured port of '8005' with a state of 'Listen'
    Error No applications are using Remote Console Logon's configured port of '9090' with a state of 'Listen'
    Error No applications are using Sybase's configured port of '2638' with a state of 'Listen'
    Error No SepM IIS virtual directories exist which are properly located in the directory E:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\. Check the report "Is Microsoft IIS correctly configured for Symantec Endpoint Protection Manager?"

    3.

    Name:  Symantec Endpoint Protection Manager
    Type:  Service
    Depends on:  World Wide Web Publishing
    Status Setting Default Actual
    Error State Running Stopped


  • 20.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 15, 2011 09:04 PM

    sorry, ODBC is connected but not able to log on to SEPM. From the support tool, I am getting the errors mentioned in the previous post



  • 21.  RE: Unable to login to Symantec Endpoint Protection Manager

    Broadcom Employee
    Posted Oct 15, 2011 11:02 PM

    looks like the SEPM DB services are not found to be running on the port. is there any port conflicts?

    can you post the scm-server-0.log?



  • 22.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 09:55 AM

    Hi,

    After reading whole thread, best way to resolve the issue is to reconfigure the SEPM console with your database.

    Try and let us know the result.

    Regards

    Neeraj 



  • 23.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 10:42 AM
      |   view attached

    I have attached scm-server-0 log

    Attachment(s)

    txt
    scm-server-0_33.txt   136 KB 1 version


  • 24.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 11:07 AM


  • 25.  RE: Unable to login to Symantec Endpoint Protection Manager

    Broadcom Employee
    Posted Oct 17, 2011 11:07 AM

    there is error

    "2011-10-17 08:31:47.187 SEVERE: Unknown Exception
    org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect)"

    can you check the application event viewer logs for asa and post it here.

    There is one case on the forum with the same error message and issue been fixed, may be it gives some hint.

    https://www-secure.symantec.com/connect/forums/sep-management-console-and-services-not-working#comment-3802201



  • 26.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 02:47 PM
      |   view attached

    I reconfigured using Management Server Configuration Wizard.  Now I could see Ports 8005 and 9090 are active

    Active Connections

      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1832
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       760
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:1025           0.0.0.0:0              LISTENING       516
      TCP    0.0.0.0:1028           0.0.0.0:0              LISTENING       1832
      TCP    0.0.0.0:1029           0.0.0.0:0              LISTENING       1832
      TCP    0.0.0.0:1041           0.0.0.0:0              LISTENING       1832
      TCP    0.0.0.0:2301           0.0.0.0:0              LISTENING       2600
      TCP    0.0.0.0:2381           0.0.0.0:0              LISTENING       2600
      TCP    0.0.0.0:2638           0.0.0.0:0              LISTENING       3356
      TCP    0.0.0.0:2639           0.0.0.0:0              LISTENING       6984
      TCP    0.0.0.0:2730           0.0.0.0:0              LISTENING       7088
      TCP    0.0.0.0:2736           0.0.0.0:0              LISTENING       7336
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       4988
      TCP    0.0.0.0:5555           0.0.0.0:0              LISTENING       1964
      TCP    0.0.0.0:5800           0.0.0.0:0              LISTENING       2464
      TCP    0.0.0.0:5900           0.0.0.0:0              LISTENING       2464
      TCP    0.0.0.0:8005           0.0.0.0:0              LISTENING       7088
      TCP    0.0.0.0:8045           0.0.0.0:0              LISTENING       7088
      TCP    0.0.0.0:8530           0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:8531           0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:9090           0.0.0.0:0              LISTENING       7088
      TCP    127.0.0.1:80           127.0.0.1:2720         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2724         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2727         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2731         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2732         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2734         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2737         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2741         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2743         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2745         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2753         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2760         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2762         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2764         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2767         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2771         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2773         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2785         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2787         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2795         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2801         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2804         TIME_WAIT       0
      TCP    127.0.0.1:80           127.0.0.1:2806         TIME_WAIT       0
      TCP    127.0.0.1:1071         0.0.0.0:0              LISTENING       5404
      TCP    127.0.0.1:2639         127.0.0.1:2721         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2723         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2728         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2729         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2754         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2757         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2774         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2775         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2776         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2777         ESTABLISHED     6984
      TCP    127.0.0.1:2639         127.0.0.1:2778         ESTABLISHED     6984
      TCP    127.0.0.1:2721         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2722         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2723         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2726         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2728         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2729         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2733         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2742         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2752         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2754         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2757         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2759         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2763         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2766         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2772         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2774         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2775         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2776         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2777         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2778         127.0.0.1:2639         ESTABLISHED     7088
      TCP    127.0.0.1:2784         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2794         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2800         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:2805         127.0.0.1:2639         TIME_WAIT       0
      TCP    127.0.0.1:5152         0.0.0.0:0              LISTENING       1852
      TCP    127.0.0.1:5152         127.0.0.1:2974         CLOSE_WAIT      1852
      TCP    127.0.0.1:8005         0.0.0.0:0              LISTENING       7088
      TCP    127.0.0.1:9090         127.0.0.1:2735         TIME_WAIT       0
      TCP    172.16.8.32:80         10.36.34.105:3170      ESTABLISHED     4
      TCP    172.16.8.32:80         172.16.8.32:2780       ESTABLISHED     4
      TCP    172.16.8.32:80         172.16.13.77:2885      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.13.77:2886      TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.14.220:1559     ESTABLISHED     4
      TCP    172.16.8.32:80         172.16.32.178:3580     TIME_WAIT       0
      TCP    172.16.8.32:80         172.16.32.178:3581     TIME_WAIT       0
      TCP    172.16.8.32:139        0.0.0.0:0              LISTENING       4
      TCP    172.16.8.32:1383       172.16.8.115:389       CLOSE_WAIT      1832
      TCP    172.16.8.32:1764       172.16.8.32:2736       ESTABLISHED     7088
      TCP    172.16.8.32:2709       172.16.8.103:135       TIME_WAIT       0
      TCP    172.16.8.32:2710       172.16.8.103:1026      TIME_WAIT       0
      TCP    172.16.8.32:2715       172.16.14.23:139       ESTABLISHED     4
      TCP    172.16.8.32:2730       172.16.8.32:2739       ESTABLISHED     7088
      TCP    172.16.8.32:2736       172.16.8.32:1764       ESTABLISHED     7336
      TCP    172.16.8.32:2739       172.16.8.32:2730       ESTABLISHED     7336
      TCP    172.16.8.32:2758       192.168.79.3:25        TIME_WAIT       0
      TCP    172.16.8.32:2779       192.168.79.3:25        TIME_WAIT       0
      TCP    172.16.8.32:2780       172.16.8.32:80         ESTABLISHED     2540
      TCP    172.16.8.32:2781       172.16.8.32:8530       ESTABLISHED     2540
      TCP    172.16.8.32:2782       172.16.8.32:8530       TIME_WAIT       0
      TCP    172.16.8.32:2803       192.168.79.3:25        TIME_WAIT       0
      TCP    172.16.8.32:3389       172.16.10.143:59137    ESTABLISHED     4988
      TCP    172.16.8.32:4177       208.19.38.40:80        CLOSE_WAIT      1376
      TCP    172.16.8.32:8530       172.16.8.32:2781       ESTABLISHED     4
      TCP    172.16.8.32:8530       172.16.10.191:1025     ESTABLISHED     4
      TCP    172.16.8.32:8530       172.16.10.212:4430     ESTABLISHED     4
      TCP    172.16.8.104:25        172.16.9.54:1039       TIME_WAIT       0
      TCP    172.16.8.104:25        172.16.9.54:1040       TIME_WAIT       0
      TCP    172.16.8.104:25        172.16.9.54:1041       TIME_WAIT       0
      TCP    172.16.8.104:80        10.25.80.196:3521      TIME_WAIT       0
      TCP    172.16.8.104:80        10.25.80.196:3522      ESTABLISHED     4
      TCP    172.16.8.104:80        172.16.9.218:1433      ESTABLISHED     4
      TCP    172.16.8.104:80        172.16.10.163:2331     ESTABLISHED     4
      TCP    172.16.8.104:80        172.16.14.54:3013      ESTABLISHED     4
      TCP    172.16.8.104:80        172.16.24.109:1825     TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.24.155:1502     TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.24.155:1503     TIME_WAIT       0
      TCP    172.16.8.104:80        172.16.24.155:1504     TIME_WAIT       0
      UDP    0.0.0.0:161            *:*                                    2232
      UDP    0.0.0.0:162            *:*                                    2252
      UDP    0.0.0.0:445            *:*                                    4
      UDP    0.0.0.0:500            *:*                                    516
      UDP    0.0.0.0:1031           *:*                                    2232
      UDP    0.0.0.0:1812           *:*                                    4728
      UDP    0.0.0.0:3456           *:*                                    1832
      UDP    0.0.0.0:4500           *:*                                    516
      UDP    127.0.0.1:123          *:*                                    936
      UDP    127.0.0.1:1068         *:*                                    876
      UDP    127.0.0.1:1333         *:*                                    516
      UDP    127.0.0.1:1350         *:*                                    2636
      UDP    127.0.0.1:1382         *:*                                    1832
      UDP    127.0.0.1:2638         *:*                                    3356
      UDP    127.0.0.1:3198         *:*                                    456
      UDP    127.0.0.1:3456         *:*                                    1832
      UDP    127.0.0.1:4010         *:*                                    1424
      UDP    172.16.8.32:123        *:*                                    936
      UDP    172.16.8.32:137        *:*                                    4
      UDP    172.16.8.32:138        *:*                                    4
      UDP    172.16.8.32:2638       *:*                                    3356
      UDP    172.16.8.104:123       *:*                                    936
      UDP    172.16.8.104:2638      *:*                                    3356

     

    I am not sure whether I have given the correct path for the server data folder

    I gave server data folder path as

    E:\Program Files\Symantec\Symantec Endpoint Protection Manager\data



  • 27.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 03:27 PM

    Was your SEPm installed on E drive earlier ? if yes then its correct.

    Was your SEPM on port 80 earlier. Or is it now on port 80 and earlier it was on 8014.

    Check conf.properties

    for the line scm.iis.http.port=8014

     

    \Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties

    open with notepad.



  • 28.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 03:57 PM

    Yes, SEPM was installed in E drive

    Here is conf.Properties

    #Mon Oct 17 14:42:52 EDT 2011
    scm.server.version=11.0.6200.754
    scm.externallog.retryinterval=1000
    scm.timer.lu_delta=2
    scm.server.type=master
    scm.db.client.bin=E\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\ASA\\win32
    scm.timer.agentstatus=60
    scm.timer.activedirectory=86400
    scm.guplistmaxbackofftime.seconds=1800
    scm.companysize=0
    scm.timer.logcollection=20
    scm.liveupdateclient.path=C\:\\Program Files\\Symantec\\LiveUpdate
    scm.agent.root=E\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\data
    scm.server.port=8005
    scm.schema.version.pre-upgrade=11.0.6.0
    scm.iis.http.defaultsite=1
    scm.timer.iiscache=10
    scm.agent.groupcreation=false
    scm.db.datasource=jdbc/metadatabase
    scm.agent.kcs=A9259ED1A4AE2927E8CBB3F33EC9948E
    scm.externallog.retrycount=30
    scm.timer.appcollection=20
    scm.timer.packagebuilder=60
    scm.http.port=9090
    scm.extlog.deli=,
    scm.server.backup=E\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\Server Private Key Backup\\
    scm.console.log=true
    scm.guplistupdatefrequency.seconds=60 



  • 29.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 04:36 PM

    So SEPM was installed on port 80,

    Now go to IIS Manager -Websites- go to the properties of the website where SEPM is installed (content,client package,secrs,secreg etc) and make sure the port listed over there is 80 as well.



  • 30.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 04:56 PM
      |   view attached

    Yes, It is installed on port 80



  • 31.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 05:05 PM

    try running upgrade.bat once

    Program Files\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat



  • 32.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 08:07 PM

    I upgraded SEPM and tried to login with Username, Password and Local host:8005

    But I am not able to log in



  • 33.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 17, 2011 08:08 PM

    I am getting the Error as "Unexpected Server Error"



  • 34.  RE: Unable to login to Symantec Endpoint Protection Manager

    Broadcom Employee
    Posted Oct 17, 2011 09:53 PM

    is the DB service started?

    pass on the scm-server-0.log



  • 35.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 18, 2011 08:32 AM
      |   view attached

    Yes, The DB service started. Attached scm-server-0 log

    Attachment(s)

    txt
    scm-server-0_34.txt   9.21 MB 1 version


  • 36.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 18, 2011 09:30 AM

    Test the ODBC connection now



  • 37.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 18, 2011 09:34 AM

    Not sure why is your SEPm using SSL Secure Handshake

     

    javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake


  • 38.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 18, 2011 09:35 AM

    I tested ODBC connection. It is getting connected



  • 39.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Oct 21, 2011 09:32 AM

    I am not able to log on to the SEPM still.

    While running the support tool I am getting the following errors

    1. Microsoft IIS is Symantec Endpoint Protection Managercorrectly configured for not
    Some or all of the Microsoft IIS configurations are not correct
     

    2. The Symantec Endpoint Protection Manager is not using its configured ports
    Some or all of the ports are not configured correctly
     



  • 40.  RE: Unable to login to Symantec Endpoint Protection Manager

    Posted Dec 19, 2011 06:46 AM

    I AM USING SEPM 11.0 ...

    I UNABLE TO START SEPM SERVICE.................

     

    BUT SYMANTEC EMBEDDED DB SERVICE IS RUNNING ......

     

    HOW TO START SEPM SERVICE..

    KINDLY SHARE SOLUTIONS

    REGARDS

    KARTHICK