Blog

  • Enabling the new graphs in LoadRunner Analysis 9.51

    Posted on September 1, 2009 by Admin

    I have been wanting to check out the new Throughput graphs. HP Support released Knowledge Base Article #KM759621 on August 12, 2009. “How to use the new Throughput (MB) and J2EE/.Net Probe Metrics graphs that were added in SP1 for LR/PC 9.5.”

    In Performance Center, In addition to applying SP1 to the PC components such as Usersite/Admin site, Utiliy server, Hosts etc… You must apply the separate SP1 for Analysis Stand Alone.

    SP1 for LoadRunner 9.5 is required. You must also ensure that the Diagnostics Server is running the late Read Entire Entry

  • VuGen: Dynamic Transactions Created From A Parameter File

    Posted on August 28, 2009 by Admin

    From Michael Hendershot

    Based on the search item I choose, I want a different transaction. This pulls the transaction name from parameter file and generates the transaction name off the “SearchFieldTransaction” column in my parameter file. Be careful. Tree view will take the “tmptransactionname” out of the lr_start and lr_end transaction.

    Code:
    Action()
    {
    char tmptransactionname[25];

    sprintf(tmptransactionname,”%s”,lr_eval_string(“{SearchFieldTransaction}”));

    lr_start_transaction(tmpt Read Entire Entry

  • When LoadRunner Agents Crash

    Posted on August 17, 2009 by Admin

    The following files are helpful in debugging errors:

    Agent log file: agent.log or m_agent_daemon. This file is located in the temporary directory of the agent machine. It provides information about the connection errors.
    Bridge log file: lr_bridge.log. This file is located in the scenario’s temporary log directory (i.e brr_*\log). lr_bridge controls virtual users during scenario execution.
    Virtual user log files: ScriptName_VuserID.log.
    This file is located inside log directory found in scenario result directory.

    Here are Read Entire Entry

  • Error on LoadRunner 9.51 Installation

    Posted on August 10, 2009 by Admin

    A new knowledge base article is available on the HP Support side for LoadRunner 9.51. KM753044. If you get the following messages during installation:
    “Another instance of the program is already running.”
    and/or
    “Setup has determined that a previous installation has not completed. You should restart your system in order to complete this process.”
    It is possible this is coming from conflicting software. Software such as Tivoli or Radia installed on the system interfere with the installation of LoadRunner.

    The suggested fix:

    S Read Entire Entry

  • Does LoadRunner 9.51 support the Citrix Xen App Client?

    Posted on August 10, 2009 by Admin

    A recent knowledge base article was added on the HP Support site for LoadRunner 9.51. KM755736 now states:
    “Yes, LR 951 supports Citrix client 11.0. However, please make sure the registry patch is applied after this citrix client installation.”
    The patch adds a couple of keys to registry;

    [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Virtual Channels\Third Party\CustomVC]
    “VirtualChannels”=””

    [HKEY_CURRENT_USER\SOFTWARE\Citrix\ICA Client\Engine\Lockdown Profiles\A Read Entire Entry

  • LoadRunner VuGen: Make any SERVER or URL a Parameter

    Posted on July 30, 2009 by Admin

    From Michael Hendershot:
    // DEFINE VARIABLES
    char *appurl; // Variable To Hold URL Name

    // ************************************************************************
    // START – SELECT ENVIRONMENT TO RUN LOADTEST AGAINST BY UNCOMMENTING THE CORRECT ENVIRONMENT
    // ************************************************************************

    //appurl = “server_url:9999”; // Application #1
    appurl = “server_url:1111″; // Application #2

    // CONVERT URL TO PARAMETER TO USE IN URLS BELOW
    lr_save_string(appurl,”p_Url”); Read Entire Entry

  • LoadRunner 9.51 Analysis Bug – Renaming Titles

    Posted on July 20, 2009 by Admin

    Today I had to open a ticket with HP Support concerning the Analysis module. I had a graph where I wanted to show the CPU utilization across multiple servers to see how hard each one was working. This could give me an indication of whether or not load balancing was throwing the right amount at each server.

    To illustrate this, I selected the Processor Utilization for each server in the farm (there were three), and then decided to make it pretty by going into advanced options. One of the things I wanted to do is show the legend at th Read Entire Entry

  • LoadRunner VuGen: Determine if an iteger is odd or even

    Posted on June 22, 2009 by Admin

    Today’s code comes to us from Anthony Lyski:
    “I ran into an issue today where I needed to know id an integer was an odd or even number. I found that this is a very effective way to determine. I put this code in a ‘for’ loop so you can see how it works over a range of numbers.”
    int i;

    for (i=0;i<100;i++) {
    if (i & 1){
    lr_message(“%d is odd”, i);
    }
    else{
    lr_message(“%d is even”, i);
    }
    } Read Entire Entry

  • Programmatically Create A Unique Parameter Name

    Posted on June 11, 2009 by Admin

    Lets say you need to grab a list of items or numbers from a web page, such as GUID’s. These are not dynamic numbers, but will be used in a script as parameters. Here is how I captured the data I wanted and created my own DAT file:

    Figure out the format you want the DAT file to be in. For me, this was a GUID, another GUID, and a user ID. I created a file and put the top line in with the headers GUID1, GUID2, LOGIN and saved it to my C: drive in the root folder. I already knew the login so I had already set this up a a paramet Read Entire Entry

  • MI Listener: Additional Trace Logs For Debugging

    Posted on June 3, 2009 by Admin

    Did you know there is a deeper level of logging in the MI Listener Aganet? The following can be done if you are having problems with the MI_Listener and the Generator to determine connectivity issues.

    kill the agent processes on all the machines
    append to [launcher] section at launch_service\dat\mdrv.dat the following line:
    ExtCmdLine=-drv_int_msgs -drv_log_flush

    Activate agents on all the machines and try to connect.
    collect log file generated (%TEMP%\LoadRunner_agent_startup.log).

    You will need these logs when submi Read Entire Entry