Tips for replaying RDP VuGen scripts in BSM or LoadRunner

Tips for replaying RDP VuGen scripts in BSM or LoadRunner

If you’ve ever worked with RDP VuGen scripts, you’ll know it can be challenging to develop a reliable script.  This applies if you need to generate high load via LoadRunner RDP scripts for performance testing. It also applies if you need reliable RDP scripts over time as part of a monitoring solution using Business Process Monitors (BPM)s in HP BSM. Differentiating between false errors and real errors with RDP VuGen scripts can be time consuming and drive you insane.

Over and above writing a robust RDP VuGen script, here are some tips to more reliably run RDP scripts in either LoadRunner or HP BSM. We have successfully run 250+ concurrent RDP user tests with no errors using a combination of the below, even without the RDP agent using LoadRunner. There are a number of additional techniques to make RDP scripts more reliable but these are beyond the scope of this article.
Script Run-Time Settings:

RDP Synchronization Image Tolerance:

Set the default tolerance for image synchronization to Exact. This should be the global setting. You can relax the tolerance on a case by case basis in the rdp_sync_on_image function using "Tolerance= Medium" where tolerance can be Exact, Low, Medium or High.

RDP Synchronization Typing Speed:

Set the typing speed (msec/char) to at least 300 (msec/char). In some cases the script will still run faster in LoadRunner than you want it to, in which case you can try increasing the typing speed further.
RDP Server settings:

RDP-tcp Session Properties:

Set your Terminal Server settings to automatically end disconnected sessions after 1 minute. This will ensure that any disconnected/hung sessions are automatically logged out so the next user can pick up a “clean” session. If allowed also set Active and Idle session limits to Never. This will ensure there will be no limits to how long a user can be active or idle in the RDP session.

These options are found in Remote Desktop Session Host Configuration > Properties > Sessions Tab.

  • End a disconnected session: 1 minute
  • Set Active session limit: Never
  • Idle session limit: Never

Still having problems?

Connection Reset by Server Errors.During test execution on the LR Controller, you are getting the following error:-202930 xxx.c(xx): Error:Connection reset by the server



Generally this is a difficult error to find the root cause for but if you have a scenario with large think-time and/or pacing (minutes) and find that your vusers are failing with the above error, we suggest you try this first.

Increase the Socket receive buffer size (bytes) in Run-Time settings. This option is found under Run-Time Settings > RDP > Advanced > Socket receive buffer size (bytes).

VuGen has a description as follows:

The amount of bytes to allocate for the socket’s receive buffer. If the buffer is too small, it can fill up causing the server to disconnect. If the buffer is too large, it uses more local system resources (non-paged memory) and can slow system performance.



Tech tips from JDS

Posted by JDS Admin in Micro Focus, Tech Tips
Incorporating iSPI metric reports into MyBSM dashboard pages

Incorporating iSPI metric reports into MyBSM dashboard pages

Current BSM dashboards show limited capability of displaying NNMi iSPI Metric reports in any of the out of box NNMi Components.

With a bit of creative thinking we can overcome this limitation.

As MyBSM allows us to create a URL-based component, the main objective is to set up a reoccurring report schedule in iSPI Metrics and have the html report saved to a remote file system whilst maintaining a static file name. The report can then be published by IIS in which the MyBSM URL component can then reference. Let’s demonstrate how this can be done in the following high level steps.


BSM edit2

Step 1:

From the BI Configuration on the iSPI Metrics server, set up the remote File System where your iSPI Metric report will be saved. Note that SERVER_FS is a remote Windows server with Internet Information Services (IIS) activated and listening to port 80, and NPS_reports is a folder we’ve shared.


Step 2:

From the iSPI Metrics console which is cross launched from the NNMi console, go to BI Server -> Administration. Then navigate to: Configuration -> Dispatchers and Services. Click on the Define File System icon.



Step 3:

Define the File System Location by specifying a sub directory. In this example we want our report to be saved to the SampleReports sub-directory which resides under our shared folder called NPS_reports.


Step 4:

Create the report schedule for the desired report in iSPI Metrics. We have chosen the out of box “Report View Of Executive” report to be saved to the Sample Reports location we defined in the previous step.


Step 5:

Select the option to “Replace existing files” with the static file name we have chosen:


Note that iSPI Metrics adds a suffix of “-en-au.mht” to the Report name above when it’s actually saved to the file system.

This is what the report looks like when saved to SERVER_FS:


Step 6:

On SERVER_FS, we have defined our Virtual Directory where our html reports reside:


Step 7:

In BSM, we navigate to the MyBSM page and create a New Component. We supply the URL of the report we wish to publish.


Step 8:

Finally, verify the html report is viewable via MyBSM.


Tech tips from JDS

Posted by JDS Admin in Micro Focus, Tech Tips