- Error -10343: Communication error: Failed to connect to remote host
Make sure that you apply the same LoadRunner version and Service Pack on the Controller and Load Generator machines.
Make sure that you can ping the Controller and host machine bidirectionally. You may need to add the IP address and machine name on the host file
- Error -29989: Process “lr_bridge.exe” was not created on remote host , reason – communication error.
The LoadRunner Agent Process is trying to connect through a port that is busy .LoadRunner Agent Process/service starts itself at port 50500 and 54345 (For monitoring/running vuser over firewall, it is port 443). Do a netstat -an on the machine and check to see if 54345 and 50500 are occupied. If these ports are in used when you start the agent, you will get the above error.
- Error -10344: Communication error: Failed to bind socket. A process on the machine is already bound to the same address.
You may also get this error during replay if LoadRunner agent of the host machine is connecting back to the controller using a port that is already bound.
- ERROR -29987: Process “traceroute_server.exe was not created…” when connecting to a remote host.
verify that you are able to ping back and forth between the controller and the load generator machines using both host names as well as ip addresses..
Add the host name and ip address of load generator to the hosts file on the controller. Add the host name and ip address of the controller to the hosts file on the load generator
5.Error -30932: “Failed to open eve file
The Load Generator files may be specified in the Controller options to be shared on a network drive, but they are being saved on a local drive. To check this, in the Controller go to Tools -> Options -> RunTime File Storage and select the “On the current Vuser machine” option