Hi,
The trouble with the Call Executable step type and the same with the labview version, you dont know whether control has been returned because everything was ok or not.
So what you might be seeing, running from Teststand, is it prematurely returning because your executable failed.
I have had to do tricks, like my executable creating a temporary file, then in TestStand, check for the presence of the file.
Have you tried running your VI from an action step rather than use the Call Executable step, to see if its more reliable?
Regards
Ray Farmer
Regards
Ray Farmer