Endpoint Protection

After entering user name & password console showing "This may take Several seconds"  for long time. Client getting updates.

Hi are you using embedded database?

Do you have enough disk space on Root Drive and the Drive on which you have SEPM installed.
Make sure ODBC connects fine.
If still having issues connecting try posting the error you find in SCM-Server log
\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-o.log

 hi ajeet,
what operating system are you using? try to check the permission of the SEPM users in inetpub and wwwroot properties. They should have full permissions in there..

hi,
check for the scm-server-o.log for any errors, check by increasing the javaheapsize if it improves the situation.

Pete!

hi pete,
i got this issue when i installed the SEPM server on a windows SBS 2003 server, i also tried to increase the java heap size to 1 gb or even 2gb, but it didnt help me, when i ran the sep support tool it showed me that there are certain errors regarding the iis authentication..

okay,  that looks authentication issue. Ensure there is no deny to any of the account for the site. I/m intersted to know the scm-server-o.log message when you try to login, can you paste it here, may be expres would like to place comment on that .

Pete!

Dear Sir,

Go on the below location

Program Files\Symantec\Symantec Endpoint Protection Manager\tools

Reset the password

Check your Java and IIS, Which versions u r using of those?

Please provide additional info on the problem regarding the database used.. this could also be communication error with the database if external.

sry for the late response, SEPM  installed on Windows server 2000 SP4 with MS SQL server 2000. I checked ODBC datasource connectivity it's fine.
C: drive have 14GB free space. other informations i will post tomorrow.

Java version-1.5.0_15
SEPM- 11.0.2295

MS SQL SERVER 2000.

 

IN SCM-SERVER--1.LOG file- error code 0X80020000 showing

"ODBC data source test completed successfully" 

try changing the password for the default SEPM users that requires authentication.

i started resetpass.bat file, but same  problem

.jdb updation also not happening on the server.

in Event viewer
The MSSQL Server ADHelper service terminated withspecific error 3221225572  showing.

in services.msc MSSQL Server ADHelper service(sqladhlp.exe) not able to start.

Is this problem global to all users or just the user account you are using?
If the problem is user account specific and Since you already changed passwords, Please try to delete/define that specific user account. Just be sure that you still have an Admin user account to redifine the old one.

This problem is not user specific, another user a/c facing same problem

Please verify on the database that the user really exists, did u try logging in with the domain?

I checked in SQL database user alredy there, here is no any domain environment.

2009-04-25 09:33:32.578 SEVERE: ================== Server Environment ===================
2009-04-25 09:33:32.593 SEVERE: os.name = Windows 2000
2009-04-25 09:33:32.593 SEVERE: os.version = 5.0
2009-04-25 09:33:32.593 SEVERE: os.arch = x86
2009-04-25 09:33:32.593 SEVERE: java.version = 1.5.0_15
2009-04-25 09:33:32.593 SEVERE: java.vendor = Sun Microsystems Inc.
2009-04-25 09:33:32.593 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2009-04-25 09:33:32.593 SEVERE: java.vm.version = 1.5.0_15-b04
2009-04-25 09:33:32.593 SEVERE: java.home = D:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2009-04-25 09:33:32.593 SEVERE: catalina.home = D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
2009-04-25 09:33:32.593 SEVERE: java.user = null
2009-04-25 09:33:32.593 SEVERE: user.language = en
2009-04-25 09:33:32.593 SEVERE: user.country = US
2009-04-25 09:33:32.593 SEVERE: scm.server.version = 11.0.4014.26
2009-04-25 09:33:38.687 SEVERE: ================== StartClientTransport ===================
2009-04-25 09:33:40.171 SEVERE: Unknown Exception in: com.sygate.scm.server.servlet.StartupServlet
java.lang.Exception: HTTP 404 Object Not Found, URL: http://localhost/secars/secars.dll?action=34
at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:556)
at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:72)
at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:104)
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:585)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)
com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
at com.sygate.scm.common.communicate.Communicator.getRequestInputStream(Communicator.java:580)
at com.sygate.scm.server.util.ClientTransportHelper.startClientTransport(ClientTransportHelper.java:72)
at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:104)
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:585)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:151)

Can you remember what authentication did u use during the setup? Please also check the DNS, we need to make sure that the servers are communicating well.

SQL authentication i used, server communication is ok

Check the root Default Web Site had SSL enabled (for some of the other sites on this server). Please try disabling SSL on the Symantec sites. (just try)

Can you also double check on the link below; (I think this is somewhat related, not sure)

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

For the authentication, I was referring if you use domain or symantec authentication.

After repairing the SEPM it's running fine.
Thanks for your valuable suggestions.