Endpoint Protection

When I login to the SEPM console it shows black just an error " Unexpected error" .

I do restart the server but same result :(...

any idea what should i do now?

See the attached log file

Attachment(s)

scm-server-0.pdf   16 KB 1 version

no response !!!!!!!

Your SEPM seems to run on an XP box. Perhaps you have more than 10 concurrent connections to the SEPM.

See this thread: http://www.symantec.com/connect/forums/constant-unexpected-server-errors

And have a look on this KB article:

Symantec Endpoint Protection communication issues due to Error HTTP 403.9 - Access Forbidden: Too many users are connected

http://www.symantec.com/docs/TECH104358

Hope that helps!

... have a look here :

http://www.symantec.com/connect/forums/symantec-endpoint-protection-manager-11-mr5-console-error

Solution

Solution 1:

1. Browse to C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection Manager\php\temp
2. Right click on the temp folder and select the Security tab, Is the IUSR account listed there and does it have full permission?
3. If not, then apply the same and try to login into the SEPM.

 Solution 2:

1. Go to C:\WINDOWS\system32\drivers\etc
2. Open the host file with notepad
3. Towards the end of the file, it should have only these lines

127.0.0.1       localhost  (Default IP)

    4.   If any other IP address is mentioned remove the same, unless they are critical and valid for the business, and save the file and try to login to the SEPM.

You should now be able to login into the SEPM successfully.

Suggestion:

This may require running a repair of the SEPM installation using Add/Remove Programs in the Control Panel.

Please do the following and revert back..

1. Launch the Services utility (>Start >Run "services.msc") to ensure that the Symantec Endpoint Protection Manager service is stopped.
2. Navigate to the ...\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\etc directory and open the conf.properties file with Notepad.
3. Modify the scm.server.port= line to 8444, and then save and close this file.
4. Go to >Start >All Programs > Symantec Endpoint Protection Manager to launch the Management Server Configuration Wizard.
5. Complete the Management Server Configuration Wizard to implement this change.
6. Return to the Services utility and start the Symantec Endpoint Protection Manager service.
7. Login to the Symantec Endpoint Protection Manager

Regards

As per the attached logs I can see there is a "HTTP 403 Access Forbidden" error.

As per the error it means that may be you have some ip address specifed in the denied access list in the IIS

For that go IIS > Symantec web server > Properties > Directory security and click on the second edit tab to see if there is any IP address in the denied list. ( by default it should allow all)

also make sure there is no SSL certificate getting used in IIS.

Hi,

For unexpected error  follow the below steps:

Ensure that all Symantec services are started

·         Check that all database ports are available (1433 for SQL or 2638 for Embedded)

·         Verify ODBC connection

Verify communication to the embedded (Sybase) database.

1.     Verify that the "Symantec Embedded Database" service is running and that the "dbsrv9.exe" process is listening on TCP port 2638.

2.     Test the ODBC connection.

                 i.        Click Start> Control Panel

                ii.        Open Administrator Tools

               iii.        Double-click Data Sources (ODBC)

               iv.        Select the System DSN tab

                v.        Double-click the SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:

o    Name: SymantecEndpointSecurityDSN

o    Description:

o    Server: Server name\Instance Name (Can be blank as it is localized, otherwise specify default "sem5")

o    Login ID: dba

o    Password: <SEPM Login Password> 

 

               vi.        Leave the default settings for the remaining items and click Finish

              vii.        Click Test Data Source, and verify that it states "Success"

             viii.        Click OK

Verify communication to the Remote (SQL) Database.

3.     Verify that you have specified a named instance during installation and configuration. Example: \\\

4.     Verify SQL Server is running and properly configured.

5.     Verify the network connections between Symantec Endpoint Protection Manager and the SQL database.

6.     Test the ODBC connection.

                 i.        Click Start> Control Panel

                ii.        Open Administrator Tools

               iii.        Double-click Data Sources (ODBC)

               iv.        Select the System DSN tab

                v.        Double-click SymantecEndpointSecurityDSN and go through the wizard to ensure the following settings:

o    Name: SymantecEndpointSecurityDSN

o    Description:

o    Server: Server name\Instance Name (Only enter the server name or IP address if using the default instance)

o    Login ID: sa

o    Password: <SA Password> 

 

               vi.        Leave the defaults for the rest of the items and click Finish

              vii.        Click Test Data Source on the next page and ensure it states "Success"

             viii.        Click OK

·         Reboot the machine.

If the above does not resolve the issue, examine the scm-server-0.log for possible indications of the cause. By default, this log is located in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\.