"Error -27778: SSL protocol error when attempting to connect with host" in load runner | SSL handshake with remote server Failed error

When i run the scripts in LRE i am facing 

"Error -27778: SSL protocol error when attempting to connect with host",

Error: Action.c(44): ssl_handle_status encounter error : SSL_ERROR_SSL, error message : error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version [MsgId: MMSG-26000]
Action.c(44): Error -27774: SSL protocol error when attempting to connect with host "XXXXX" [MsgId: MERR-27774]

Write the below functions at the start of of script:


web_set_sockets_option("SSL_VERSION", "TLS"); or

 web_set_sockets_option("SSL_VERSION", "TLS1.2"); or
web_set_sockets_option("SSL_VERSION", "1");

This forces the SSL connection to the server to use version 1 of the SSL protocol rather than letting the server suggest a version during the connection handshake. If it is not work talk with Developers to get the exact SSL_VERSION USED for communication by your Application.
If this doesn't works try to change the registry.

In the Registry change [HKEY_CURRENT_USER/Software/Mercury Interactive/LoadRunner/Protocols/WPlus/SSL/OpenSSL] "ReuseSSLSession" value to 1

Run-Time Settings -> Preferences -> Select "WinInet Replay Engine instead of Sockets (Windows Only)."

"HttpSendRequest" failed, Windows error code=12002 - Perf Center Error_load runner error

While running an internal application using the load runner Controller i was getting the "HttpSendRequest" failed, Windows error code=12002 - Perf Center Error .I solved these by following the below steps:

1.Check Vugen runs script as a process or running  vusers asa  thread?

You can check this in Run time settings-General-Miscellaneous-Multithreading then uncheck the value

2.Are you working with WinInet, and the error itself comes from WinInet API not specifically Vugen.We can see in part of the replay  errors comes from resources during the replay where they were timed out.

If we are forced to use WinInet then this will occur, but if you can use Sockets you may want to try that option instead or a Click and Script protocol.

you can uncheck the WinInet replay instead of sockets (Windows only) in the runtime settings-preferences.This will solve the problem.

3.And the another option is to use web_set_max_retries ("X") to increase the limit of 30 sec.You can place this before the action which is failing but  I wouldn't recommend that.

HttpSendRequest time out only occurres when any transaction takes more than 30 sec to connect to server. This default 30 sec time is because of the use of WinInet Replay engine. Thus this error pops up when you are running script with winInet replay and transactions are taking more than 30 sec. Only thing to get rid of this error is to fine tune the whole system and check the backend and servers to see any request que has formed up.