Endpoint Protection Small Business Edition

 View Only

  • 1.  HTTP error 503

    Posted May 05, 2015 02:12 AM

    SEP Clients disconnecting from Manager after upgrade 12.1.5



  • 2.  RE: HTTP error 503

    Posted May 05, 2015 02:24 AM

    I suggest you can raised support ticket.

    See same problem thread

    https://www-secure.symantec.com/connect/forums/sep-client-cannot-communicate-sepm-after-upgrade-121-1215



  • 3.  RE: HTTP error 503

    Posted May 05, 2015 08:38 AM

    Enable sylink debugging on an affected client let it run thru a few heartbeats, post the log here for review:

    Enable sylink debugging for Endpoint Protection clients



  • 4.  RE: HTTP error 503

    Posted May 18, 2015 04:46 AM

    Case was created with Symantec for more than 2 weeks and the response is very bad. The problem still not solved.

    Clients and servers also were not updated more than 2 weeks.

     



  • 5.  RE: HTTP error 503

    Broadcom Employee
    Posted May 18, 2015 10:19 AM

    Could you share the support case number would like to look into it.

    Have you tried by pushing out communication update package?



  • 6.  RE: HTTP error 503

    Posted May 18, 2015 10:34 AM

    has to do with Apache, do you have any other website running on it?

    Have you checked under TCP/ IP settings, is it set to Auto? or Full Duplex?



  • 7.  RE: HTTP error 503

    Posted Jul 03, 2015 08:45 AM

    Hi all,

    I am having the same issue after upgrading from 12.1.4 to 12.1.6 and now i am getting 

    2015/07/03 12:05:07.416 [3276:15020] AH: Setting the Browser Session end option & Resetting the URL session ..
    2015/07/03 12:05:07.456 [3276:15020] <ParseHTTPStatusCode:>503=>503 SERVICE NOT AVAILABLE
    2015/07/03 12:05:07.958 [3276:15020] AH: Setting the Browser Session end option & Resetting the URL session ..
    2015/07/03 12:05:07.998 [3276:15020] <ParseHTTPStatusCode:>503=>503 SERVICE NOT AVAILABLE
    2015/07/03 12:05:08.000 [3276:15020] ###### Set ACSConnec offline
    2015/07/03 12:05:08.000 [3276:15020] CProfileMgrManPlugin::ReceiveMessage: enter
    2015/07/03 12:05:08.000 [3276:15020] ProfileMgrMan: ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] CProfileMgrManPlugin::ReceiveMessage: exit
    2015/07/03 12:05:08.000 [3276:15020] AVMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] AVMan: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] LUMan: Entering ReceiveMessage with id 0x40002
    2015/07/03 12:05:08.000 [3276:15020] AtpiMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] AtpiMan: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] BashMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] BashMan: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] CidsMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] CidsMan: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] NETSECMAN: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] NETSECMAN: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] RebootMgrMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] RebootMgrMan: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] RepMgtMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] RepMgtMan: Leaving ReceiveMessage
    2015/07/03 12:05:08.000 [3276:15020] SubmissionsMan: Entering ReceiveMessage with msg id 262146
    2015/07/03 12:05:08.000 [3276:15020] SubmissionsMan: Leaving ReceiveMessage