Endpoint Protection

When logging into the Protection Manager with "admin" and the localhost I am getting the error "Unable to communicate with the reporting component."
Has anyone else had this error? Any help will be much appreciated.

This error has been seen before. Two of the KB's that relate to this error are listed below. You should look through them and see if they help and if not post back, and we can try other things.
Cheers,

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

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

Also it would help to know what version are you running, and on what OS?

Is ur IIS configuration is well set??  Visit the following KB article

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

Ajit

Is this server a Domain Controller as well?

You can also check the steps given in the document below and let us know the results:

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

Cheers,
Aniket

The version of SEPM is 11.0.4014.26. The server is not acting as a Domain Controller.  IIS is set correctly as well as the Reporting Virtual Directory.  When I right click and select "Browse" in IIS Manager Web Sites\Symantec Web Server\Reporting  I get the following error:
"Bad Gateway, The server received an invalid response from another server while attempting to fulfill the request."
Is there a specific version of PHP we should be using?  Thank you for your help with this!

You can actually Bypass the PHP altogether.

Install FastCGI (If not already installed), and bypass the PHP installation as per the following KB - service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/04bee96905e871ca8825745c006f5575

Hope this helps.

Please let us know if your issue is resolved if not we can suggest you more steps to do but first you can run the SEP Support tool that can help you resolve most of your issues.

After going through all the suggested fixes, we did a full uninstall and reinstall of SEPM. This seems to have fixed the issue at hand.  Thanks!