Unable to launch 'TestStandLVRTS.application' ActiveX automation server

[Papaiah K.]

When running the excutable built using the TestStand3.1 deployment package, following error is occuring:

Exception occured in TSAPI error loading step'set UUT Globals' of sequence 'Main sequence' in Final Test.seq. Unable to launch 'TestStandLVRTS.application' ActiveX automation server.

We use TestStandLVRTS AciveX automation Server for distribution the application. Any help or suggestions are highly appreciated.

Regards,
Papaiah Kummari

[AllanS]

Papaiah,

First, do you get the error on your target computer design computer or both? Next in your workspace after you have inserted all the code modules? Do any of them have red Xs on top of them? If they they are not linked correctly, denoted by the X, this error can occur. Let me know and we will go from there. Have a great day!

Allan S.
National Instruments

[Papaiah K.]

Allan,

While packaging the Modules, there are no errors (red check boxes)in either destination window, source window or work space window of distributed file. I am verifying the distribution package on the design system. All the source code works fine in development environment.

Here is another observation, when I chage the Adaptors on TestStand from development environment to other executable "TestStandLVRTS" I am getting the following error on the design system.

Unable to launch the 'TestStandLVRTS.application' ActiveX automation server. Error code -18001, An error occured accessing the LabVIEW activeX automation server.

I am thinking does my development system has any installation problem? I'm in little hurry to finish this packaging, If you can give a call at 714 466 1635 I would greatly appreciate, or if you give me your contact number anf best time to call, I can do so.

Regards,
Papaiah kummari
Sr. Test Engineer
Powerwave Technologies
Ph: (714)466 1635

[Papaiah K.]

Allan,

While packaging the Modules, there are no errors (red check boxes)in either destination window, source window or work space window of distributed file. I am verifying the distribution package on the design system. All the source code works fine in development environment.

Here is another observation, when I chage the Adaptors on TestStand from development environment to other executable "TestStandLVRTS" I am getting the following error on the design system.

Unable to launch the 'TestStandLVRTS.application' ActiveX automation server. Error code -18001, An error occured accessing the LabVIEW activeX automation server.

I am thinking does my development system has any installation problem? I'm in little hurry to finish this packaging, If you can give a call at 714 466 1635 I would greatly appreciate, or if you give me your contact number anf best time to call, I can do so.

Regards,
Papaiah kummari
Sr. Test Engineer
Powerwave Technologies
Ph: (714)466 1635

[AllanS]

Are you making sure that you include the TestStandLVRTS in your deployment package? If you are not go into the TestStand\Components\NI\Runtimeservers\LabVIEW and use the build script to rebuild the TestStandLVRTS.exe. Next, make sure you include this in the deployment package. If after deployment you still recieve this error make sure that TestStandLVRTS is resident in memory. I hope this helps please let me know if it doesn't and we will go from there.

Allan S.
National Instruments

[Papaiah K.]

Allan,

I installed the TestStand3.1 in repair mode and rebuilt the TestStandLVRTS.exe, now error is not popping up when Labview full featured operator interface is launched. However I am not sure how to distribute Labview runtime server.llb along with Teststand distribution. Can you send me the procedure to do it.

Thank you
Papaiah Kummari
pkummari@pwav.com

[Papaiah K.]

Allan,

After building the sequence files using TS3.1 deployment package, If I run installer on the development System and use the Labview full featured operator interface with adaptor set to TestStandLVRTS and serach directories set to the installed locations, I can reun the sequence. Same thing is not working on a Target mechine that doesn't have development environment, it gives following error:

Error loading step 'Set UUT Globals' of sequence 'Main Sequence' in Final Test.seq. Unable to launch the 'TestStandLVRTS.Application' ActiveX automation server.

At this point I have Labview vi ( TestStand - LabView Runtime server) running with message 'Server built with Labview 7.1. Since I don't know how to distribute the Labview Runtime server.exe, I copied the exe manually on to the target machine.

With Labview7.0 and TestStand3.0 I could build the executable and deploy easily on to the taget system, why is this happening with latest versions. On the development machine, when I run TestStand in 'TestStandLVRTS' mode why is the TestStand - LabView Runtime server vi running on the desktop, it was not the behaviour with TS3.0 and LV7.0

Do you think you can give me a call, that way we may be able to resolve the issue faster.

[AllanS]

Starting in TestStand 3.1 you can change the LabVIEW Adapter to run on the LabVIEW Runtime engine then you will not need to worry about TestStandLVRTS.

If you do not wish todo it this way then make sure that you VIs and server.llb are compiled in the same version of LabVIEW. Therefore mass compile both to one version to be sure.

If you would like to discuss your issue over the phone you can generate a service request at this page.

http://sine.ni.com/apps/we/niae_asc.main

Let me know if any of the suggestions help and we will go from there.


Allan S.
National Instruments

[Papaiah K.]

Allan,

I ran the deployment utility using LabVIEW runtime 7.1 after mass compiling the code. On the developemnt machine, I installed the software that was packged using deployment utility, changed the search directory to new installed location. I could run TestStand LabVIEW Operator interface, opeen the sequence and execute. However when I install the sofware on the target machine, it come with a messafe cannot open a step in the sequence, vi may not be executable. At this point I have Labview 7.1 Runtime set as adaptor and search path is set correctely on the target machine. Any ideas please....

Regards,
Papaiah Kummari

f.y.i I requested for phone support, tomorrow I'll make a call to at the number given.