can you post the scm-server.log?

Try this once

verify Distributed Component Object Model (DCOM) properties

1. Login as Local Administrator, On the Windows taskbar, click Start > Run.
2. Type the following, and then click OK:

   dcomcnfg

    

3. Do one of the following, depending on your operating system:
   
   • In Windows XP/2003, click Component Services > Computers > My Computer. Then right-click My Computer and click Properties.
   • In all other versions of Windows, go on to the next step.
4. On the Default Security or Default COM Security tab, under Default Access Permissions, click Edit Default.
5. Verify that Administrators, Interactive, and System accounts are set to Allow Access, and then clickOK.
6. Under Default Launch Permissions, click Edit Default.
7. Verify that the Administrators, Interactive, and System accounts are set to Allow Launch, and clickOK.
8. Do one of the following, depending on your operating system:
   
   • In Windows XP/2003, skip the two following steps.
   • In all other versions of Windows, go on to the next step.
9. In the Default Configuration Permissions section, click Edit Default.
10. In the Registry Key Permissions window, verify that the following are set to Full Control, and then click OK:

    CREATOR OWNER
    ...\Administrators
    SYSTEM

     

11. On the Default Properties tab, verify that Default Impersonation Level is set to Identify.
12. Click Apply, and then click OK.
13. Restart the computer for the changes to take effect.

Please post the scm-server log, typically located in the following location:

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\scm-server-0.log

Hi,

I have attached the scm-server logs.

can you try logging into administrator account instead of LDAP?

com.sygate.scm.server.util.ServerException: LDAP Authentication Failed [path=LDAP://172.18.131.162:389, user=MV43218].

Please check your user account "vtcarrick" once..

dont you have SEPM authentication account?

Have you checked for any errors within the logs of the SEPM's Apache server?  These are usually found in "%ProgramFiles%\Symantec\Symantec Endpoint Protection Manager\apache\logs"

The odd thing in your situation is that the SEPM is working.  This is usually not possible without the Webserver service running as well.  Can you confirm that the "Symantec Endpoint Protection Manager" service is defintiely started?

The only thing I can think of that might bring about this situation is if someone has deliberately started up the httpd.exe process in "%ProgramFiles%\Symantec\Symantec Endpoint Protection Manager\apache\bin" by other means.  Doing so would casue the process to bind to the SEPM's client communication port (8014 by default), and thus prevent the "Symantec Endpoint Protection Manager Webserver" service from starting.

You could try to verify this by running a netstat on the SEPM and see if anything is listening on 8014.  I'd also recommend using the -o switch with netstat so you can grab the PID and check task manager to find out under which context this process might be running (i.e. SYSTEM, or a specific user...)

Did you try by restarting the server?