Troubleshoot load generators

This section provides information for troubleshooting issues related to load generators.

Troubleshoot load generators over a firewall

Problem Description

The following problems might arise when using a load generator that is located over a firewall:

  • Cannot add the load generator to a performance test.

  • The check host process on the load generator returned a Failed result.

  • The load generator has the Unavailable or Non-operational state.

  • Cannot restart the load generator.

  • The Over Firewall tab in the Hosts module does not display the load generator’s settings.

Troubleshooting

  1. Check that the load generator is configured correctly.

    1. In LoadRunner Enterprise Administration, under Maintenance > Hosts, select the Hosts tab.

    2. Click the host in the grid and select Host Details.

    3. Verify that the Location is ofw, and that a name for the MI Listener is defined.

    4. On the host on which the load generator is installed, launch LoadRunner Agent Configuration from the Start menu using the Run as administrator option. The Agent Configuration dialog box opens.

    5. Select Enable Firewall Agent, and then click Settings. The Over Firewall Settings dialog box opens.

    6. Make sure that the MI Listener Name exactly matches the MI Listener defined for the host in LoadRunner Enterprise Administration above.

    7. Make sure that the Local Machine Key exactly matches the host’s and location’s name as defined above. Format: <ofw_host_name>_<ofw_location_name>.

    8. Click OK, and then OK again to close the Agent Configuration dialog box.

    9. When prompted to restart the Agent, and click OK.

    10. In the Remote Management Agent Service log, verify that the agent is up and running.

  1. If any of the problems listed above persist after checking the load generator configurations, try the following:

    1. Check that the MI Listener is up and running.

    2. Check that the MI Listener logs do not contain any errors.

Back to top

If UNC collate fails, the load generator is set to "already collated"

Problem Description

When a collate failure is encountered and UNC collate fails, an error is returned to LoadRunner Enterprise, but the load generator is marked as "already collated". As a result, on collate retry, the process succeeds even though no data is collated from the machine.

Troubleshooting

Deactivate UNC collate on all affected Controller machines. To do this, open the Collator.exe.config file located in the <LRE_host_installdir>\bin directory, and change the "EnableUncAttempt" value from 'true' to 'false'.

Back to top

"Change Machine Identity failed" when adding new host

Problem Description

When adding a load generator as a Windows Host from LoadRunner Enterprise Administration, encounter the following error: "Change Machine Identity failed. Reason: User already exists with a different password."

This error can occur if the load generator is already linked to a different environment.

Troubleshooting

Make sure the load generator is not linked to any other environment before adding it.

Back to top

See also: