LabVIEW 8.5, TestStand 4.0, Wibdows XP-SP3
In the same VI, I've connected in parallel:
- a call to a System Exec, calling a program which may in some circumstances prompt for a user's answer (which will never come...)
- a while loop, managing a timeout which finally kills the program above in the case it waits infinitely for a user's answer
Just to be more precise: in my case the program is WinSCP, which prompts when you should accept a private key which is not in its cache; but the concern here is not WinSCP but LabVIEW.
Of course, I test it in a case where we are stucked in System Exec.
- This works fine when the VI is launched from LabVIEW
- When the same VI is called in a TestStand sequence step (ActiveX automation server to the LV development system), it does not run the while loop (we're stuck in both System exec and inside the loop). The only way to release everything is to manually kill (through Windows Task Manager) the program.
for information, all tasks: LabVIEW, TestStand (SeqEdit) and program (WinSCP) are 0% CPU and memory.is stable.
Have you an explaination for this unexpected behavior of the VI when called from TestStand ?
Enclosed is the VI; to run it, you might have WinSCP installed and a valid session to an accessible host (here named vhe-219), but you won't have put its key in the cache!
Note: you won't see the same issue with other programs or commands (e.g. netsh, ftp...) even if they await a user's prompt.
Thanks for your help!
