Endpoint Protection

 View Only
Expand all | Collapse all

Unable to communicate with the reporting component after upgrading to RU5

Migration User

Migration UserFeb 24, 2010 03:19 AM

  • 1.  Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 02:11 AM
    After upgrading to SEPM 11.0.5002.333/RU5 i have an error during opining the SEPM "Unable to communicate with the reporting component " and when i press on OK button i can login to the SEPM but i can't check (Home, monitor and reports tabs) but i'm able to check polices, clients and admin tabs.

    I have restart the serve but still have the same proble.

    Can you help please?


  • 2.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 02:16 AM
     

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

    If this link not helps paste/attach the scm-server-0.log with is present in Program Files \Symantec\Symantec Endpoint Protection Manager\tomcat\logs


  • 3.  RE: Unable to communicate with the reporting component after upgrading to RU5



  • 4.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 03:04 AM
      |   view attached
    Hi,

    Thanks to reply me. i tried the link but still dosn't work with me.

    Please find attached the log file you asked.

    Thanks alot.

    Attachment(s)

    zip
    scm-server-0_1.zip   890 B 1 version


  • 5.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 03:13 AM
    Do yo have any proxy settings in IE?
    If yes try by removing it.
    Whether the ODBC connection was successful?
    Immediately after the upgrade whether the database upgrade wizard pop ups?
    Whether it is completed successfully?
     


  • 6.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 03:19 AM
    Run a repair for SEPM and see if that helps.


  • 7.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 03:45 AM

    Hi,

    I have tried to Test Data Source but it's failed.

    Acoording to the link you sent me:

    Name: SymantecEndpointSecurityDSN
    Description: <Anything>
    Server: Servername\InstanceName (Can be blank as it is localized, otherwise specify the default: sem5)
    Login ID: dba
    Password: <password>

    For the server i put the name of the server but for password should i put the SEPM pass or keep it blank? and in case i should put the SEPM pass then should i change the login ID to the one i'm using normally?

    Regards,



  • 8.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 03:50 AM
    ID: is always DBA
    password: is your SEPM password, the first password what you used to set sepm
    if not this is how you can find your password, configure ODBC , the issue should get resolved.
    https://www-secure.symantec.com/connect/articles/how-find-database-password-embedded-database 


  • 9.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 03:54 AM
    Do not change the login name. 
    If you are configured with simple it will be same as the login password of SEPM.If you used advanced it will be different one,you have to use the password which you used.
    Refer this article if you do not know the password
    How to find the Database password for Embedded Database


  • 10.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 04:11 AM
    1-normally when i login to SEPM i'm using username= admin and pass=xxx in ODCB connection i pressed on configure then i went to login tabe and i put userID=DBA (capital) and put the password=xxx (the same pass for admin user which i used normally to connect to sepm). i think this is exactly what you asked. is it?

    Also in Database name i put =sem5 and server name = the server name

    I went to the ODCB tabe again and pressed on Test Connection button but error: Connection Faild: database server not found.

    Any thing els to do it,

    Thanks alot

      


  • 11.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 04:21 AM
    you are making one small mistake.
    click on network
    check tcp/IP

    type host=ipaddress of your server
    now test the connection

    http://img514.imageshack.us/img514/3461/odbc.png

     


  • 12.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Broadcom Employee
    Posted Feb 24, 2010 04:31 AM
    check the IIS settings and permissions. ANoanymous access should be enabled.


  • 13.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 05:30 AM

    Hi,

    Anoanymous access  already enabled  and TCP/IP already was configured as shown in the attched pic and still have Connection Faild: database server not found..

    Any other idea?

     



  • 14.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 05:40 AM
    add spc_ infront of server name.Also try by keeping the user name dba in lower case 


  • 15.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 05:48 AM
    Hi,

    I was writing for you about "spc" to tell you it was thier before as SPC_servername but i have remove it and when runing the test connection: Connection Faild: database server not found.

    If i add the SPC (capital or small letters) to the server name SPC_servername  and run the test connection, another error: connection faild: invalid user ID or password. i tried also with dba not DBA and i'm sure of the password because i tried to login to SEPM more than one time and it's fine. but i still have the same problem

    ??????????/


  • 16.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 06:00 AM
    Do you tried that article  which I suggested in earlier post for finding the password?


  • 17.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 07:05 AM
    I have very strange thing. let me explain:


    as i said before i'm logong to to SEPM

    usernema: admin
    password: xxx

    long time ago during logging to SEPM it asked me to change the password. it happened more than one time and i put a new password (zzz)

    now i tried to test the connection with

    User ID: dba
    pass: zzz

    and it worked fine. the test connection is OK but when i tried to login to SEPM with

    username: admin
    pass: xxx

    i still have the same problem. i can't check (Home, monitor and reports tabs) but i'm able to check polices, clients and admin tabs and the same error come :Unable to communicate with the reporting component.

    I tried to login to SEPM:

    username: admin
    pass: zzz

    but authentication failure and this is normal cuz this pass changed long time ago to xxx but i think since it's the first pass i used it has been accepted in the ODCB. is it it right?


    But why i still have the error?Unable to communicate with the reporting component.


  • 18.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 07:14 AM
    thats okay, lets try why your home page is not showing up.
    do you use a proxy in internet explorer?
    try this
    http://localhost:port used by sepm /reporting 
    do you get a log in page or access denied?



  • 19.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 07:28 AM
    There is no proxy in IE and http://localhost:9090 is working fine.

    Regards,


  • 20.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 24, 2010 07:32 AM
    Port is not 9090 ,He is telling about the port which SEPM installed (port of your SEPM IIS webserver) and the url is  http://localhost:port/reporting


  • 21.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 08:05 AM

    Can you tell me how can i check the port in IIS please?

    Regards,

    Martin



  • 22.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 08:30 AM
    start - run-inetmgr
    expand websites, look for symantec web server
    right click properties, you will get the port number it will be 80 or 8014
    open IE
    http://localhost:port/reporting.
     give authenticated users full access to C:\Program Files\Symantec\Symantec Endpoint Protection Manager folder


  • 23.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:03 AM
    Thanks to reply

    Inside the web sites, there is default web site then i have :

    clinet package
    content
    reporting
    secars
    secregaspnet_client

    I did not find symantec web server??

    Could you please advice?

    Thanks


  • 24.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:07 AM
     THat means your SEPM is installed on default website and most probably on port 80.


  • 25.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:09 AM
    Your sepm is intalled on default website
    so open an IE
    http://localhost/reporting
    what do you get ?
    page cannot be displayed or access denied? 


  • 26.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:26 AM
    yes i got page cannot be found.

    So what is that mean?


  • 27.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:28 AM


  • 28.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:44 AM
    Two things:

    when i type http://localhost/reporting  in the IE it dosn't asked me about user name and pass but directly give error page cannot be found and not displayed.

    Also when i access the SEPM i don't have page can not be displayed. pleas look to the attached pic how it looks like?



  • 29.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 09:49 AM
    can you check if anonymous access is checked in IIS?
    open -iis
    right click default website
    properties
    under directory security check integrated windows authentication.
    click on
    right click on reporting virtual directory, select browse
    does that give you log in screen ? 


  • 30.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 10:00 AM
    anonymous access is checked in IIS as you told me before to check it you and


  • 31.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 10:41 AM
    Thats a generic error..Well try this now..

    Open the ODBC 
    Remove everything that you have inserted and click OK.

    Login  : Supply username and Password : Username & Password -Blank

    Database :Server name : SPC_SERVER'S NAME

    Network : tcp/IP : IP=127.0.0.1:2638

    Click OK.
    then try looging into SEPM.




  • 32.  RE: Unable to communicate with the reporting component after upgrading to RU5



  • 33.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:21 AM
      |   view attached
    I tried:

    Open the ODBC 
    Remove everything that you have inserted and click OK.

    Login  : Supply username and Password : Username & Password -Blank

    Database :Server name : SPC_SERVER'S NAME

    Network : tcp/IP : IP=127.0.0.1:2638

    Click OK.
    then try looging into SEPM.

    But it not changing any thing, still i have the same error.

    Also i tried to enable php but still i have unexpected error without any details. so i tried to save the logs to a file but it's not writing any logs in the file.

    Please check the copy of the php.ini file i modfied.

     

    Attachment(s)

    zip
    Php.zip   695 B 1 version


  • 34.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:27 AM
    the log wont be generated if its on c root i think, can you put it somewhere else? 


  • 35.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:30 AM
    Enable log visit on Reporting

    right click -reporting -properties

    then try logging in ( to generate logs)
    then
    go to C:\WINDOWS\system32\Logfiles\W3SVC1

    open the recent log file and let us know if you see any http 4xx.x error code.


  • 36.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:36 AM
    I changed the location and i checked the permission on the folder and file where i creat the log to be saved and have full permision but still not writing inside it.???????
     


  • 37.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:43 AM
      |   view attached
    i enabled log visit.

    please find attached the log file

    Thanks

    Attachment(s)

    zip
    ex100225.zip   818 B 1 version


  • 38.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:43 AM
     You can also try one more troubleshooting step.

    Un-install IIS from add/remove programs - add/remove components- uncheck IIS..next..next finish

    reboot the computer

    Install IIS same way you removed.

    then Repair SEPM from add/remove programs - change -repair..next..next..install.


  • 39.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 25, 2010 11:54 AM
    the log shows 404
    might be an issue with java
    remove the version of java installed

    Home, Monitors, and Reports pages are blank in the remote console after upgrading to Java 1.6 Update 10, or newer

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


  • 40.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 26, 2010 01:59 AM
    Check whether Microsoft Internet Explorer is your default browser,if no set it as the default browser.For this do as follows
    Open the Control Panel and go to the Internet Options.
    Click the Programs tab.
    Check the option Internet Explorer should check to see whether it is the default browser.
    The next time you open Internet Explorer, you should be prompted to set it as the default browser.
     


  • 41.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Feb 28, 2010 03:44 AM
    Hi all,

    I can't remove IIS cuz there is another application using the iis (mantis) but i tried to repair SEPM but the same problem still exist.

    Also i'm using only IE on this server and it's the default browser.

    For Java, i did not upgrade or downgrade any thing on the server and it was working fine before i upgrade to RU5.

    Thanks,

    Martin


  • 42.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Mar 10, 2010 05:09 PM

    Did you try setting the permissions for the LOCAL SERVICE and NETWORK SERVICE accounts as listed in the "
    Check the IIS Configuration\Verify User Rights" section of the Symantec support doc ID 2008042212582048 ? (http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument)

    I just had this problem with an SAV 10.1 upgrade and this solved it for me. (I had to apply it via GPO as it was installed on a Domain controller.)



  • 43.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Mar 11, 2010 04:20 AM
    i have same problem before, then resolve with install fastcgi 32 bit (fcgisetup32.exe) dowdload from microsoft. To run script follow instruction on SEP CD2. (html file)


  • 44.  RE: Unable to communicate with the reporting component after upgrading to RU5

    Posted Apr 08, 2010 02:25 AM

    I have followe all the articles including (http://service1.symantec.com/support/ent-security....) but my problem did not solve.

    can you please explain more about (fcgisetup32.exe).

    -link to install it...
    -is there any setting to do.
    -what about the sepm CD2 and what can i find there to help me install (fcgisetup32.exe)

    Regards,