The Home, Monitors, Reporting pages fail to appear when you launch the Symantec Endpoint Protection Manager or Symantec Protection Center.
The Symantec Endpoint Protection Manager or Symantec Protection Center shows page not found.
This error can occur for the following reasons:
Ports to the reporting server are blocked
SEPM/PHP directory permissions
IE security settings
IIS permissions on virtual directories (e.g. IIS lockdown procedures, Active Directory permissions, etc...)
Apache configuration issues
First ensure the port used from reporting functionality is not blocked locally or externally:
To test the port used by the reporting functions follow the steps below. Note:This is a loop back and does not leave the machine. 1. Open Internet Explorer and type the following: https://127.0.0.1:8445/reporting 2. This will bring up a window that states that the Certificate is not valid - Click to continue anyway. 3. This will bring up a dialog window that will allow you to log into the reporting function. Enter your log in information. Does not need a domain unless there is more than one domain. 4. If working correctly, this will bring up the all the reporting functions of the manager.
Perform the test again using the IP address of the machine to see if the port is being blocked. This test will simulate using the Reporting function from another machine.
1. Open the internet Explorer and type the following in the address box: https://<IPaddres_of_SEPM>:8445/reporting . 2. A dialog may appear stating there is a problem with this websites's security certificate. Click "Continue to this website". 3. This will bring up the same dialog window to log into the reporting portion of the Symantec Protection Center. Log into the reporting function using the normal log in information. 4. Verify the reporting function appears.
If these tests fail, verify that port 8445 is not blocked.
If port 8445 is open, then try the following:
Verify the PHP temp folder and Symantec Endpoint Protection Manager folder have full permissions for Administrator and SYSTEM account:
Note: If you have a working SEPM you can replace the httpd.conf file on the non-working server with a copy from the working SEPM. Be sure to stop the SEPM service before replacing the file, then restart the service after it is replaced.
Enable TLS 1.0 in the IE settings: Internet Options > Advanced > Security > enable TLS1.0
Ensure IE Enhanced Protection is disabled
If none of these suggestions correct the issue, then please contact Symantec Technical Support and open a support ticket.
Imported Document ID: TECH165437
Subscribing will provide email updates when this Article is updated. Login is required.