RTE Protocol Scripts Failing in Performance Center :: TE_Connect.. Failed to Connect

137 views
Skip to first unread message

Binga

unread,
Jul 30, 2015, 1:07:55 PM7/30/15
to LoadRunner
Am getting below error while running my RTE protocol scripts in Performance Center.....The scripts are working fine in Vugen.


Error: TE_connect failed after 1 tries. Retrying Reason: Unable to connect to host. The error message is: Connection closed by host.

During connection of comm-type = telnet;host-name = test565;telnet-port = 22;terminal-id = ;set-window-size = true;security-type = ssh;ssh-type = ssh2;ssh-show-info = false;ssh-show-login-dialog = false;ssh-cipher = 3DES;ssh-enable-compression = false;ssh-enable-x11 = false;ssh-attempt-tis = false;ssh-allow-agent = false;ssh-keyboard-interactive = false;ssh-key-file = ;ssh-username = ;terminal-type = vt420-7;terminal-model = vt220;login-command-file = ;terminal-setup-file = ;



Sudhir Kumar

unread,
Aug 27, 2015, 3:17:20 PM8/27/15
to LoadRunner
Looks like there is a limitation with TE_Connect. Better increase the timout value in the TE_connect() call or manually code a retry mechanism in the script

Bala Ji

unread,
May 11, 2016, 9:20:50 AM5/11/16
to LoadRunner

I too faced similar issue.

Here are the steps that I followed to overcome this issue.

1. Telnet Port: 23 ( Default ) & SSH Port: 22 ( Default )
2. While running through VuGen, there is some component which am unsure that opens connectivity with port 22 which is a SSH port.
3. But while running through ALM, this component is not called up, so port 22 connectivity is not established.

Work Around Followed:

1. As per my requirement, it is not a mandatory to use SSH, I can proceed with Telnet.
2. So, I enabled the Telnet Port and commented out the SSH codes and connected to port 23 and script runs successfully in ALM. 
Reply all
Reply to author
Forward
0 new messages