Here are the LoadRunner tweaks used to deal with these issues

Login.c(7): Error -26000: rc=-1/WSAGetLastError=10038 from WSAEventSelect(_nSocketFD=4294967295, _pvEvent=00000000, muiNewDir=0x00000021) in SocketDesc::SetWaitDir for this=09E16C08: An operation was attempted on something that is not a socket.

And

logout.c(10): Error -27778: SSL protocol error when attempting to connect with host ''aut.test.com'', Snapshot Info [MSH 0 9]

to eliminate this intermittent SSL and ''not a socket'' errors that occurs when replaying the LoadRunner scenario in the controller.

Modify your script(s) to include the following statements, these statement should be at the beginning of the script(s)

Vusert_int()

// Or

Action()

{

web_set_sockets_option(''SSL_VERSION'', ''3'');

web_set_sockets_option(''MAX_CONNECTIONS_PER_HOST'',''1'');

            web_browser(''aut.test.com'', 
            DESCRIPTION, 
            ACTION, 
            ''Navigate=https://aut.test.com'', 
            LAST);

...

The first line web_set_sockets_option(''SSL_VERSION'', ''3''); forces the SSL connection to use SSL version 3 instead of letting the server suggest a version during the connection handshake.

The second line web_set_sockets_option(''MAX_CONNECTIONS_PER_HOST'',''1''); forces a single TCP connection to stay live between the Load Generator to the AUT servers. Ending the possibility of errors when LoadRunner sends data across that connection, if the server try to prematurely shutting down an existing connection