Unexpected server error - msg after upgrading to SEP12RU6

[ThaveshinP]

Anyone see this before or make sense of this error message. Saw this in the System logs under "Errors and above"

Event type:	An unexpected exception has occurred
Event description:	Unexpected server error.
Error message:	Unexpected server error.
Error code:	Unexpected server error.
Stack trace:	java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at java.net.Socket.connect(Socket.java:528) at sun.net.NetworkClient.doConnect(NetworkClient.java:180) at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) at sun.net.www.http.HttpClient.<init>(HttpClient.java:211) at sun.net.www.http.HttpClient.New(HttpClient.java:308) at sun.net.www.http.HttpClient.New(HttpClient.java:326) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:997) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:933) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:851) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1301) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468) at com.sygate.scm.common.communicate.Communicator.getResponse(Communicator.java:1783) at com.sygate.scm.common.communicate.Communicator.getResponse(Communicator.java:1181) at com.sygate.scm.server.task.ClientTransportInfoTask.getClientTransportInfo(ClientTransportInfoTask.java:511) at com.sygate.scm.server.task.ClientTransportInfoTask.execute(ClientTransportInfoTask.java:140) at com.sygate.scm.server.task.MonitoredTimerTask.run(MonitoredTimerTask.java:41) at java.util.TimerThread.mainLoop(Timer.java

[Migration User]

Have you try to repair SEPM for add/remove program ?

[ThaveshinP]

No not yet, have to schedule change control to do that as we have 50000 clients connecting.

[ThaveshinP]

Is there no Symantec dev's looking at this. I cant run a repair to the SEPM every time I see this.

[ℬrίαη]

Have you opened a case and submitted logs to them? Can't imagine a repair every time is the answer.

[Ramji Iyyer]

Hi Guys,

 

I am also facing this issue since 11.0 RU6 MP3. This does not impact our daily operations.

Only the logs are generated. I also tried clean installation but this issue persists.

Waiting for permanent fix.

[ℬrίαη]

11.x is end of support life so you won't get a fix for the 11.x product.

[Ramji Iyyer]

Brain,

I had mentioned  SINCE 11.0. RU6MP3. Current version is 12.1 RU6

[Migration User]

Hi,

 

If Apache is run on a server with teamed NICs, this issue may occur when Apache attempts to renegotiate the IP address after the service has already started.  If you experience this issue on a SEPM with teamed NICs, you can bind Apache to a specific IP address in order to resolve the issue.  

1.  Stop the Symantec Endpoint Protection Manager and Symantec Endpoint Protection Webserver services.  

2.  Edit the httpd.conf file in \Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\apache\conf\httpd.conf

Bind Apache to  the specific IP addresses on the system by changing the following line:

Listen 8014

Replace it with:

Listen sepmIPaddress:8014 (Where 'sepmIPaddress' is the IP address of the SEPM)

Listen 127.0.0.1: 8014

3.  Restart the Symantec Endpoint Protection Manager and Symantec Endpoint Protection Webserver services. 

 

Refer:

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