File Transfer Errors during initialization in LoadRunner Controller

File Transfer Errors are very common during initialization of load test with LoadRunner. It can be because of following reasons.


1. There may be situations where some of the runtime files of the script are not included by the controller while transferring files to different load generators (may be a bug in controller). It may not transfer all the files required for the script to run successfully. Under those situations if the scripts give compilation errors in different load generators other than local host then manually add the missing files using Add button shown in the snapshot below.

Controller Group Information

 
 
 
 
 
 
 
 
 
 
 
2. If the Length of the script name is too large then LoadRunner will throw error messages like below


Error: Mercury File Transfer error: Cannot create file C:\Documents and Settings\autodesk-admin\Local Settings\Temp\brr_mYv.195\netdir\C\Performance_Test\QAAutomation\Performance\LR\Stage\700ExodusSFDC\CallCenter\CC_SFDC_CreateGSSRequest_fromContactScreen_Attachment\CC_SFDC_CreateGSSRequest_fromContactScreen_Attachment.prm. Reason : Check the file path for illegal characters or length.

To double check if the length is the issue, go the LoadGenerator and try to add the file in the specified path. You may get the error as below

Error Copying File

Integrating Sitescope Monitor with Controller

To integrate a SiteScope server that needs authentication, modify the modify the LR installation folder\dat\monitors\xmlmonitorshared.ini file as follows:

1. Locate the [SiteScope] section in the file.
2. Append &account=administrator, or if you want to log in using other user (e.g., XXX), append &account=XXX, to the MetricListURL.

Note:

The user XXX must have the right permissions in SiteScope and may be different from the user name. The SiteScope server should be accessed as

http://sitescope:8888/SiteScope?account=XXX.
3. Add "QueryLoginInfo=1" at the end of the section.

With this, you should be able to see a login window when adding measurements.

How to reduce the amount of threads per process in LoadRunner

In LoadRunner 9.x, please perform the following steps:


1. Go to the /dat/protocols/QTWeb.lrp file.

2. By default, in web protocol the number of threads mdrv can spawn is 50. Change this value to a lower value (E.g. 15) by adding/changing the following:



[VuGen] //Add below entry if not availble
MaxThreadPerProcess=15

3. Re-run the scenario

Source: HP