Highlighted
Absent Member.
Absent Member.
1841 views

Loadrunner

Running a LoadRunner scenario results in one or more vuser groups receiving the following error messages:

• Error: The user files were not transferred to the local load generator
• One or more of the script's files have illegal names.
It is possible that two files are using the same name and directory.

This problem can occur when script development is part of a team effort under the following circumstances:

A script using a file parameter is created on one workstation. Later another team member, working from a different workstation, opens the script for editing. The second team member opens the parameter list, adds a new parameter to the file, and links this parameter to another parameter in the file using “same line as”. Both developers use the same network drive for the location of the script and data files. However one developer uses, say all capital letters, in mapping the network drive to a drive letter while the second developer uses all lower case. This results in a parameter definition file (.prm) like the following:

[parameter:Param2]
Delimiter=","
ParamName="Param2"
TableLocation="\\server1\LoadRunner reference\Knowledge Base\Illegal File Names Error\Data"
ColumnName="Param_2"
GenerateNewVal="EachIteration"
Table="Param_1.dat"
Type="Table"
value_for_each_vuser=""
OriginalValue=""
auto_allocate_block_size="1"
SelectNextRow="Same line as Param1"
StartRow="1"
OutOfRangePolicy="ContinueWithLast"
[parameter:Param1]
Delimiter=","
ParamName="Param1"
TableLocation="\\SERVER1\LoadRunner reference\Knowledge Base\Illegal File Names Error\Data"
ColumnName="Param_1"
Table="Param_1.dat"
GenerateNewVal="EachIteration"
Type="Table"
value_for_each_vuser=""
OriginalValue=""
auto_allocate_block_size="1"
SelectNextRow="Sequential"
StartRow="1"
OutOfRangePolicy="ContinueWithLast"

Note that in the first instance of “TableLocation=\\server1\...” that “server1” is all lower case. In the second instance it is all upper case. When the script is added to a scenario, and the scenario gets run, the above error message results.

Solution:

If the file is manually edited so that the case agrees in both instances, and the script refreshed in the scenario, then the next time the scenario gets run, the error will not occur.
0 Likes
2 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Sounds good - if you close this message as "solved", this will help others.
0 Likes
Highlighted
Absent Member.
Absent Member.

OR you can just copy the whole script directory to a new location,

OR you can open the script then "save as" in a different location and delete the script from the original location

Thanks
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.