Endpoint Protection

I used CleanWipe to remove SEP 11.0.5002.333 from SBS 2003 and installed SEP 11.0.5002.333

now every time i open SEP i get unable to communicate with the reporting component error

i am using SQL 2005 as the DB

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

Test the odbc connection should fix the issue.

For an SQL database

1. Verify the following:
   • You specified a named instance during installation and configuration. For example: \\<server name>\<instance name>
   • The SQL Server is running and properly configured
   • The network connections between Symantec Endpoint Protection Manager and the SQL database.
     
2. Test the ODBC connection.
   1. Open Control Panel > Administrator Tools
   2. Double click Data Sources (ODBC)
   3. On the System DSN tab, double-click SymantecEndpointSecurityDSN
   4. Go through the wizard to ensure the following settings:
      
      Name: SymantecEndpointSecurityDSN
      Description: <Anything>
      Server: Servername\InstanceName (Only enter the server name or IP address if using the default instance)
      Login ID: sa
      Password: <password>
      
   5. Leave the defaults for the rest of the items and click Finish
   6. Click Test Data Source , it should return "Success"
   7. Click OK

If the above steps don't work then paste the scm.server0.log

and also clear the transcation logs in SQL.

Symantec DSN tests OK


below is the scm.server0.log



2009-12-06 22:00:49.375 SEVERE: ================== Server Environment ===================
2009-12-06 22:00:49.375 SEVERE: os.name = Windows 2003
2009-12-06 22:00:49.375 SEVERE: os.version = 5.2
2009-12-06 22:00:49.375 SEVERE: os.arch = x86
2009-12-06 22:00:49.375 SEVERE: java.version = 1.6.0_14
2009-12-06 22:00:49.375 SEVERE: java.vendor = Sun Microsystems Inc.
2009-12-06 22:00:49.375 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2009-12-06 22:00:49.375 SEVERE: java.vm.version = 14.0-b16
2009-12-06 22:00:49.375 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2009-12-06 22:00:49.375 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
2009-12-06 22:00:49.375 SEVERE: java.user = null
2009-12-06 22:00:49.375 SEVERE: user.language = en
2009-12-06 22:00:49.375 SEVERE: user.country = US
2009-12-06 22:00:49.375 SEVERE: scm.server.version = 11.0.5002.333
2009-12-06 22:00:52.750 SEVERE: ================== StartClientTransport ===================
2009-12-06 22:00:52.875 SEVERE: Schedule is started!

are logging in remote or local to the box?
if yes, then try loggin in with console session
start - run - mstsc / console..
proxy configured in your internet explorer?

i am local to the box. i am wondering if i have a php version conflict?

Yes,should be the issue,
do u have any other application running PHP ?
do a search for  PHP folder, if u find any php other than symantec endpoint protection managers php
then just rename the other php folder, try logging in,  check if that works.

found the problem. how do i fix it?

I think the manger is picking the backupexe php.

just rename backupexec php and try opening sepm ,if it runs fine then u need to follow this document.

Specifying the php.ini file used by the Symantec Endpoint Protection Manager (SEPM) Reporting website.


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

so i did Version dependent method:

1. Browse to the PHP sub-folder inside the SEPM folder (C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Php by default).
2. Right-click on php-cgi.exe and choose Properties.
3. Select the Version tab. Note the first three digits of the 4-digit File version number.
4. Click Start->Run and type regedit. Hit Enter.
5. In the registry editor, expand My Computer, then HKEY_LOCAL_MACHINE\Software\
6. If the sub-key PHP does not exist
   1. Create it by right-clicking on the right-hand pane and choosing New->Key.
   2. Name the new registry key PHP.
7. Right-click in the right-hand pane and choose New->Key.
8. Name the new registry key to correspond with the first 3 digits of the php-cgi.exe File version (ie 5.2.5 for the 5.2.5.5 version of PHP that ships with SEPM 11.0.2000).
9. Right-click on the right-hand pane and choosing New->String Value.
10. Name the new registry value IniFilePath.
11. Modify the IniFilePath value and add the file path to the SEPM Php.ini file (ie C:\program files\Symantec\Symantec Endpoint Protection Manager\PHP\Php.ini).
12. Close the registry editor
13. Click Start->Run and enter "iisreset.exe /restart". Hit Enter.

and now i am getting a different error

from services.msc
try starting symantec endpoint manager service
or else
open iis
click on symantec web server properteis
click on directory security
click on authentication and access control
check intigrated authentication
start the sepm service
try loggin in again.

Thank you

mon_raralio for the link
Rafeeq for the fix

finally we fixed it.. Thank you Mon and Net_tech..Good day !

But I am faciing the same problem till now .I have lost hopeand think that I have to format the server.

Earlier this server was working as scs3.1 server and wsus server. I uninstalled all these and installed sepm as replication partner to my main sepm server . replication is going well but unable to see the three tabs with the error "unable to communicate with reporting components"  while loging in.

any further solution so that i can try

On the server is there any program that is using PHP

No
no other program is installed except office2003

when you go to iis.
open sepm web severs
right click on reporting and click on browse what do u get?
are u local or remote?

i am back to square 1.
the problem "unable to communicate with the reporting component" has come back after i rebooted the server

 @Net_Tech -- Fine tune your ODBC as per Mon's link.Make sure it comes up as successful.
If it still fails and you suspect its due to PHP
then take a backup of the PHP file in the Backup Exec folder
Copy the Content of the PHP folder in SEPM\PHP and paste it in Backup Exec folder and replace existing.

If in case BE doesn't work then you can replace backed up PHP content back top BE folder.

@Bijay- Re-install IIS and repair SEPM.

OK 

if i use pcanywhere to connect the server, i don't get an error, but if i use RDP i get the error.

any ideas?

 - Created new application pool.

try logging in with console session with rdp

start - run - mstsc /console.

you should not get the error

mstsc /console did not help

Hi Rafeeq from IIS I am getting fast cgi error.

http error 500

only 1 php.exe in program files sepm\php  folder