Endpoint Protection

 View Only
Expand all | Collapse all

Failed to Connect to the Server

Migration User

Migration UserApr 01, 2010 12:19 PM

Migration User

Migration UserApr 01, 2010 02:44 PM

Migration User

Migration UserApr 01, 2010 02:51 PM

Migration User

Migration UserApr 02, 2010 10:27 AM

Migration User

Migration UserApr 02, 2010 10:48 AM

Migration User

Migration UserApr 02, 2010 11:12 AM

  • 1.  Failed to Connect to the Server

    Posted Mar 26, 2010 03:43 PM

    Hello all,

    I followed Symantec Disaster Recovery link:
    http://service1.symantec.com/support/ent-security.nsf/docid/2008081906512748?Open&seg=ent

    And after restoring the database, jks file, and reconfuring the server successfully, when i try logging into the console it says failed to connect to server and the SEPM service stops after one incorrect login.

    JohnD


  • 2.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 03:47 PM

    Please run the Mangement server configuration wizrad .


  • 3.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 03:49 PM
    post the scm-server-0 logs..
    And was your sepm earlier installed on port 8014 or port 80 ?

    as now when you would have re-installed it wud have installed on port 8014.




  • 4.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 04:22 PM
    2010-03-26 16:14:18.223 SEVERE: ================== Server Environment ===================
    2010-03-26 16:14:18.224 SEVERE: os.name = Windows Server 2008
    2010-03-26 16:14:18.225 SEVERE: os.version = 6.1
    2010-03-26 16:14:18.225 SEVERE: os.arch = x86
    2010-03-26 16:14:18.225 SEVERE: java.version = 1.6.0_14
    2010-03-26 16:14:18.225 SEVERE: java.vendor = Sun Microsystems Inc.
    2010-03-26 16:14:18.226 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2010-03-26 16:14:18.226 SEVERE: java.vm.version = 14.0-b16
    2010-03-26 16:14:18.226 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2010-03-26 16:14:18.227 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2010-03-26 16:14:18.227 SEVERE: java.user = null
    2010-03-26 16:14:18.227 SEVERE: user.language = en
    2010-03-26 16:14:18.228 SEVERE: user.country = US
    2010-03-26 16:14:18.228 SEVERE: scm.server.version = 11.0.5002.333
    2010-03-26 16:14:22.875 SEVERE: ================== StartClientTransport ===================
    2010-03-26 16:14:23.991 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
    java.net.ConnectException: Connection refused: 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.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:519)
     at java.net.Socket.connect(Socket.java:469)
     at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
     at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
     at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
     at sun.net.www.http.HttpClient.<init>(HttpClient.java:233)
     at sun.net.www.http.HttpClient.New(HttpClient.java:306)
     at sun.net.www.http.HttpClient.New(HttpClient.java:323)
     at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:852)
     at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:793)
     at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:718)
     at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1041)
     at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
     at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:612)
     at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:147)
     at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:106)
     at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:880)
     at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:768)
     at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3484)
     at org.apache.catalina.core.StandardContext.start(StandardContext.java:3710)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
     at org.apache.catalina.core.StandardHost.start(StandardHost.java:697)
     at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1148)
     at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:311)
     at org.apache.catalina.core.StandardService.start(StandardService.java:450)
     at org.apache.catalina.core.StandardServer.start(StandardServer.java:2213)
     at org.apache.catalina.startup.Catalina.start(Catalina.java:484)
     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:597)
     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
    com.sygate.scm.common.communicate.CommunicationException: Failed to connect to the server.


  • 5.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 04:27 PM
    Go to 
    Program files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\conf.properties ( open with notepad )
    and check what is the value of scm.iis.http.port=xxxx ?

    Have re-stored the database on the same server ?


  • 6.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 04:34 PM

    scm.iis.http.port=8014
    No, it is different server.

    JohnD



  • 7.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 04:38 PM
    so you mean to say you backed up database on serverA and you are restoring it on serverB with diffrent name and IP ??

    it will not work..

    For moving to new server you need to follow this

    If you dont have replication in place

    How do I move Symantec Endpoint Protection Manager from one server to another with a different IP address and host name?

    http://service1.symantec.com/support/ent-security.nsf/docid/2008031204405448

    Here you will not loose clients or anythng in database..but you cannot do a replication..

     

    Or you can for a option B 
    Where you can Install a fresh manager on New Server run sylinkreplacer to connect back all the clients to the new server

    http://www.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm



  • 8.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 04:42 PM
    I'm restoring to same IP same hostname just different hardware.

    JohnD


  • 9.  RE: Failed to Connect to the Server

    Posted Mar 26, 2010 05:21 PM
    Did you ran the Mangement server configuration wizrad  after the restore??


  • 10.  RE: Failed to Connect to the Server

    Posted Mar 27, 2010 01:26 AM
    Do as follows
    Restore the database
    Copy server.xml ( \Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\conf) and keystore.jks from (\Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\etc )  from ols server to new server run the management server configuration wizard and try to login..


  • 11.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 11:23 AM

    I follows the manual uninstall article: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101615023748
    Because when I tried uninstalling normal way it would not allow me too. This is the error:



  • 12.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 11:38 AM
    use the tool wholock me, it will tell you who is locking it, should be IIS i guess.
    http://www.dr-hoiby.com/WhoLockMe/


  • 13.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 11:49 AM

    This tool does not work on Win2008.
    I think the probably is the uninstall left some registry keys which have no owner/permissions set on them with a broken sid and it will not allow me to take permission on it so i can delete them.


  • 14.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 11:55 AM
    Can you check where its stopping using this tool
    http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
    p
    ut a filter for msiexec.exe when the error pops up , check the registry path 


  • 15.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 12:14 PM
    I'm not sure if this might be part of the problem but Symantec Endpoint Protection Manager service is still listed in services however when i click on it it says cannot find the path and no description is available.


  • 16.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 12:18 PM
    seems like its marked for deletion, reboot the box onces should fix it


  • 17.  RE: Failed to Connect to the Server

    Posted Mar 29, 2010 12:41 PM
    Reboot seemed to have removed the service however still recieving that error^. I think its best if i just reformat.


  • 18.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 11:54 AM

    Hello,

    I tried restoring the DB and then copying the server.xl and the keystore.jks files and running the reconfigure server wizard again however i still getting the java -1 error in the event view and unable to login to the console the symantec manager service stops after incorrect try. It seems like IIS as i'm to bring up the web console however still cannot login and same thing happens. Anyone know what can be the issue here?

    Thanks.


  • 19.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 12:09 PM
    scm-server-0.log:

    2010-04-01 12:03:48.507 SEVERE: ================== Server Environment ===================
    2010-04-01 12:03:48.508 SEVERE: os.name = Windows Server 2008
    2010-04-01 12:03:48.509 SEVERE: os.version = 6.1
    2010-04-01 12:03:48.509 SEVERE: os.arch = x86
    2010-04-01 12:03:48.509 SEVERE: java.version = 1.6.0_14
    2010-04-01 12:03:48.518 SEVERE: java.vendor = Sun Microsystems Inc.
    2010-04-01 12:03:48.518 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2010-04-01 12:03:48.518 SEVERE: java.vm.version = 14.0-b16
    2010-04-01 12:03:48.519 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2010-04-01 12:03:48.519 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2010-04-01 12:03:48.519 SEVERE: java.user = null
    2010-04-01 12:03:48.520 SEVERE: user.language = en
    2010-04-01 12:03:48.520 SEVERE: user.country = US
    2010-04-01 12:03:48.520 SEVERE: scm.server.version = 11.0.5002.333
    2010-04-01 12:03:48.553 INFO: Server startup
    2010-04-01 12:03:49.795 FINE: updProcessState: checking...
    2010-04-01 12:03:49.797 FINE: updProcessState: The process status has been checked.
    2010-04-01 12:03:49.798 FINE: updProcessState: checking...
    2010-04-01 12:03:49.800 FINE: updProcessState: The process status has been checked.
    2010-04-01 12:03:51.328 INFO: use transport url:http://localhost:8014/secars/secars.dll
    2010-04-01 12:03:51.328 SEVERE: ================== StartClientTransport ===================
    2010-04-01 12:03:51.835 FINE: Task scheduled
    2010-04-01 12:03:51.836 SEVERE: Schedule is started!
    2010-04-01 12:03:53.053 WARNING: Log property file does not exist.
    2010-04-01 12:03:53.652 FINE: Test db connection successfully.
    2010-04-01 12:03:57.871 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {ECCC5006-EF61-4c99-829A-417B6C6AD963}, sequenceNum= 2008021700
    2010-04-01 12:03:57.871 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {EA960B33-2196-4d53-8AC4-D5043A5B6F9B}, sequenceNum= 80820001
    2010-04-01 12:03:57.871 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E5A3EBEE-D580-421e-86DF-54C0B3739522}, sequenceNum= 100309020
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E5A3EBEE-D580-421e-86DF-54C0B3739522}, sequenceNum= 100308020
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E1A6B4FF-6873-4200-B6F6-04C13BF38CF3}, sequenceNum= 100309020
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E1A6B4FF-6873-4200-B6F6-04C13BF38CF3}, sequenceNum= 100308020
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {DB206823-FFD2-440a-9B89-CCFD45F3F1CD}, sequenceNum= 80820001
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {D3769926-05B7-4ad1-9DCF-23051EEE78E3}, sequenceNum= 100301001
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {D3769926-05B7-4ad1-9DCF-23051EEE78E3}, sequenceNum= 91231021
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {CC40C428-1830-44ef-B8B2-920A0B761793}, sequenceNum= 100309020
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {CC40C428-1830-44ef-B8B2-920A0B761793}, sequenceNum= 100308020
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100401002
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100324037
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100324022
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100324002
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100323041
    2010-04-01 12:03:57.872 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100323033
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100323002
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100322040
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100322023
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100322004
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100321020
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100321004
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100320022
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100320004
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100319041
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100319023
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100319003
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100318040
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100318034
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100318016
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100317051
    2010-04-01 12:03:57.873 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100317021
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100316003
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100315040
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100315022
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100315003
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100314003
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100313021
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100313002
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100312037
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100312022
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100312003
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100311036
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100311021
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100311002
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100310037
    2010-04-01 12:03:57.874 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100310022
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100310002
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100309048
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100309032
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100309009
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 100308057
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C25CEA47-63E5-447b-8D95-C79CAE13FF79}, sequenceNum= 80929016
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C13726A9-8DF7-4583-9B39-105B7EBD55E2}, sequenceNum= 80820001
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {812CD25E-1049-4086-9DDD-A4FAE649FBDF}, sequenceNum= 100309020
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {812CD25E-1049-4086-9DDD-A4FAE649FBDF}, sequenceNum= 100308020
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {4F889C4A-784D-40de-8539-6A29BAA43139}, sequenceNum= 91111048
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {42B17E5E-4E9D-4157-88CB-966FB4985928}, sequenceNum= 100301001
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {42B17E5E-4E9D-4157-88CB-966FB4985928}, sequenceNum= 91231021
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100401002
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100324037
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100324022
    2010-04-01 12:03:57.875 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100324002
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100323041
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100323033
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100323002
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100322040
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100322023
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100322004
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100321020
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100321004
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100320022
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100320004
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100319041
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100319023
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100319003
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100318040
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100318034
    2010-04-01 12:03:57.876 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100318016
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100317051
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100317021
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100316003
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100315040
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100315022
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100315003
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100314003
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100313021
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100313002
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100312037
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100312022
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100312003
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100311036
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100311021
    2010-04-01 12:03:57.877 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100311002
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100310037
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100310022
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100310002
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100309048
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100309032
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100309009
    2010-04-01 12:03:57.878 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 100308057
    2010-04-01 12:04:03.321 FINE: Test db connection successfully.
    2010-04-01 12:04:13.321 FINE: Test db connection successfully.
    2010-04-01 12:04:19.589 INFO: PackageTask deployed fileCheckSum: fcb6f026b4c552dc83beee5fcc739ded
    2010-04-01 12:04:19.607 INFO: PackageTask deployed fileCheckSum: fcb6f026b4c552dc83beee5fcc739ded
    2010-04-01 12:04:20.157 INFO: PackageTask.publishGroup(): cmd= "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\sempub.exe" "-group" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\60379BA0A1D9E9A800E671F159B300EA" "0DD6E0092D31CCE9B587A0967DE9B6B8" "8136EC25A1D9E9A800663D106674DB6D" "5EF4053CA1D9E9A80110E7E5FED9029A" "8014" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager"
    2010-04-01 12:04:20.307 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
    2010-04-01 12:04:20.307 INFO: PackageTask.publishGroup(): success
    2010-04-01 12:04:20.526 INFO: PackageTask.publishGroup(): cmd= "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\sempub.exe" "-group" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\46944DF7A1D9E9A800F4AF1E697D5AFC" "0DD6E0092D31CCE9B587A0967DE9B6B8" "8136EC25A1D9E9A800663D106674DB6D" "5EF4053CA1D9E9A80110E7E5FED9029A" "8014" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager"
    2010-04-01 12:04:20.658 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
    2010-04-01 12:04:20.658 INFO: PackageTask.publishGroup(): success
    2010-04-01 12:04:21.006 INFO: PackageTask.publishGroup(): cmd= "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\sempub.exe" "-group" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\7FF6F80DA1D9E9A800A956AD400453AF" "0DD6E0092D31CCE9B587A0967DE9B6B8" "8136EC25A1D9E9A800663D106674DB6D" "5EF4053CA1D9E9A80110E7E5FED9029A" "8014" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager"
    2010-04-01 12:04:21.145 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
    2010-04-01 12:04:21.145 INFO: PackageTask.publishGroup(): success
    2010-04-01 12:04:21.382 INFO: PackageTask.publishGroup(): cmd= "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\bin\sempub.exe" "-group" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\06EF08DDA1D9E9A800B83842A6033108" "0DD6E0092D31CCE9B587A0967DE9B6B8" "8136EC25A1D9E9A800663D106674DB6D" "5EF4053CA1D9E9A80110E7E5FED9029A" "8014" "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager"
    2010-04-01 12:04:21.509 INFO: PackageTask.publishGroup(): returnCode = 0(Unknown Error Code) errBuf = success
    2010-04-01 12:04:21.509 INFO: PackageTask.publishGroup(): success
    2010-04-01 12:04:21.683 INFO: LoginHandler->doLogin: version from database: 11.0.3.0
    2010-04-01 12:04:21.683 INFO: LoginHandler->doLogin: version from server: 11.0.3.0
    2010-04-01 12:04:21.688 INFO: LoginHandler->doLogin: version from template: 11.0.3.0
    2010-04-01 12:04:21.705 SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.RequestHandler
    com.sygate.scm.server.util.ScmServerError: Can't read local server from database!
        at com.sygate.scm.server.consolemanager.AdminAuthenticator.authenticate(AdminAuthenticator.java:134)
        at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.doLogin(LoginHandler.java:161)
        at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.getCredential(LoginHandler.java:119)
        at com.sygate.scm.server.consolemanager.requesthandler.LoginHandler.handleRequest(LoginHandler.java:50)
        at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:114)
        at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:78)
        at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:79)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:638)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:720)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:145)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:139)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:198)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2460)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:119)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
        at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
        at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
        at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:955)
        at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:157)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
        at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
        at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
        at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
        at java.lang.Thread.run(Thread.java:619)
    2010-04-01 12:04:21.711 SEVERE: Shuting down server ...




  • 20.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 12:13 PM
    Are you using the embedded database, or SQL? Could you run an ODBC test to verify the connection?

    For the embedded database:

    Administrative Tools>Data Sources

    System DSN>Configure SymantecEndpointSecurityDSN

    Select the Login tab, enter the UserID DBA, and the SEP database password (should be the same as the SEPM login password)

    Select the Database tab, enter the server name, enter the database name - sem5

    Select the Network Tab, ensure TCP/IP is checked, enter the IP of the SEPM server

    Select the ODBC tab, and test connection



  • 21.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 12:15 PM
    If ODBC passes, could you run the SEP support tool, select Pre-installation check, and SEPM options, and post the collect full data for support?


  • 22.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 12:19 PM
    I'm using SQL not embedded database.

    Thanks.


  • 23.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 01:01 PM
    Still verify the ODBC.

    Check the System DSN configuration lists the correct SQL instance, then walk through the configuration and test the connection.

    As before, if it passes, run the SEP Support Tool and post.


  • 24.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 01:27 PM
    If there are no sources listed, there is no connection to the database.  Run the Management Server Configuration Wizard to attempt to establish the connection.


  • 25.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 01:39 PM
    Okay this very wierd but I just noticed all the clients are showing online with the management server now even though I cannot login to the console still, everytime i try the SEPM service stops. And in the event log i see: The Java Virtual Machine has exited with a code of -1, the service is being stopped.
    I did notice this information event also maybe related? : Login failed for user 'Domain\Username'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

    This would seem to suggest the database and clients can connect fine, but i still cant login to the console.

    Thanks.


  • 26.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 01:52 PM
    This error is showing in SQL 2008 log also:
    Login failed for user 'Domain\Username'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]

    The Domain\Username was the account I used for SEPM database.

    Thanks.


  • 27.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:25 PM

    The ODBC connection passed the reason it was not showing was i'm running on 64-bit which shows only if you run odbcad32.exe in C:\windows\syswow64 directory.
    This is the result:

    Microsoft SQL Server ODBC Driver Version 06.01.7600

    Running connectivity tests...

    Attempting connection
    Connection established
    Verifying option settings
    Disconnecting from server

    TESTS COMPLETED SUCCESSFULLY!


  • 28.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:32 PM
    When i run the ODBC test using SQL server authentication and Login ID: DBA and password same as the console password the test failed with error: Connection Failed
    SQLState: 28000 SQL Server Error: 18456 Login failed for user DBA. The test will pass however If i use with windows NT authentication using the network login ID

    Thanks,


  • 29.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:37 PM
    In IIS, in the default app pool advanced settings, what is 'Enable 32-bit Applications' set to?  Set to False if it is not, cycle IIS, and attempt to start the SEPM Service.

    Otherwise, could you post both the scm-server-0.log located in \Program Files(x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\logs, and the HTTP error logs \Windows\System32\LogFiles\HTTPERR.


  • 30.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:37 PM
    I notice this error in the SQL logs as well: Login failed for user 'DBA'. Reason: An attempt to login using SQL authentication failed. Server is configured for Windows authentication only


  • 31.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:42 PM
    If you use the windows NT authentication and get it to pass, are you able to start the manager service and log in?  Start the services, wait a few seconds then refresh to see if it stays started.


  • 32.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:43 PM

    The manager service is started right now, but everytime i try to login it fails and the service stops.


  • 33.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:44 PM
    The scm log didn't post, try to upload it.


  • 34.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:48 PM
    The service is probably stopping a few seconds after you start it, this what is preventing you from logging in.

    Did you check the default app pool setting in IIS?


  • 35.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 02:51 PM

    Yes default app pool setting is set to False


  • 36.  RE: Failed to Connect to the Server

    Posted Apr 01, 2010 09:13 PM
    Can you also post the catilina.out file on this thread. and also check what port you are using during the logon to the SEPM console. i.e loclhost:8443


  • 37.  RE: Failed to Connect to the Server

    Posted Apr 02, 2010 10:27 AM



  • 38.  RE: Failed to Connect to the Server

    Posted Apr 02, 2010 10:48 AM
      |   view attached
    Console says: localhost:8443

    Attachment(s)

    docx
    CatalinaOut.docx   13 KB 1 version


  • 39.  RE: Failed to Connect to the Server

    Posted Apr 02, 2010 11:11 AM
    Their are no ODBC sources listed under User or System DNS.
    And the SEP tool ran with no problems attached is full report.

    Thanks.



  • 40.  RE: Failed to Connect to the Server

    Posted Apr 02, 2010 11:12 AM
      |   view attached

    Attachment(s)

    zip
    scm-server-0_3.zip   4 KB 1 version