User files not transferred
I've been running into this issue intermittently (over the years) and it drives me nuts.
I have a script, it uses consumable data, and I'll run it for an hour with no issues. The script is checked out, the test suite which it runs under is also checked out.
After the test ends, I replace the data with a fresh batch and run it again. Most of the time with no issues.
Occasionally, I'll get in a funk where no matter what I try, when I go to run the test suite, all users error out with "the user files were not transferred to the load generator."
I'm aware of the "temp issue" environment variable and it's not that. I have no freaking idea what the heck is causing this. I know other team members experience the same issue every so often.
Seems like the solution is to create a copy of the script with a new name and use that but that's kind of ridiculous.
Anyone run into this and figure it out?
After a LOT of digging, I think I'm seeing a corrupt .prm file referencing an incorrect .dat file.
I wiped out the params, deleted the .prm file, recreated the params, recreated the dat file, no issues.
we had the same problem. its something to do with the 'parameter name' and 'parameter file name'. say you have userid as a parameter, and the filename is userid.dat that combination could cause corruption. for me the easiest way to fix the error is change the paramter name. (userid to (userid1 or username) and leave the dat filename as is.) this was the fastest way to fix the error.
Originally Posted by SteveO
Nice catch. I think I ran into that once.
A few years ago I ran into something similar. No matter what I did the files wouldn't transfer. Then I realized that I was storing my vugen scripts on the LAN. And the full path was really long, maybe over 300 characters. They ran fine in vugen, and fine in the Controller locally. But the Controller sending the scripts to other load generators? No go. And the error message gave no clue to what the problem was, which of course was the super long path.