HP,Altiris Group

Hey Folk... 

I'm unable to logon onto the Endpoint Management Console following my initial install of the product.  I continuiously recieve a...

ERROR:

Failure to connect to the server.

Make sure the the server is running and your session has not timed out.

If you can reach the server but cannot log on, make sure that you provided the correct parameters.

If you are experiencing network issues, contact you system administrator.

 

The server is running (cause I'm on it locally), I'm providing the correct parameters (cause i made up the password myself for the console admin account), and lastly; I'm not experiencing any network issues (once again, I'm doing this install locally).

I'm using port 80 for the IIS interface.  I've even tried using 8080 (same result).

 

Any help with this issue, of course, would be greatly appreciated.

Hi,

Management connection should use TCP 8443 as default, not 80 or 8080 as far as I understand.

- Jukka

Been there done that...  same result. :(

Hmm, interesting.  Now, I apologize in advance for not jumping to conclusions, but are you using the "Web Interface" or the "SEPM Console" to login to the servers interface?

Also, you are aware that there is a Batch file that you can use to change the "admin password".

Lastly, are you like me, and is it possile that you changed the default admin name?  So when you are logging in, it is not using "admin" but maybe a different name (probably case sensitive)? 

* * * * * *

When you say locally, are you physically locally or are you in an RDP session??  I have heard of problems in the past with regards to RDP sessions... 

* * * * * *

You did not mention the OS your SEPM is installed on...  sorry for the bunch of question, but the more info you give, the easier it is for us to help.

Thanks.  Cheers.

I'm glad to answer questions...

The SEPM is installed on Server 2003...  I'm using the SEPM console as the login point...  I'm physically at the server performing these interfaces (no RDP session)

I have not tried a different name for the default "admin" account.  I left it as "admin" and just created a password for it.

I did not not know about the batch file...  Where can I locate it?

Thanks very much...

1. Open Windows Explorer on the computer where you run Symantec Endpoint Protection Manager.
2. Change directory to the <Drive>:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools folder.
3. Double-click the Resetpass.bat executable file. The password is reset to the default password.
4. Be sure to change the password immediately.

Note: If you change the admin account name to something other than admin and then subsequently run resetpass.bat, it changes the account name back to admin.

HI,

Did you change setting in SEPM/IIS port?

check for the event id in the application event id. I guess you might be facing 4096 issue, check the KB of symantec and see if that helps to resolve the issue.

B.T.W is SEPm and DB service started, if yes can you check running the management server onfiguration again and see if it fixes the issue.

This not creedntials issue, if it was it throws different error.

 

Pete!

Hi,

I experienced the same problems when using a SQL server database that was not on the SEPM. It turned out that I had to install teh SQL Server 2005 client tools on the SEPM even when there was no database physically on the SEPM.

Also notice that SEPM accounts are case-sensitive.

Erik

 

 

This is the catlina.out log

Mar 9, 2009 8:24:23 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-9090
Mar 9, 2009 8:24:24 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8443
Starting service SCM
Apache Tomcat/4.1.37-LE-jdk1.4
Has valid SAV license
Info>> No SNAC license file in D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: ================== Server Environment ===================
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: os.name = Windows 2003
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: os.version = 5.2
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: os.arch = x86
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.version = 1.5.0_14
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.vendor = Sun Microsystems Inc.
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.vm.name = Java HotSpot(TM) Server VM
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.vm.version = 1.5.0_14-b03
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.home = D:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: catalina.home = D:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: java.user = null
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: user.language = en
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: user.country = US
Mar 9, 2009 8:24:25 PM com.sygate.scm.server.util.ServerLogger writeHeader
SEVERE: scm.server.version = 11.0.2000.1567

Please someone help

Hi Dodixon3, I have same issue yesterday, you done all things right like me. There is no issue with your username and password. So don’t reset the password. Root cause of the problem is database and the server ports are in use. Just let me know which kind of database server you are using? Embedded/ SQL? To solve your problem: 1) Change the database port to 2639 2) Change the server port to 8445 Feel free to contact me, if you don’t know how to change the port. This will solved your problem. You might have to change settings in multiple files/registry entries.

Dodixon3,

The login issue you are facing in SEP Manager console is related to the ports, that the Tomcat communication uses. Another application is communicating on port 8005, which in turn causes the SEP manager to stop allowing logins, the SEP manager service stops working etc.

Here is the Solution:

The port number used by Tomcat can be changed by editing this file:

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\conf\server.xml

Changed the default value for the port from 8005 to 8006. Save this file and restart the Symantec Endpoint Protection Manager service.


This will resolve all issues.


Hope this helps.

--WDS

HI Spicetech
                      how to change database port to 2639 and server port to 8445.

where to do it.

Hi Dodixon3,

Check the SEPM Service(SemSvc.exe)

The catalina.out you have posted does not show any port conflicts.  Catalina.out has errors only if there are any port conflicts.
Its usual size is 3 kb. It can not be opened if SEPM service has started. If there is a port conflict, its possible that in Event Viewer, you may receive a Java 1 error instead of java -1.

Check that the SEPM service has stopped or started.

You should get some indication of errors in scm-server-0.log.   If you see an error like "connection refused", then you should check the ODBC connectivity.

If you see an error that has HTTP mentioned in it, you should check the IIS manager for configuration.

Cheers,
Aniket

Dear All,
                 I also faced this problem but got rid of it. I have Symmantec Manager on the Domain Controller on which ISA is also running. I configured SSL port 8443 after that I was unable to login. I contact several experts and also symmantec support team but got nothing. Suddenly I notice that what I had done before this and I got answer. Actually Symmantec Console use port 8443 which was used by the ISA also and not free that is why I was unable to Login. So everyone who is facing this problem first check that the port 8443 is free and not used by anyother application.
Thanks
Tauqeer Gul

According to me, it's very common error people are getting when they are trying to Login after installation complete. Check the port conflict first. Resolving port conflict solve most of the problems.