Vidéos d'aide de Screencast

SEP 11 SEPM Console Keeps Loosing Communications with DB

Created: 30 Janv. 2013 • Updated: 30 Janv. 2013 | 6 comments

3x's in the last week, have had the SEPM Console Fail. Loosing Connection with our External DB.

So far has come back up, but I have had to Start and Stop Symantec Services for SEPM.

This is just one of the errors I get:

Server returned HTTP response code: 500 for URL: https://localhost:8443/servlet/ConsoleServlet

Our Console is on SEP 11.6 RU 3.

Any ideas, is this a Java issue?

Commentaires CommentairesAccéder au dernier commentaire

l'image des Chetan Savade


Please update us with Server OS details?

If possible please pass on scm-server-0.log file.

File would be present under tomcat\logs folder.

Go through the following articles:

Java -1 Errors and HTTP 500 errors when connecting to the Symantec Endpoint Protection Manager on a Windows Server 2008 64 bit

Java -1 Errors and HTTP 500 errors when connecting to the Symantec Endpoint Protection Manager on a Windows Server 2003 64 bit

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

l'image des pete_4u2002

does it happen at specific time?
are the NIC running with latest?
is there any firewall between DB and SEPM ?

l'image des SebastianZ

HTTP 500 would be internal server issue - may be a problem with the Web server IIS. Do you see any other errors in the Event Viewer?

l'image des JS@support


This error is commonly seen with SEP 11 product.

You should upgrade the SPEM to SEP 12.1 

SEP 12.1 doesn't have any dependency on IIS.SEP 12.1 will use apache which is much much stable compare to IIS especially when we integrate SEPM with IIS.

However if you upgraded to the latest SEP 11 version this error can also go away. Take Symantec tips if using SEPM on windows 2008 or using IIS 7.

l'image des usacc23

My OS is Windows 2003 R2 32bit

I believe this article is the one that

is causing me angst:

Why is happened all of a sudden though I kinda find odd.

I believe the only solution for me now is to Upgrade from SEP 11.6300 to SEP 11.7300 on the SEPM.

We are currently going through a SEP 12.1.2 Project that won't be done until June.

Please let me know if this sounds correct to anyone out there?

l'image des JS@support


If DB service is up and running while doing an upgrade then upgrade can be successfull.

You can go ahead with the upgrade.