05-05-2013 10:42 AM - last edited on 09-21-2013 08:23 PM by maikoro
LR Version 11.52.
OS: windows Server 2008 R2 Standard
Getting the below errors on the controller.
1.Error: The user files were not transferred to the local load generator
2.The file C:\LR Scripts_09977p\V5_NBCU_Perf_PO Save_Same Accounts_G0BU\PO Save same Accounts_G0BU.c which is part of script v5_nbcu_perf_po save_same accounts_g0bu.1 cannot be found
For the 2nd issue, I follwed the steps mentioned in th knowledge document KM172825, but no use. when I looked under the file file was there.
This is a roadblock for me.
For the 2nd issue.
To verify the files that will be transferred to remote machine:
1. From the Controller, select a group, and click on "Details."
2. In the "Group Information" window, expand "More."
3. Go to the Files tab.
4. Check the list of files listed. Make sure that the file(s) mentioned in the error message are listed. If not, add them as necessary.
Please advise me!
P.S. This thread has been moevd from Performance Center Support and News Forum to LoadRunner Support Forum. - Hp Forum moderator
05-06-2013 11:39 AM - edited 05-06-2013 11:40 AM
Please refer to the KM902643
When running VuGen scripts in Performance Center and the following error appears: "Error: The user files were not transferred to the local load generator."
The controller cannot transfer the script files to the Load Generator. When running a scenario in LoadRunner Controller / Performance Center, the Controller transfers the Vugen script files to the temporary location on the Load Generators. The temporary location will be created under <the load generator's temporary directory>\<brr folder>\netdir\<Path to the results folder on the controller>\<results name>. For example, if the script in Controller is stored in c:\VugenScript\Script1 and the Load Generator has the temporary folder set to C:\Documents and Settings\Default User\Local Settings\Temp, the Load Generator would save this script file in C:\Documents and Settings\Default User\Local Settings\Temp\<brr folder>\netdir\c\VugenScript\Script1. This is caused by a limitation of the maximum path length on Windows OS. The length limitation is 255 bytes in Windows XP and 260 bytes in Windows Vista. Please refer to MSDN: File Names, Paths, and Namespaces(http://msdn.microsoft.com/en-us/library/aa365247(V
On the Load Generator: A. If you are running the agent as a process, you can change the "TEMP" system Variable of the user from C:\Documents and Settings\Default User\Local Settings\Temp to C:\Temp. The procedure is listed under KM172893 B. If you are running the agent as a service, you can change the service to use an account with Administration privileges, and change the admin account's "TEMP" system variable to a shorter path: - Go to Start -> Control Panel -> Administrative Tools -> Services.
- Look for the LoadRunner / Performance Center Agent Service.
- Right-click and select Properties->Log On, changing this from "Local System account" to "This account", supplying the Administrative account username and password.
- Follow the procedure from KM172893 to change the admin user temporary location.
09-16-2013 10:08 PM
All those KB's will be in support.openview.hp.com ; you need to have a registered sign-in and valid SAID for accessing those cases.
09-16-2013 11:15 PM
Please guide... I have a valid user ID .. http://support.openview.hp.com/ In the search box on the top I gave KM172893, the search results says
No results for 'KM172893'
03-31-2014 02:44 AM
another problem can be the disk space. I had this error with one of my run, and the paths were good, and the user too. But the disk of one of the injectors was full. after clean it, the run works.
03-31-2014 07:29 AM
I ran into a similar issue once. Turned out that the path to the scripts on the shared drive was too long and LR simply wouldn't handle it, I got a similar error message. Unfortunately the the error message didn't say that the problem as a too long path. That took a while to figure out.
05-07-2014 02:52 PM
I got this error when I created a scenario by copying an existing scenario and making a duplicate of it.The test scenario is corrupted.
I Created a new scenario from the scratch and the issue was fixed.