Endpoint Protection

 View Only
Expand all | Collapse all

Unable to communicate with the reporting component problems

Migration User

Migration UserJan 26, 2010 12:47 PM

  • 1.  Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 09:39 AM
    I have installed Symantec Endpoint Protection manager 11.0.5002.333 on 3 servers, all windows server 2008 r2 x64, they are each connected to a backend SQL 2008 x64 enterprise server at each site and they all replicate perfectly with each other through SEPM.  My problem is, everytime I login to any of them I get "unable to communicate with the reporting component" and it doesn't show the Home, Monitors, or Reports tab.  And I know some of you will more than likely post the thing about the ODBC connection fix well, that thing doesn't work, mine connects perfectly to the database and that fix is for people using the embedded database.  I've also tried many other "fixes" and none of them seem to work.  I'm leaning torwards something with IIS because of the following fix.  Normally if I open a browser to http://localsite:8014/reporting I get a blank page.  However, if I go to c:\....Symantec Endpoint Protection Manager\Inetpub\Reporting and give the everyone group full access to that folder the reporting site comes up to a login screen and if I attempt to login I then get a blank screen that says "LOGOUT_SPM".  Also after I make this change and try to login to the SEPM it immediately logs me out.  I'm beginning to think this is something with IIS but I've reinstalled IIS and rechecked all the settings several times.  I've attempted to phone Symantec about this problem but they never seem to want to answer the phone so I thought I'd try here.  Any suggestions?


  • 2.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 09:45 AM
    when you are tying to log in try with ip address on the home login page
    do u have network service listed in your gpo.

    if its on dc try this , if not you can add it locall

    Symantec Endpoint Protection: Adding Network Service to the Default Domain Controller Policy
    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008010816442248

    what do you have in your host file?
    you should have loopback address not the ip address of your server.

    are you local to the box or remote? installing on console session also fixes this issue.


  • 3.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 09:50 AM
    I have to install it via remote, it's a virtual machine.  Host file is unchanged from how ti comes loaded in a brand new windows server installation.  I've tried logging in via ip address but it does the same thing localhost does.


  • 4.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 09:52 AM


  • 5.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 10:07 AM
    Yeah I just checked and it is added in the GPO.  Anything else?


  • 6.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 10:11 AM
    open a browser
    type http://localhost:8014/reporting
    note: 8014 is the port number your sepm is on

    what do you get?

    page cannot be displayed

    do you have proxy setting in IE?

    if so bypass proxy for local server address.


  • 7.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 11:19 AM
    when i go to that site i get "cannot display the webpage"  please reread the original post, i stated this already.


  • 8.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 11:25 AM
     Open IIS manager -Symantec webserver - reporting -right click and browse..
    Check if you get any error or a login screen.
    Also enable Log Visits on secars and check what you get in IIS logs..


  • 9.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 11:26 AM
    Since you are able to receive the login page, I don't think it could be a permission issue... Something else is preventing from loading the home page..

    Enable startup errors in the php.ini and try to login, lets see what it says...  And also, you might as well try this before editing php file... Since its a 64 bit OS, Download and install the 64 bit version of JRE from the following location:

    https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=jre-6u16-oth-JPR@CDS-CDS_Developer.



    * After insalling Java, perform a repair of SEPM ...  and lets see if we have any luck :)


  • 10.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 11:36 AM
    Interesting, I can reach the login page for reporting now via IIS7 Manager and I can login and view the page for reports but it still comes up with that error when I try to login via SEPM


  • 11.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 12:23 PM
    when logging into the manager then rather than localhost:8443 try using servername or Ip address 8433. 


  • 12.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 12:47 PM

    Does the same exact thing.



  • 13.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 12:54 PM

    do you have any diff verion of php installed

    How to enable error logging to troubleshoot PHP issues in Symantec Endpoint Protection Manager (SEPM
    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008010712380848
    eanble the log in and let us know the errors

    give a full permission to F:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection Manager\Php

    for everyone..

    and check.
     



  • 14.  RE: Unable to communicate with the reporting component problems

    Posted Jan 26, 2010 01:17 PM
    No I don't have any different version of php installed.  I enabled logging but it never creates a log file in the location I specified.  The reporting site comes up and lets me login now so that's probably why.  But why won't the reporting site come up when I login to SEPM is what I want to know??


  • 15.  RE: Unable to communicate with the reporting component problems

    Posted Jan 27, 2010 08:03 AM
    I guess symantec is pretty much worthless at this point, no suggestions and the enterprise support never answers after being placed on hold for 2.5hrs.  I really want to speak to a supervisor, this is rediculous.


  • 16.  RE: Unable to communicate with the reporting component problems



  • 17.  RE: Unable to communicate with the reporting component problems

    Posted Jan 29, 2010 02:32 PM
    None of these have worked.  I was told by a symantec support tech that it might be that I installed it through a RDP connection but I have since uninstalled it and reinstalled it through a straight console session and the same thing happens.  I do notice this problem only happens when I need to connect it to an external SQL database, if I use the embedded database I never have problems getting into those three reporting tabs.


  • 18.  RE: Unable to communicate with the reporting component problems

    Posted Jan 29, 2010 02:37 PM


  • 19.  RE: Unable to communicate with the reporting component problems

    Posted Jan 29, 2010 02:51 PM
    Thanks for the above link but why must I change to SQL authentication mode, why won't it work with Windows authentication.  Not to mention those instructions aren't made for my version of IIS 7 so it is going to take me a while to figure out those settings.


  • 20.  RE: Unable to communicate with the reporting component problems

    Posted Jan 29, 2010 03:05 PM

    give it a try , u can revert back anytime u like :)