Unable to communicate with the reporting component
Just installed the latest EndPoint Protection Manager onto a Windows 2003 server. I can log into the manager, but I get the following error:
Unable to communicate with the reporting component.
My Home, Monitors, and Reports tabs are blank. Everything else is available and works fine. I can add clients, and commands run on their machines from the console.
I did install the Symantec website as a custom site as I already have sites running in IIS. PHP was already installed on the machine at C:\PHP as well. It is the 5.2.6 version, the same as is installed in the Symantec folder.
Navigating to http://localhost:8014/reporting only displays a blank page.
I have no entries in my event viewer to help pinpoint a problem.
This server is a DC, and I have followed the KB article describing issues to be expected with a DC installation.
I've read through and attempted the fixes discribed in every article I could find that came up in search about this issue.
Setting IIS account to Local Service - no effect
Upgrading Java to the latest version and increasing its HEAP size - no effect
Double checked Network Service permissions - no effect (was already correct)
checked ODBC connections - no effect (connection test is ok, I am using the embedded database)
Anything else to be tried?
Comments
Create a new user for IIS
Hi
In IIS Change the IUSR. account
Create a new user in AD and make him the member of Guest . Replace this with IUSR in IIS .
Restart the IIS and SEPM service and see if this works or not.
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
Some possible causes
The primary components at play are IE Embedded, IIS, PHP, ODBC and the SQL database. In my experience this type of display behavior is most commonly a PHP error. By default with our product the PHP error is not set to display on screen and so IE Embedded simply displays a blank page. The following document discusses how PHP debugging can be enabled in several ways. My recommendation would be the display to screen option. This way if it is a PHP error you should see it instead of the blank screen.
PHP Debugging:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008010712380848
Though I have not seen this as common, another possible cause is the ODBC connection as described in the following KB.
ODBC connection:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007122311505400
Reconfigure ODBC Connection
Reconfigure ODBC Connection
Regards....
Ramji Iyyer
Regards...
Ramji Iyyer
PHP
Take a backup of C:\PHP folder then
Copy all the contents of Program files\Symantec Endpoint protection manager\php\* folder and paste it in C:\PHP folder and replace the new files with the existing ones.
SEPM should work..
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
Just to mention a right order
Just to mention a right order of troubleshooting steps since you are getting a totally blank page, just try replacing the IUSR account in website properties with Admin account. On a DC this needs to be done. Try to navigate to reporting website again. If it was a permissions issue, you would be able to see the login page, otherwise atleast some error which would point in the right direction.
The admin account can then be replaced with steps mentioned by Prachand earlier.
PHP issue
I think this is a PHP issue you can install the Fast cgi & then configure.
In SEP CD2 you will get the Fast CGI & the installation Guide.
to Save time
Hi,
as everyone mentioned problem is with php
so rename your c:\php to c:\php old
move it to d drive root
d:\php
in IIS extensions
change your php path for your applications to d:\php
by default symantec will look in c drive , not in d drive
so both applications should work fine
Rafeeq
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
Copying the PHP folder from
Copying the PHP folder from the Endpoint Security Manager folder to C:\PHP does solve the problem. However, I also run a Moodle website and a PHPmyadmin program on this server that stop working when I do this.
I've tried copying the original PHP folder to D:\PHP as you suggest. I'm a little confused as what you mean by "change your php path for your applications to d:\php".
In IIS, I can go under the web service extensions tabs to find a PHP ISAPI Extension file. I added D:\PHP as a location for this extension alongside the existing C:\PHP.
I then have tried changing both my Moodle and Phpmyadmin sites to use the D:\PHP\php5isapi.dll in the site's application settings as the default for .php functions.
I end up getting database configuration errors with both sites when I do this. They won't function again until I return C:\php back to its original state and roll back the changes made to IIS.
I've also tried lining up the php.ini files from both the existing php installation and symantec's making changes to the original to reflect the options present in the symantec version. No go, the symantec service won't even start when I do this (though moodle and phpmyadmin remain running).
Thoughts?
Hi, Please try the steps
Hi,
Please try the steps provided in the document below:
"Unable to communicate with reporting component" and BAD GATEWAY error on SERVER/reporting
http://service1.symantec.com/support/ent-security....
Cheers,
Aniket
Greetings!!! What is the type
Greetings!!!
What is the type of communication settings PUSH/PULL and what is the heartbeat????
If it is push then make it PULL and change the heartbeat to 1 hrs. Follow the steps to do so
1. Login to SEPM console
2. Go to Clients Tab.
3. Click any of the group.
4. Go to the Policy beside clients in the right side.
5. Expand Local Specific settings
6. Click the group- Push
7. make it Pull and change the heartbeat.
8. Close all the windows
9. reset the iis using iisreset command.
Ajit
Regards'
Ajit Jha
Technical Consultant
STS
Error: "Unable to communicate
Error: "Unable to communicate with the reporting component" when opening Symantec Endpoint Protection Manager (Embedded Database)
Question/Issue:
The Symantec Endpoint Protection Manager (SEPM) is installed with the Embedded Database. You are able to log-in; however, the error "Unable to communicate with the reporting component" occurs on login.
Cause:
This issue can occur if the ODBC connector is not configured to connect to the embedded database.
Solution:
To solve this problem enter the Symantec Endpoint Protection Manager login credentials for the Symantec Endpoint Security Database in the Data Sources (ODBC) configuration panel.
To enter the login credentials:
In the Windows Control Panel, open Data Sources (ODBC).
On the System DSN tab click Symantec Endpoint Security DSN.
Click Configure.
On the Login tab, enter the User ID DBA and the Symantec Endpoint Protection database password configured during installation (this is the same as the Endpoint Protection Manager login password by default).
On the Database tab enter the name of the computer that runs Symantec Endpoint Protection Manager into the "Server name:" field.
Under Database Name, enter the following: sem5
On the Network tab ensure TCP/IP is checked.
Enter the IP address of the computer that runs Symantec Endpoint Protection Manager into the TCP/IP field in the following format:
HOST=10.10.10.10
On the ODBC tab, click Test.
If the test is successful Click OK to save the changes. If the test is not successful please refer to the document "Symantec Endpoint Protection Manager 11.x communication troubleshooting" or contact Symantec technical support for assistance.
:-)
Enter subject (optional)
I was having this problem, and I tried your solution and it worked. Thanks!
Previous suggestion
Hi
Have you tried my prevoius suggestion
"In IIS Change the IUSR. account
Create a new user in AD and make him the member of Guest . Replace this with IUSR in IIS .
Restart the IIS and SEPM service and see if this works or not.
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
I've added a new user
I've added a new user "symantec" into AD with Guest permissions as you suggested. I changed the Symantec web site to use this account for access in place of the IUSR account and restarted IIS. Now the Symantec Endpoint Protection Manager won't remain running. It starts then stops, giving the following error:
The Java Virtual Machine has exited with a code of -1, the service is being stopped.
Rolling back changes hasn't had any effect. I can't get the service to run now.
I'm about one more night of troubleshooting away from rolling back to 10.2 and looking at other solutions.
Its the problems with PHP
Hi,
What i ment was, symantec looks in C drive for php versions
let it check , in the mean time we can change the php your applications are using.
can you let me know which one did u edit in web site extensions,
Reporter Or your application extension.
whever your application is using PHP we need to change all those paths.
Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq
IIS Manager
In the IIS Manager..
go to Web Service Extensions --Reporter-Properties..
Check the location of PHP-CGI
make sure it is pointing to symantec protection manager\Php\php-cgi.exe..if not add the php-cgi in the sepm\php\php.cgi.exe
VMWARE-- SEP 12.1 vs McAfee vs Trend Micro
you can grant full control
you can grant full control for IIS_Users to SEPM folder (and for subfolders)
Is your problem resolve? if
Is your problem resolve? if still not try to reinstall IIS then configure ODBC then try to log in. let me know how it goes
:-)
If you are considering
If you are considering re-installing IIS, then make sure that you run a repair install on SEPM. because after re-install, all the virtual directories of SEPM will be lost.
Repairing the SEPM will re-instate the website for Symantec.
Cheers,
Aniket
If you got this solved
let me, and all other users, know.
I have tried to get SEP up and running sharing the IIS with another software product, but no chance!
I could manage to only get one software working correctly with the IIS, the other one failed. (SafeGuard Enterprise Server)
I got the same error you get.
Would recommend to set the SEPM up on another machine, with its own IIS and see if its working. (worked for me)
best regards
Dominik
Consultant
PMCS.helpLine Software Gruppe
www.pmcs.de
follow us on Twitter: PMCS_NBU ; PMCS_BE ; PMCS_EV
unfortunately this had to be the solution
I was trying to avoid having to do what dominik suggested, but I ended up having to go with a dedicated machine. I would have much rather got it running on the other server, it's a much newer and better machine, but whatever. It's working now and seems to be ok with a Pentium III and 2GB RAM on an ancient Compaq.
For future reference, does SEPM play nice with Exchange? Sometime next year we'll be purchasing a new server, and I might think about switching it to the new machine at that time. This is planned to be our Exchange server however, so I'll need to know if the two can coexist.
and again
first of all, sorry to hear, that you also have not been able to get it up and runnig.
Now regarding the exchange: As it also uses the IIS, I would again not recommend to do it. But if you are able to get it running, let us know.
Consultant
PMCS.helpLine Software Gruppe
www.pmcs.de
follow us on Twitter: PMCS_NBU ; PMCS_BE ; PMCS_EV
i have the same error in win2008 standard R2
i could not find a document for this OS. im using native database .
You should open a new thread
You should open a new thread on this issue. Since the one you tagged onto was old (and solved) most people will ignore it. When you post you should mention what version of Endpoint you have and what version of Java you have.
Grant-
Please don't forget to mark your thread solved with whatever answer helped you : )
Would you like to reply?
Login or Register to post your comment.