Error -10343: Communication error: Failed to connect to remote host [server name: ]. (sys error message – ) [MsgId: MERR-10343]
Posted: April 21st, 2008 | Author: TnT Admin | Filed under: Errors | Tags: Controller, Errors | 1 Comment »I believed that you would have encountered the following error when you are having load generator connectivity problems.
Error -10343: Communication error: Failed to connect to remote host [server name: ]. (sys error message – ) [MsgId: MERR-10343]
Error -29989: Process “lr_bridge.exe” was not created on remote host “” ,reason – communication error. [MsgId: MERR-29989]
Lately, while I was verifying the upgrade of my LoadRunner versions from 8.1 to 9, I encountered a connectivity problem with the Controllers and Load Generators but well, it’s been resolved… Anyway, just to share with you like a case study on the steps I took to troubleshoot the problem.
Initially I went to the support website in hope to find some information with these generic errors but they weren’t helpful in my context. I’m not implying that they are useless but it wasn’t applicable to me at that point of time. You can look through it too first:
- Document ID 25162 – Common connectivity problems between Controller and Generator
Document ID 11905 – How-to and troubleshooting guide for setting up a Windows machine as a Load Generator
To give you a background information, I’ve got 4 machines, one Controller and 3 Load Generators (LG). Let’s name them in the following manner for the ease of illustration:
- 1. Controller – CONTROLLER
2. Load Generators – LG1, LG2 and LG3
The OS installed for all machines were Window XP and firewall programs were installed in them, namely ZoneAlarm and Sygate.
The following steps were taken:
- 1. Ping from CONTROLLER to LG1, LG2 and LG3 – No problem
2. Ping from LG1, LG2 and LG3 to CONTROLLER – No problem
3. Telnet port 54345 from CONTROLLER to LG1, LG2 and LG3 – No problem
4. Telnet port 54345 from LG1, LG2 and LG3 to CONTROLLER – No problem
5. Turn off Windows XP firewall for all machines – Done
6. Allowed firewall access for incoming and outgoing traffic – Done
7. Install LoadRunner full suite on LG1 and connect to all other machines via the Controller program – All machines connected except unsuccessful connection to CONTROLLER.
This is clear that communication in terms of network port from ALL machines were successful. Except CONTROLLER where port establishment from the LoadRunner program on CONTROLLER was unsuccessful which signifies that the problem could be caused at the application-level.
- 8. Tried launching the Sygate on the CONTROLLER – Unsuccessful; Sygate not launched.
After trying all the above, my assumption is that Sygate is corrupted with the LoadRunner, disallowing the it to communicate to the agents on the LG. I’m left with two options.
- a. Uninstall Sygate.
b. Format the entire machine and start anew with nothing on it.
I went ahead with [a] before doing the ultimatum [b]. And well, it solves the whole thing! (of course, I installed a new copy of Sygate to get things back to normal too.) Anyway, summary of this troubleshooting, it was caused by a corrupted firewall program which may affect you too so do take note in future!
Nice one