South Africa Security and Compliance User Group

Expand all | Collapse all

Unexpected server error - msg after upgrading to SEP12RU6

Jump to Best Answer
  • 1.  Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 04:45 AM

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

    Event type:
    Event description:
    Error message:
    Error code:
    Stack trace:


  • 2.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Broadcom Employee
    Posted 07-22-2015 05:04 AM

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



  • 3.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 06:00 AM

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



  • 4.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 06:01 AM

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



  • 5.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 06:03 AM
    Have you opened a case and submitted logs to them? Can't imagine a repair every time is the answer.


  • 6.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 06:17 AM

    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.



  • 7.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 06:29 AM

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



  • 8.  RE: Unexpected server error - msg after upgrading to SEP12RU6

    Posted 07-22-2015 07:02 AM

    Brain,

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



  • 9.  RE: Unexpected server error - msg after upgrading to SEP12RU6
    Best Answer

    Broadcom Employee
    Posted 07-22-2015 07:50 AM

    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