Error -18002 with TestStandLVRTS

[Ken Pietrzak]

I'm trying to find ways to speed up my sequence. I'm using TestStand 2.0.1 with LabVIEW 7.1. I read that using the run-time server as an adaptor is more efficient than using the development environment. Is this true by the way? Also I want to test this to see if LV is needed to run the sequence on customer computers. The sequence runs fine with the LabVIEW adaptor. When I switch to TestStandLVRTS, I immediately get a -18002 error on the first step. It's an error loading the step: The VI is not executable. I've tried the following based on suggestions listed in the forums:

1. Recompiled and rebuilt TestStandLVRTS to LV 7.1
2. Mass Compiled the entire TestStand directory, LabVIEW 7.1 directory, and my code.
3. Changed any absolute c
alls in the sequence to relative calls.
4. Moved my VI code structure and the sequence to the same folder as TestStandLVRTS.
5. Ran TestStandLVTRS to register the program before opening the sequence.

Does anybody have any other suggestions?

Thanks

[SarahM]

Hey Joe,

Do you get this error with any sequence or just the first step of your sequences. One suggestion would be try a very simple sequence with one step that calls 1 VI without any subVIs.

Are you running the sequence from the sequence editor, the LabVIEW operator interface or some other environment? If you're running it from the LabVIEW operator interface you should use the TestStandLVGUIRTS activeX server. The following KnowledgeBase gives more information:

Do I Need to Compile My LabVIEW VIs called from TestStand into Executables when Distributing My Test System? 

Have you seen the following knowledgebase? From your post it seems you've tried these
suggestions already but you may want to double-check.

Why Do I Get Error -18002 "VI is not executable" with TestStand? 

If you're concerned about efficiency then you might want to try LabVIEW DLLs. Please refer to the following knowledgebase:

Can I Improve TestStand Performance by Using LabVIEW DLLs instead of LabVIEW VIs? 

[SarahM]

Hey Joe,

Do you get this error with any sequence or just the first step of your sequence. One suggestion would be try a very simple sequence with one step that calls 1 VI without any subVIs.

Are you running the sequence from the sequence editor, the LabVIEW operator interface or some other environment? If you're running it from the LabVIEW operator interface you should use the TestStandLVGUIRTS activeX server. The following KnowledgeBase gives more information:

Do I Need to Compile My LabVIEW VIs called from TestStand into Executables when Distributing My Test System? 

Have you seen the following knowledgebase? From your post it seems you've tried these
suggestions already but you may want to double-check.

Why Do I Get Error -18002 "VI is not executable" with TestStand? 

If you're concerned about efficiency then you might want to try LabVIEW DLLs. Please refer to the following knowledgebase:

Can I Improve TestStand Performance by Using LabVIEW DLLs instead of LabVIEW VIs? 

I hope this helps!!

Regards,

Sarah Miracle
National Instruments