"Error -27778: SSL protocol error when attempting to connect with host" in load runner
Recently i had some issues with SSL protocol error,while running the scripts in controller i am facing the "Error -27778: SSL protocol error when attempting to connect with host",so finally i got rid of that by using the below steps in the script Keep the below code at the start of of script use web_set_sockets_option("SSL_VERSION", "TLS"); 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. We had same issue on vugen 11.50 with new patch also then we enabled the below setting Run-Time Settings -> Preferences -> Select "WinInet Replay Engine instead of Sockets (Windows Only)."
Posted by raviteja gorentla 2 comments:
Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest
Labels: Controller, General, Performance Testing, Scripting, Vugen
"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.