Host in Resource Failure in Performance Center

Problem description: The host is in Resource Failure status.

Troubleshooting

Option 1: Check the host connections

Check the connections between your project’s hosts and the machines

within your system using the Check Hosts operation in the Hosts page of

the Administration Site (Resources > Hosts > Check Hosts) or User Site

(Project > Hosts > Check Hosts).

 

If Ping to Host fails:

➤ Make sure the host is up and running, and is connected to the network.

Check the routing table (netstat –r) and make sure that requests to this

host are properly routed.

➤ Make sure that the host’s IP address can be properly resolved.

➤ Verify that the ping to the target host from the Performance Center Web

server, utility server, and database is below 20 ms.

➤ If your firewalls or hosts ignore ICMP requests (pings), use HTTP requests

to validate response times from the host to the Web server (a simple

LoadRunner web_url(…) request to http://<server>/loadtest/).

Alternatively, open a browser and type http://<server>/loadtest in the

address field.

If the file server fails:

➤ Make sure that the host can ping the file server.

➤ Make sure that the Performance Center system user has access to LRFS

share on the file server. You can verify this in any of the following ways:

➤ In the command line, execute the following:

net use \\fileserver\LRFS / user:

<Performance_Center_user><Performance_Center_user_password>

➤ Log in to the host machine as the Performance Center system user, and

in the command line, execute the following:

% net use \\fileserver\LRFS

If the above operation fails, check the error message and resolve the

problem. Contact your Windows administrator for assistance.

➤ Make sure that the security settings on LRFS share allow the HP

Performance Center system user full control.

➤ Make sure that the Performance Center system user can create, update,

and delete files from LRFS share.

➤ Make sure that the Performance Center Web server can launch

applications on the host

➤ If the database fails:

➤ Check the <HP Performance Center>/bin/globals.ini file and make sure

that the connection string is correct for the database you are using.

➤ See the troubleshooting for “Login to Oracle Database Server Hangs” on

page 124.

➤ Verify ADODB connectivity to the database 

Option 2: Check the Performance Center version

Make sure that the version of Performance Center service pack level and

feature pack level on all your host and server machines are the same as those

on the Performance Center Web and Utility servers. That is, all Performance

Center hosts and servers MUST be at the same service pack and feature pack

level.

Check the registry entry under

[HKEY_LOCAL_MACHINE\SOFTWARE\Mercury

Interactive\LoadRunner\CurrentVersion] for the following variables:

➤ Major

➤ Minor

➤ ServicePack

Note: Any patches applied to one machine must be applied to all machines

if and when applicable.

Option 3: Launch wlrun.exe manually from the Controller host machine

If the host check succeeds, but the host is still not operational, launch the

Controller manually from the Controller host machine as follows:

1 Log in to the host machine.

2 Configure the wlrun.LrEngine application to run as an interactive user:

➤ Launch dcomcnfg.exe.

➤ In the Application tab, select wlrun.LrEngine from the list of DCOM

applications.

➤ Click Properties to view the properties for wlrun.LrEngine.

➤ In the Identity tab, set the user account to The interactive user.

➤ Click OK and close the DCOMCNFG window.

Note: When you are finished with this step, set wlrun.LrEngine back to

its original identity. By default, this is This User with the Performance

Center user name and password. If you used a different identity, restore

it.

3 Launch the Controller (wlrun.exe) from the <HP Performance Center>/bin

directory (on the Controller host).

4 If an error message is displayed during the startup of the Controller, resolve

the error message before continuing. For Performance Center to utilize the

Controller properly, no error messages should be displayed during startup.

5 Create a new, simple load test and reference the scripts from the LRFS share

(on the Performance Center file server). Run the load test with one or two

users to verify that the Controller works.

Note: Scripts uploaded to the Performance Center LRFS reside in the

\\fileserver\LRFS\<ProjectID>\Scripts directory. To obtain the <ProjectID>,

select User Management > Projects.

The following is an example path to the USR file for a script named MyTest:

\\myserver\LRFS\2\Scripts\MyTest\MyTest.usr

6 Close the Controller (wlrun.exe).

7 From the Performance Center User Site, launch a simple load test.

➤ Check whether the following processes are displayed in the Task Manager

on the Controller host:

➤ OrchidActiveSession.exe OR ORCHID~1.exe

➤ WLRUN.EXE

➤ Check whether the Controller is displaying a dialog box that requires

user input before the Controller can proceed with the load test. Address

the reasons for the dialog box being displayed, and make sure that no

dialog boxes are displayed when re-running the load test from

Performance Center.

Examples of dialog boxes that may be displayed include License Has

Expired, Monitor Not Licensed, and Host is Over-Utilized.

If you are unsure how to resolve the problem indicated in the dialog box,

contact the Customer Support Web site (http://www.hp.com/go/

hpsoftwaresupport) for assistance. Note: When you are finished with this step, set wlrun.LrEngine back to

its original identity. By default, this is This User with the Performance

Center user name and password. If you used a different identity, restore

it.

Option 4: Reinstall Performance Center host on the host machine

If all of the above steps fail to resolve the problem, reinstall the Performance

Center host on the host machine.

1 Uninstall Performance Center (Start > Settings > Control Panel > Add/

Remove Programs). (This is really the Performance Center host.)

2 Delete HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive from the

registry.

3 Clean the Performance Center machine, as described in the section about

cleaning Performance Center machines in the HP Performance Center System

Configuration and Installation Guide.

4 Re-install the Performance Center host. For more information, see the HP

Performance Center System Configuration and Installation Guide. Make sure that

you install the same version of Performance Center as is installed on your

Web server.

Note: Do not install an Performance Center server (such as a Utility Server,

Web Server, or File Server) on the same machine as the Performance Center

host (such as a data processor, Controller, or load generator).