Re: automating loadrunner start

Maybe you could start to debug this by printing out a bit more info, e.g.

system(@argv)==0 or die "Failed to execute Loadrunner (ret=$?): $^E";
[download]

(If I'm understanding you correctly, "I get a failed to start loadrunner message" is referring to this error message...(?))

Comment on Re: automating loadrunner start Download Code

Replies are listed 'Best First'.
Re^2: automating loadrunner start by grashoper (Monk) on Apr 22, 2009 at 21:03 UTC
I get this error failed to start loadrunner the system cannot find the file specified in gui.pl line 4 ret=256. I changed as follows and now I get a -1 (doesnt that mean its already running?) `use Win32::GuiTest qw(WaitWindow FindWindowLike SetForegroundWindow Se +ndKeys); use strict; my @argv=("E:\\MIBOR_TimingTest\\MIBOR\\MIBOR.usr"); system(my @argv)==0 or die "Failed to execute Loadrunner (ret=$?): $^E +"; #sleep 600; my @whnds=FindWindowLike( undef,"^Mercury Virtual User Generator"); if (!@whnds){ die "Cannot find window with title/caption Mercury"; } else{ printf("Window handle of Mercury is %x\n", $whnds[0]); } SetForegroundWindow($whnds[0]); SendKeys("{F5}");` [download]	[reply] [d/l]
Re^3: automating loadrunner start by runrig (Abbot) on Apr 22, 2009 at 21:08 UTC
`my @argv=("E:\\MIBOR_TimingTest\\MIBOR\\MIBOR.usr"); system(my @argv)==0 or die "Failed to execute Loadrunner (ret=$?): $^E +";` [download] No, you do not want that second "my".	[reply] [d/l]
Re^4: automating loadrunner start by grashoper (Monk) on Apr 22, 2009 at 21:09 UTC
oh right you are, that makes it a completely seperate variable doesn't it?	[reply]
Re^5: automating loadrunner start by runrig (Abbot) on Apr 22, 2009 at 21:11 UTC
Re^6: automating loadrunner start by grashoper (Monk) on Apr 22, 2009 at 22:14 UTC
Re^3: automating loadrunner start by almut (Canon) on Apr 22, 2009 at 21:26 UTC
cannot find the file specified in gui.pl line 4 ret=256 `$?` being 256 simply means the program exited with a return code of 1 (i.e. `$? >> 8`) — see system for the details. Whatever that means... hopefully you can find more about the circumstances under which this happens in the LoadRunner docs.	[reply] [d/l] [select]