Back to Blog

HP Support KM00354420: PC 11.5 – Test Run Failure

HP Software has  released a knowledge base article (KM00354420) to deal with failed runs on a newly installed PC Host within Performance Center 11.5 and higher. Indications of this conditions are a failed status at the “Launch Controller” step when trying to execute a test. A message window will display the message:

“Run test failed: Reason: Failed to launch Controller.”

Checking System Health may also report this error on the problematic Host:

“Check connectivity between the Controller and Load Generator”.

The problem is generally reported after the Host has been added successfully to Lab Management.  Because of this issue, the Host cannot be used in a load test scenario. The PC Host Controller process wlrun.exe crashes as soon as it is started. The cause can be a registration failure of certain PC Host DLLs during the Host installation. To verify that this:

  1. Log in to the problematic PC Host using RDP.
  2. Go to Start >Run type wlrun.exe and click OK.
  3. The HP LoadRunner Controller should start. Select OK on the New Scenario dialogue.
  4. If the LoadRunner Controller crashes at this point, go to the Workaround/Fix information below.

To correct the registration failure try the following steps on the problematic PC Host:

  1. Browse to %windir%\Microsoft.NET\Framework\v2.0.50727
  2. Type cmd and press enter
  3. In the command window, enter the following command:
    RegAsm.exe /codebase <PC Host Installation>\bin\SLAConfig.dll
  4. Browse to %windir%\Microsoft.NET\Framework\v4.0.30319
  5. Type cmd and press enter
  6. In command window, type the following commands:
    RegAsm.exe /codebase <PC Host Installation>\bin\HP.SEV.UI.Component.dll
    RegAsm.exe /codebase <PC Host Installation>\bin\HPSEVFacade.dll

Note: The default path for a PC Host Installation is C:\Program Files (x86)\HP\Performance Center Host

For more information on this issue and the KB article, please login to the HP Software support website with your valid support credentials at this URL:

Back to Blog