Endpoint Protection

 View Only
Expand all | Collapse all

Unable to communicate with the reporting Component

Migration User

Migration UserOct 08, 2009 07:53 AM

  • 1.  Unable to communicate with the reporting Component

    Posted Oct 06, 2009 07:22 AM

    When i log into the symantec endpoint manager, i have getting this error (Unable to communicate with reporting component.Here is my symantec  tomcat log file.Please show me the way how to fix this problem. Right now i cannot see home,monitor,reports in the symantec endpoint console.

    2009-10-06 18:06:10.062 SEVERE: ================== Server Environment ===================
    2009-10-06 18:06:10.062 SEVERE: os.name = Windows XP
    2009-10-06 18:06:10.062 SEVERE: os.version = 5.1
    2009-10-06 18:06:10.062 SEVERE: os.arch = x86
    2009-10-06 18:06:10.062 SEVERE: java.version = 1.5.0_15
    2009-10-06 18:06:10.062 SEVERE: java.vendor = Sun Microsystems Inc.
    2009-10-06 18:06:10.062 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2009-10-06 18:06:10.062 SEVERE: java.vm.version = 1.5.0_15-b04
    2009-10-06 18:06:10.062 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2009-10-06 18:06:10.078 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2009-10-06 18:06:10.078 SEVERE: java.user = null
    2009-10-06 18:06:10.078 SEVERE: user.language = en
    2009-10-06 18:06:10.078 SEVERE: user.country = US
    2009-10-06 18:06:10.078 SEVERE: scm.server.version = 11.0.4202.75
    2009-10-06 18:06:18.453 SEVERE: ================== StartClientTransport ===================
    2009-10-06 18:06:19.875 SEVERE: Schedule is started!
    2009-10-06 18:08:39.859 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:08:49.859 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:08:50.000 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:08:59.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:09:09.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:09:10.000 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:09:29.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:09:30.000 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:09:39.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:10:19.875 SEVERE: AgentLastCheckInTask connect to secars failed: Access Forbidden
    2009-10-06 18:10:19.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:10:29.890 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:10:30.015 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:10:39.890 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:10:59.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:11:09.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:11:10.015 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:11:59.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:12:09.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:12:10.015 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:12:29.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:12:30.015 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
    2009-10-06 18:12:39.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:12:59.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:13:09.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ClientTransportInfoTask
    java.lang.Exception: HTTP 403 Access Forbidden, URL: http://localhost/secars/secars.dll?action=36
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:300)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    com.sygate.scm.common.communicate.CommunicationException: Unexpected server error. ErrorCode: 0x10010000
     at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:321)
     at com.sygate.scm.server.task.ClientTransportInfoTask.run(ClientTransportInfoTask.java:86)
     at java.util.TimerThread.mainLoop(Timer.java:512)
     at java.util.TimerThread.run(Timer.java:462)
    2009-10-06 18:13:10.015 SEVERE: AgentOnlineStatusTask connect to secars failed: Access Forbidden
     



  • 2.  RE: Unable to communicate with the reporting Component

    Posted Oct 06, 2009 07:27 AM


    1. Reconfigure the ODBC settings..


    2. Check the below link & resolve asap..

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



    Regards...
    Ramji Iyyer



  • 3.  RE: Unable to communicate with the reporting Component

    Trusted Advisor
    Posted Oct 06, 2009 07:33 AM

    Hello,

    Here's the Probable Solution:

    Please go through the following KB's and Let me know if that resolves your issue:

    Unable to communicate with the reporting component after logging into the Symantec Endpoint Protection Manager

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

    Error: "Unable to communicate with the reporting component" when opening Symantec Endpoint Protection Manager (Embedded Database)

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

    Error: Unable to Communicate with Reporting Component and HTTP 403 Forbidden in IIS with description as "The configured user for the current application pool does not have enough privileges to run CGI"

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

    Unable to communicate with reporting component – HTTP 404

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



  • 4.  RE: Unable to communicate with the reporting Component

    Posted Oct 06, 2009 07:34 AM
    Hi,

          If this computer is a domain controller, follow these steps:
    Click Start, click Administrative Tools, and select Active Directory Users and computers.
    In the active Directory Users and computers window, in the left pane right click on Domain controllers and select properties.
    On the properties sheet click on Group Policy tab, select the Default Domain Controller Policy and click on edit.
    In the new window, expand Computer Configuration, expand Windows Settings, expand Security Settings, and then expand Local Policies.
    In the left pane, click User Rights Assignment.
    In the right pane, double-click Adjust Memory Quotas for a Process.
    Click Add User or Group.
    Type the user name or the group name that is the security account for the application pool that you want, and then click OK. (Note: If you click Browse to add an account, you may have to click Object Types or Location to add the account that you want.)
    Click OK two times.
    In the right pane, double-click Replace a Process Level Token.
    Click Add User or Group.
    Type the user name or the group name that is the security account for the application pool that you want, and then click OK. (Note: If you click Browse to add an account, you may have to click Object Types or Location to add the account that you want.)
    Click OK two times.
    Exit the Group Policy Object Editor & other windows by clicking OK.
    Click Start, click Run, type gpupdate /force, and then click OK.
    Click Start, click Run, type iisreset, and then click OK.
    Method b: If this computer is a member of a domain, follow these steps:
    Click Start, click Run, type gpedit.msc, and then click OK.
    Under Local Computer Policy, expand Computer Configuration, expand Windows Settings, expand Security Settings, and then expand Local Policies.
    In the left pane, click User Rights Assignment.
    In the right pane, double-click Adjust Memory Quotas for a Process.
    Click Add User or Group.
    Type the user name or the group name that is the security account for the application pool that you want, and then click OK. (Note: If you click Browse to add an account, you may have to click Object Types or Location to add the account that you want.)
    Click OK two times.
    In the right pane, double-click Replace a Process Level Token.
    Click Add User or Group.
    Type the user name or the group name that is the security account for the application pool that you want, and then click OK. (Note: If you click Browse to add an account, you may have to click Object Types or Location to add the account that you want.)
    Click OK two times.
    Exit the Group Policy Object Editor.
    Click Start, click Run, type gpupdate /force, and then click OK.
    Click Start, click Run, type iisreset, and then click OK.

    If this computer is not a member of a domain, follow these steps:

    Click Start, click Run, type secpol.msc, and then click OK.
    Under Security Settings, expand Local Policies.
    In the left pane, click User Rights Assignment.
    In the right pane, double-click Adjust Memory Quotas for a Process.
    Click Add User or Group.
    Type the user name or the group name that is the security account for the application pool that you want, and then click OK. (Note: If you click Browse to add an account, you may have to click Object Types or Location to add the account that you want. )
    Click OK two times.
    In the right pane, double-click Replace a Process Level Token.
    Click Add User or Group.
    Type the user name or the group name that is the security account for the application pool that you want, and then click OK. (Note: If you click Browse to add an account, you may have to click Object Types or Location to add the account that you want.)
    Click OK two times.
    Exit the Local Security Settings tool.
    Click Start, click Run, type gpupdate /force, and then click OK.
    Click Start, click Run, type iisreset, and then click OK.



  • 5.  RE: Unable to communicate with the reporting Component

    Trusted Advisor
    Posted Oct 06, 2009 07:38 AM

    Also if,

    As we see the Error int he logs provided, we found,

    Unexpected server error. ErrorCode: 0x10010000

    Follow the KB:

    Clients stop communicating with Symantec Endpoint Protection Manager (SEPM) with HTTP 401 error in Sylink log and HTTP 401.1 error in IIS log

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008032702341648

     









  • 6.  RE: Unable to communicate with the reporting Component

    Posted Oct 06, 2009 07:39 AM
    What is the database you are using ?

    Title: 'Error: "Unable to communicate with the reporting component" when opening Symantec Endpoint Protection Manager (Embedded Database)'
    Document ID: 2008110803510948
    > Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2008110803510948?Open&seg=ent


  • 7.  RE: Unable to communicate with the reporting Component

    Posted Oct 06, 2009 07:41 AM
    Unexpected server error. ErrorCode: 0x10010000  the logs has HTTP 403


    Title: 'Error: Unable to Communicate with Reporting Component and HTTP 403 Forbidden in IIS with description as "The configured user for the current application pool does not have enough privileges to run CGI"'
    Document ID: 2008030706052048
    > Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2008030706052048?Open&seg=ent


  • 8.  RE: Unable to communicate with the reporting Component

    Posted Oct 06, 2009 07:52 AM

    Try this

    HTTP Error Codes and their meaning

    https://www-secure.symantec.com/connect/articles/http-error-codes

    http error 403 is present in your server



  • 9.  RE: Unable to communicate with the reporting Component

    Posted Oct 06, 2009 08:03 AM
    open your IIS
    right click symantec web server
    clcik on properties
    click on directory security
    click on autentication and access control
    check integrated windows authentication.
    try loggin in now, should work fine

    if this does not work,

    check your IUSR account, most of the times it will be member of guest account and guest account will be disabled.
    IUSR accont should be memeber domain users.

    or else create a new account and put in IIS, anonymous access.


  • 10.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 12:38 AM
    My database is microsoft SQL 2005 & Windows XP .I test with symantec endpoint protection support tool and i have go this error message.

    Error                   SEPM Virtual Directories with incorrect permissions:
                               Location                                                                Expected                                          Actual
                               /LM/W3SVC/1/Root/Reporting                     Scripts and excutables                       None
                              /LM/W3SVC/1/Root/Secars                           Scripts and excutables                      None
                              /LM/W3SVC/1/Root/Secars                           Scripts and excutables                      None

                             SEPM Virtual Directories with incorrect paths:
                             Location                                                         Path
                             /LM/W3SVC/1/Root                                  c:\inetpub\wwwroot

    Error                 Microsoft SQL Server version 2005.090.4035.00 is not identified version

    Error                  The Secars commucation test failed some tests:

    Error                  Microsoft SQL Server version 2005.090.4035.00 is not identified version


  • 11.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 12:55 AM
    As you have tried everything its better to take a backup and reinstall SEPM.


    Take a database backup
    copy server.xml from Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\conf
     copy keystore.jks from Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc.
    Reinstall database and restore the files.
    Run a SEPM reconfiguration wizard.


  • 12.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 01:01 AM
    If i uninstall the symantec endpoint manager, do i need to deploy the user again? i don't want to deploy the user again. Is there any other way to fix that problem? i cannot not see only home,monitor,report right now.


  • 13.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 01:18 AM
    Nothing will happen to your data and clients....
    Make sure you take proper backup of DB and the files which i have mentioned... 


  • 14.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 01:34 AM
    I cannot not see only home,monitor, report. It is because of SQL? In other froums they mention  permission in IIS.


  • 15.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 01:52 AM
    in the IIS, If i browse the Reporting it will show (Unexpected Error). I think i needed the permission.


  • 16.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 02:00 AM
    Ya it is because of IIS permission... When you do a repair it recreates the IIS permission...
    You tried every thing and did not get the solution so I told u to reinstall. Its a last option... 

    Try this...

    https://www-secure.symantec.com/connect/articles/how-create-new-reporting-virtual-directory-iis-manager-troubleshooting-unable-communicate-r


  • 17.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 02:06 AM
    Check the solution part of this forum...
    Its really good step by step information about your problem......

    https://www-secure.symantec.com/connect/forums/sep-manager-console-failed-load-3-menu


  • 18.  RE: Unable to communicate with the reporting Component

    Posted Oct 07, 2009 04:13 AM
    Right now i can login to the endpoint manager. But if i refresh the console page it stay missing.I testing with symantec endpoint protection support tool and i get one error in internet information service.

    The error mean that i stay missing the path. I don't know where to find that path in symantec endpoint manager. The error is

    SEPM virtual directories with incorrect path
    Location                                                                               Path
    /LM/W3SVC/1/Root                                          


    I don't know where to put the path.I already put this path to the symantec endpoint protection manager\inetpub but i still get the error.Please help me how to fix this porblem.


  • 19.  RE: Unable to communicate with the reporting Component
    Best Answer

    Trusted Advisor
    Posted Oct 07, 2009 07:33 AM

    Hello,

    Try the steps below..now

    1) open your IIS
    2) right click symantec web server
    3) clcik on properties
    4) click on directory security
    5) click on autentication and access control
    6) check integrated windows authentication.
    7) try loggin in now, should work fine

    if this does not work,

    check your IUSR account, most of the times it will be member of guest account and guest account will be disabled.
    IUSR accont should be memeber domain users.

    or else create a new account and put in IIS, anonymous access.

    Also if,

    As we see the Error int he logs provided, we found,

    Unexpected server error. ErrorCode: 0x10010000

    Follow the KB:

    Clients stop communicating with Symantec Endpoint Protection Manager (SEPM) with HTTP 401 error in Sylink log and HTTP 401.1 error in IIS log

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008032702341648


     



  • 20.  RE: Unable to communicate with the reporting Component

    Posted Oct 08, 2009 07:13 AM
    Today i fix this problem. I try Mithun Sanghavi Solution & it can fix my error. I check the integrated window authentication & it will fix all of my problem.Thank you for all who helping me.


  • 21.  RE: Unable to communicate with the reporting Component

    Posted Oct 08, 2009 07:53 AM
    Its good to here that problem solved...  


  • 22.  RE: Unable to communicate with the reporting Component

    Trusted Advisor
    Posted Oct 12, 2009 09:16 AM
    Hello,

    Thank you very much for trying the Solution provided.

    It would be really appreciated if you could mark the Solution provided as "Solution".



  • 23.  RE: Unable to communicate with the reporting Component

    Posted Oct 12, 2009 09:41 AM
    Good to see your issue getting resolved.

    @ MIthun: Keep up the good work. 

    Cheers,
    Aniket