Endpoint Protection

 View Only
  • 1.  unable to communicate with the reporting component

    Posted Jun 17, 2009 09:40 AM
    When i am trying to solve this by testing the ODBC connection it is giving error that "user name and password is incorrect"

    and i cross checked with customer again same.

    and what problem actually i am facing is in the ADMIN console  first three modules are not coming  just displaying BLANK and after logging immediately it is giving the error " UNABLE TO WITH THE REPORTING COMPONENT"

    plase help to sort out this problem



  • 2.  RE: unable to communicate with the reporting component

    Posted Jun 17, 2009 09:45 AM
      There can be many reasons for this error follow this document 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


  • 3.  RE: unable to communicate with the reporting component

    Posted Jun 17, 2009 10:45 AM
    is thers any way to reset the DBA password(embeded database) and the OS using is WINDOWS XP


  • 4.  RE: unable to communicate with the reporting component

    Posted Jun 17, 2009 10:59 AM
    There is a way but you should know your Old password for it try this

    http://service1.symantec.com/support/ent-security.nsf/docid/2008011823355248 

    Also can you let me know if you go to IIS & try to Browse the Reporting hive under the symantec webserver what do you get.
    Try UseID as DBA & password as symantec & see if that works.


  • 5.  RE: unable to communicate with the reporting component

    Posted Jun 17, 2009 11:08 AM
    I also had similar issues with this. I tested the ODBC connection to the database which was ok. My problem was the username that IIS was using for the reporting php page. It uses the default IIS_username to access the page but for some reason it didnt have the appropriate permissions. I went into the reporting component under IIS to change the authentication method. I used a valid admin account and selected [Integrate Windows Authentication]. I then restarted IIS and all is well now.