teststand deploment exception

[glsimpson]

I'm getting an exception in labview.exe every time I try to build the teststand deployment. I can't find any references to this being a known bug with teststand so assume it is just my bad luck. Everything has always worked fine when the sequence is run from the development environment.

Starting a log for the deployment.
Starting Analysis
Processing Workspace...
Done processing workspace file
Finished Analysis
Building...
2:37 PM
Internal error code -2147023170 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
The remote procedure call failed.
 in TestStand - Dynamically Call Build VI Distribution LV 8 or Above.vi->TestStand - Call Build VI Distribution for Unique VI Hierarchies LV 8 or Above.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
The build process is done.
2:38 PM
Aborted
+++++++++++++++++++++++++++++++++++++++
 

 

[Raj_V]

This error is occurring because LabVIEW crashes when a VI attempts to execute. There could be multiple causes of this error, so we will need to do a little troubleshooting.

Are you attempting to call LabVIEW code modules in your sequence file? If so, have you verified that they all run properly independently of TestStand by opening them in LabVIEW and running them?

If the only VIs that appear to be broken are those that teststand uses behind the scenes, we may need to do a repair of your teststand installation, since these files may have been corrupted. You can do this by going to Control Panel >> Add/Remove Programs >> National Instruments Software >> Change/Remove. Then use the NI Software Installation tool to repair your TestStand installation.

[Anand_Jain]

Glsimpson,

What version of TestStand and LabVIEW (Is it 8.2 or 8.2.1) are you using?

Did you try mass compiling your source VIs?

It might help narrow down the specific VI that is causing LabVIEW to crash.

Regards

Anand Jain

National Instruments

[glsimpson]

I've tried mass compiling and repairing the labview and teststand installation and it hasn't helped.  I'm using labview 8.2 and teststand 4.2 .

[RayFarmer]

It's not only your source file that need mass compiling, it's also the VI components within the teststand areas.

By the looks of your error it seemed to be doing something with NIDAQ components. maybe this is the source of your problem.

Regards

Ray Farmer

[glsimpson]

After a couble more ties I fianally gave up on labview 8.0 and teststand.  After a clean install with labview 2009 I am finally able to run the deployment utility for my sequence file.  Now when I install on the deployment system, teststand uses the full development licence to run.  How do I get my simple deployed sequence to run with only the read only deployment license in place? There must be a checkbox somewhere in the deployment utility that I am overlooking.

[Raj_V]

The teststand sequence will run with the highest license currently available on the system. If you would like your sequence to use the base deployment license (for debugging purposes) as opposed to the full development license, you can deactivate the development license from license manager and your sequence will run using the base deployment license installed.