Hi

Try these steps:
1. Install JAVA 1.5 or later
2. Visit these links: 
 (A)  http://service1.symantec.com/support/ent-  security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

(B) http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/32a9ac7fc1ff64b8882574fa007a946b?OpenDocument

Regards
Ajit

Have you checked the IE security settings on the server?

Check your ODBC connection as well.

Why do you need the port number?

It does not work for me either if I add the port number. Without it it works fine.

http://localhost:8014/reporting    Unable to Connect

and http://localhost    OK

 http://localhost:8014  Unable to Connect

and http://localhost/reporting   ok

If you don't use the port number it just defaults to 80.  I assume many of you are using the default website with port 80.  So you could use http://localhost:80/reporting and get the same result. 

If this is an Upgrade, (you originally installed MR0-MR2) then port 80 is the default install port.
Port 8014 is the default port only if you have fresh installed from MR3 or higher.

Hi,

I Think IIS install on SEPM is having problems processing PHP files.

Think I figured this one out...

I just did a fresh install of SEP 11.0.4202 (MR4 MP2) today on a pair of Server 2003 R2 SP2 x86 Hyper-V VMs (it's a Hyper-V cluster, each SEPM server runs on a separate node). I had this exact problem on BOTH of them. What I figured out is that for some reason the SEPM install configured my IIS site on both servers to use the domain account I use to connect to the SQL database. I'm not sure what the reason for this is, but it turns out this account didn't have permissions to the directory structure where the Reporting files reside. Once I added it, everything started working. What I did was:

1. Open Windows Explorer to %PROGRAMFILES%\Symantec\Symantec Endpoint Protection Manager\

2. Open the Security permissions of the Inetpub directory.

3. Click the Advanced button and remove the checkmark next to "Allow inheritable permissions...". When it asks what you want to do, click on "Copy" then on "OK".

4. Add the domain account used to connect to your SQL database and give it Modify permissions. Click on Apply.

5. Click on the Advanced button again and add the checkmark next to "Replace permission entries on all child objects..." and click on "OK". Click "Yes" when it asks if you want to continue.

Mine worked immediately but you may have to do an IISRESET.

We too dont use the ports like that of Maximilian...
http://localhost/reporting
thanks...

Can you post screenshot?

Hi,

I am reading a lot of confused pieces of information here.

Clarifications for all:
1) before MR3, SEPM installed its website in the default website with the default port 80. If you don't type the port, the http will be use the default port... 80.
2) from MR3 SEPM installs its custom website on port 8014... this is not the default port for http, therefore you must explicitly type it.
3) SEPM does not install anything in http://localhost or http://localhost:8014, these tests are not significant for SEPM, you have to browse to our virtual folders, like in these URL's:
http://localhost:8014(or 80)/reporting
http://localhost:8014(or 80)/secars/secars.dll?hello,secars

Questions:
1) is the SEPM website installed on port 80, 8014 or somethink else? Check it in IIS, then you will know if you have to type the port or not and which one.
2) is this server a Domain Controller? There is a well-known problem with this configuration

Troubleshooting:
Enable the IIS logging and check what http errors you get when you test the URL's:
http://localhost:8014(or 80)/reporting
http://localhost:8014(or 80)/secars/secars.dll?hello,secars

Cheers,

 This is a very generic error reading the logs might give some insigt about the problem
but before that have you tried everything on this Article ?
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

I tried the following link and didn't fix the issue. Still comes up maybe 50% of the time.

http://service1.symantec.com/support/ent-security....

Considering the different articles and how common it appears, Symantec needs to come up with a better fix than to try 10 different things as listed in:
http://service1.symantec.com/support/ent-security....

About 1/2 the time when I log into SEP Manager, I get the reporting error. This is from my PC. I rarely get on the server but I did once after experiencing the issue on my PC and same thing. As for the server, it was a brand new Windows 2003 load with nothing out of the ordinary done for permissions, rights, etc. No group policies are applied to it and no other software is installed so I guess this is why I was surprised this error occured and has been discussed in the forums quite a bit (relative to other issues).

The last time I worked on this, I was not aware of the other KB article so I will try that and hopefully will get it resolved.