error code: 7 during TS deployment build

[John_N]

Hi all,
I ran into this the following error code while trying to build a deployment image:

Error Code:7
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in ABAPI Save Libraries New Dest.vi->ABAPI Dist Build LLB Image.vi->ABAPI Copy Files and Apply Settings.vi->TestStand - Build VI Distribution 8 AX Wrapper.vi->TestStand - Build VI Distribution 8 AX Wrapper.vi.ProxyCaller

I checked out the "ABAPI Save Libraries New Dest.vi" to debug the problem, but the run arrow is not broken, indicating that VI is runnable.  Also, I don't have access to see the block diagram for that VI anyway (I'm prompted for a password when trying to access it) which makes sense because it's an NI VI.  Any help is greatly appreciated!
Thanks,
-John

[John_N]

Sorry, forgot to mention I'm using TS 3.5 & LV 8.2.

[RayFarmer]

Hi,

The problems is not in the distribution VI's, but in your own and is probably due to VI's being at different versions.

Mass compile all the VI's including the TestStand directory and then try again.

Hope this helps.

Regards

Ray Farmer

[John_N]

Ray,
    Thanks for the advice!  I recompiled just the TestStand 3.5 directory and the error vanished.  The weird thing is that I did not have to mass compile my VIs (that was the first thing I did to attempt to fix the error).  According to the "Distributed Files" tab in the deployment utility, the only files being added to my deployment from the TS directory are: FrontEndCallbacks.seq, StationCallbacks.seq, CustomStrings.ini, and MyTypes.ini, which makes me wonder why mass compiling the TestStand directory helped at all since all of my VIs are located outside of the NI directory. Anyway, thanks so much for your help!
-John

[RayFarmer]

Hi John,

It could be that some component was still linked to a VI or ctl in the TestStand\API\Labview folder.

Anyway, a mass compile does usually sort the deployment build problems..

Glad you sorted it and the bit of quick thinking reduced you mas compile time.

Regards

Ray Farmer

[John_N]

Ray,
    Compiling the TestStand directory does not appear to be a proper cure for the problem.  I found myself recompiling the TS directory every time I rebuilt the deployment installation or I would continue to get the error even without any changes to any VIs or sequences (mine or NIs).  I started a new build from scratch, and from this build I get the same error, but now mass compiling does nothing!
    I started playing around with the distributed files to see if i could track down a sequence or VI that could be causing the problem and found something odd:

1) Imagine I have sequence Test.seq calling A.vi, B.vi, C.vi, D.vi, E.vi
2) Let's say I run into that error when I include all of those VIs
3) When I remove say, B.vi and C.vi, the error dissappears
4) When I look into B.vi & C.vi I noticed that the VIs have a subVI that calls "Invoke Node" which takes a reference from the Sequence Context.
5) Here's the catch: When I make a new build with a sequence calling B.vi & C.vi, I get no error!

Any suggestions on how to tackle this problem?
Thanks for your time!
-John

[John_N]

Hmm....
I just tried a few different configurations for deployment builds.  In a few cases, unselecting the "Create Installer" option got rid of the error... I'm trying a few more things on my side before I call this a bug.
-John