Symantec Access Management

  • Private Community

  • 1.  Socket error 10053

    Posted Jan 10, 2014 10:05 AM

    smps.log in Siteminder 12.5CR004 shows a lot of socket errors 10053, i.e. ->

    [3820/3788][Fri Jan 10 2014 09:53:05][CServer.cpp:2268][ERROR] Failed to receive request on session # 6312 : xxxxxxxxxxxxxxxx. Socket error 10053

    (xxxxxxxx is for the server name and ip address)

    These errors don't seem to affect anything.  Anybody knows why this occurs?

    Thanks



  • 2.  RE: Socket error 10053

    Posted Jan 10, 2014 10:48 AM

    You didn't say what OS your running on.  Could it be windows? because:

    a.)  That socket error number is unusual.

    b.)  A google of the error turns up windows and mentions anti-virus software?

    http://www.wisegeek.com/what-are-the-common-causes-of-socket-error-10053.htm

     

    Maybe CA support and your virus software vendor can help alleviated it?   The error seems indicative of an established webagent session being dropped or timing out at the tcp level.

     

     

     



  • 3.  RE: Socket error 10053

    Posted Jan 10, 2014 10:59 AM

    Hi.

    Thanks for response.  Yes, it is Windows2008R2.

    I've already disabled Antivirus (McAfee), as I also thought it was related to it based on the search results, but the error is still there.

     



  • 4.  RE: Socket error 10053

    Posted Jan 10, 2014 01:34 PM

    socket error 10053 is a winsock (windows socket) error.

    unix are much much lower.

    http://lmgtfy.com/?q=winsock+error+codes+list

    try the second hit on the google search that brings up.

     

    Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission time-out or protocol error.

     

    ie: your os killed it on SM



  • 5.  RE: Socket error 10053

    Broadcom Employee
    Posted Jan 14, 2014 12:14 PM

    Hi,

    Socket error 10053 is actually a windows socket error.
     
    The use case goes something like this...
     
    Something (likely an agent) attempted to connect to the policy server.
    The request was queued.
     
    By the time the policy server got to the request, the connection was closed.
    This can happen if the queued requests take longer for the policy server to
    complete then the agent is configured to wait for.
     
    This can also occur when the connection is interrupted by dropped packets
    on the network or a 3rd party product on the server.

    Thanks



  • 6.  RE: Socket error 10053

    Posted Jan 16, 2014 10:32 AM
    gena.pasmanik:

    smps.log in Siteminder 12.5CR004 shows a lot of socket errors 10053, i.e. ->

    [3820/3788][Fri Jan 10 2014 09:53:05][CServer.cpp:2268][ERROR] Failed to receive request on session # 6312 : xxxxxxxxxxxxxxxx. Socket error 10053

    (xxxxxxxx is for the server name and ip address)

    These errors don't seem to affect anything.  Anybody knows why this occurs?

    Thanks

     

    Hi,

     

       Check the below link for various socket errors, this error generally comes when some software is blocking the connection.


    http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx

    WSAECONNABORTED
    10053

     

    Software caused connection abort.

    An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.

     

    Regards

    Vikas Tiwari