LRE Test Run Failure Due to Endpoint Name Resolution Issue

Disclaimer: The information provided in this article is for general informational purposes only. The author and the publisher do not guarantee the accuracy, completeness, or reliability of the information. The techniques and suggestions mentioned may cause harm if not implemented correctly. The author and the publisher are not liable for any damages resulting from the use or misuse of the information. Use your own judgment and exercise caution when applying the suggestions in this article. Always consult official documentation and experts, and test changes in a controlled environment before applying them to production systems. By using this information, you agree to hold the author and the publisher harmless from any liability or claim.

Applies To:

• LoadRunner Enterprise (LRE) 2024 (and potentially earlier versions)

• Deployed on on-premise servers or cloud environments (e.g., AWS EC2)

Issue:

When attempting to run a Proof of Concept (POC) or standard load test in LRE, the test fails to execute. The error logs indicate a failure to connect to the PCSLoadTestManagement.svc endpoint with the message:

There was no endpoint listening at http://<hostname>/PCS/PCSLoadTestManagement.svc that could accept the message.

The specific error in the logs may look like:

System.Net.WebException: The remote name could not be resolved: '<hostname>'

Cause:

This issue typically occurs due to hostname resolution failures on the LoadRunner Controller machine. Specifically:

• The Controller machine is unable to resolve the name of the LRE server.

• The hostname used (e.g., ec2amaz-xxxxxx) is either not registered in DNS or cannot be resolved due to lack of internal DNS configuration.

• The LRE configuration refers to a machine name that is not resolvable by the Controller machine.

Steps:

Step 1: Update the Hosts File on the Controller Machine

1. Navigate to the following path on the Controller machine:
   C:\Windows\System32\drivers\etc

2. Open the hosts file using Notepad (Run as Administrator).

3. Add an entry that maps the IP address of the LRE Server to its hostname. For example:

   10.0.0.25    lre-server-hostname
   

   Replace 10.0.0.25 with the actual IP address of the LRE server, and lre-server-hostname with the machine name used in the LRE configuration.

Step 2: Reconfigure Host in LRE UI

1. Log in to the LRE Web UI.

2. Navigate to Hosts under Administration.

3. Update the host configuration to match the correct IP or resolvable hostname.

4. Save the configuration.

Step 3: Re-run the Load Test

After the above changes, initiate a test run again. The test should now connect successfully to the PCS service and execute as expected.

Additional Info:

• This issue is commonly encountered in cloud environments (e.g., AWS, Azure) where machine names like ec2amaz-xxxxxx are not registered in DNS by default.

• Ensuring that name resolution (DNS or local hosts file) is properly configured between Controller, Load Generators, and LRE Server is critical for successful test execution.

• In enterprise environments, consider using static DNS entries or internal DNS services for machine name resolution instead of relying on auto-generated hostnames.

We hope this article provided you with the assistance you needed. If you would like to find out more regarding the Services and Support Offerings we provide, please reach out to our Sales Team.