NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand Deployment: "Save Modified VIs?" problem.

Has there been any resolution to this??

 

I am using LV 2011, TS 2010 SP1, same issues building a deployment.

0 Kudos
Message 31 of 33
(932 Views)

I'm working with a similar issue right now. I just wanted to add some insight. First, including the TestStand Engine in a deployment automatically includes LabVIEW Run-Time Engines. These can be seen in the Installer Tab by clicking the Engine Options button or the Drivers and Components button. These issues seem to all be related to files in the LabVIEW vi.lib, user.lib, or instr.lib folders. One workaround was limiting the deployment to include only one version of the LabVIEW Run-Time Engine. Still working on other solutions, but I will post if I figure anything else out.

Taylor B.
National Instruments
0 Kudos
Message 32 of 33
(792 Views)

Mass compiling the vi.lib folder allowed the build to be successful. The person I was working with had LabVIEW 2012 SP1 f5, and I wonder if not all VIs were updated to the latest patch. It's hard to say, but a mass compile of the vi.lib folder cleared up the issue. This probably also the case is the error is in the user.lib or instr.lib folders.

Taylor B.
National Instruments
0 Kudos
Message 33 of 33
(783 Views)