LoadRunner unable to read file
Question ID: 107005

We are currently using LR 12.50. When running the scripts on the controller and using the load generator found on localhost the scripts are working correct. When the user changes the load generator from localhost to an external generator, sitting on a different server, we receive an error saying that the file D:\\…..\\file.txt cannot be opened. This file contains information needed by the script to execute. Does the load generator require access to the controller where the file exists at in order to execute this? I was under the impression the controller would handle this file? Any Input or suggestions would be great.

Marked as spam
Posted by (Questions: 108, Answers: 6)
Asked on July 29, 2016 2:52 pm
Answers (1)
Private answer

There are 4 methods that can be used to overcome this issue:

1. Copy the file.txt to the exact file path on all LG machines or
2. Add the file.txt to the script within VuGen or
3. Map a Drive from each Load Generator with the same path. Example: Each Load
Generator has a mapped ''X:scriptsdatastorefile.txt'' or
4. Use Virtual Table Server (VTS) for your Version of LoadRunner to handle external
data .

Also, HPE has stated the following Length restrictions:

* Parameter names - 64 characters
* Transaction names - 170 characters
* Action names - 64 characters
* Script names - 100 characters

Additionally, it is generally a good idea to keep to the DOS convention for naming scripts/results/scenarios/transactions and not to use any special characters and spaces in names. They can cause unexpected problems.

It would also be a good idea to not use reserved words like ''file,'' ''length,'' etc. for transaction names as it may cause compilation errors. Also do not name the Parameterization data file PID, con.dat, prn.dat or lpt*.dat (or any other system devices).

Marked as spam
Posted by (Questions: 159, Answers: 15)
Answered on July 29, 2016 2:54 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top