Teststand Error 7

[davidpcl]

I'm getting a strange error when building a Teststand distribution - I've looked at all the other posts relating to the error code I'm getting which seem to suggest that I've got a file missing, but nothing that quite matches the error that I've got :-

Processing Workspace...
Done processing workspace file
Beginning build process, please wait.
09:38
An installer was not created due to an error
The build is finished
09:40
Error Code:7
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Dist Cmp Settings to Disk Hier.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller
+++++++++++++++++++++++++++++++++++++++

Anyone got any ideas?

D Clark

[RayFarmer]

Hi,

Its a very mis-leading error, what it means is there is a problem with your set of VI's. Not an error with "TestStand - Dist Cmp Settings to Disk Hier.vi" which is part of the Distrubition Kit.

Try mass compiling all your vi's and llb's you are using, also don't forget the VI's in the TestStand folders as well. Check all the dynamically load VI's as well.

You could try running the TestStand Distribution with this vi open encase you can get any extra information front he front panel during it runtime.

What this VI should tell you, is which VI it had the problem with, after all it will have that information available. Unfortunately the "TestStand - Dist Cmp Settings to Disk Hier.vi"  is locked so you can not make any changes to it.

Hope some of this helps

Regards

Ray Farmer

[davidpcl]

I've managed to fix this problem - I've found out a number of things about what Teststand does and doesn't like when building files into a distibution. I've been building the distribution just by using the file view in the top level workspace. The first thing is that it doesn't like seeing .ctl and .lib files in the list - it's fine to have these called by a top level .vi or sequence but actually in the files list - doesn't like it at all. In fact it seems that a  general rule for creating an installer using Testand is to only include in the file list top level sequence files, and Labview vi's and let Testand do the task of finding all the subvi's, ctl's and librarys.

[TSVA]

I am getting a similiar error as you did but while MASS compiling I get the following errors as well.  Any insight? I am using TS 3.1 and LV 7.1

thanks

Starting Log.
Processing Workspace...
Done processing workspace file
Beginning build process, please wait.
11:36 PM
An installer was not created due to an error
The build is finished
11:36 PM
Error Code:7
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Dist Cmp Settings to Disk Hier.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller

#### Starting Mass Compile: Wed, Apr 04, 2007 11:36:59 PM
  Directory: "C:\Program Files\National Instruments\TestStand 3.1\AdapterSupport\LabVIEW\TestStand - Create Express VI Wrapper.llb"
CompileFolder: error 8 at C:\Program Files\National Instruments\TestStand 3.1\AdapterSupport\LabVIEW\TestStand - Create Express VI Wrapper.llb
#### Finished Mass Compile: Wed, Apr 04, 2007 11:36:59 PM

[mrbean]

I am trying to build an installer (wia the TestStand Deployment Uitility).  My workdspace has changed many times to try and figure out what I'm doing wrong, but the attached .png is the latest attempt (it's actually a merge of the TestStand Workspace, and the output of the Build)

I have seen Error Code 7 many times, but right now, I'm seeing Error Code 1055.  I WAS including (in the workspace) some of the source files, but now I just have the sequence files.  I have customized the sequential model (TS40_Sequential...) and the reportgen_html.seq.  I listed some other sequence files, as I wasn't sure if the deployment would find them on their own.

I first started out with a LabVIEW project and found many, many conflicts, which I resolved.  However, the deployment obviously has a mind of its own.  Any ideas on where to start on something like this?

[herosphro]

mrbean,

As you have probably noticed deployment errors are hard to diagnose.  If the error message gives us any information we can use that to narrow down the scope of the problem, but even this is not always helpful.  The only information I can find on that particular error deals with LabVIEW versions 8.2 and older working with TestStand.  Since you mention you are including just the sequence files in this deployment, I think that this is probably not applicable information.  Do you have the error information for this particular error (I couldn't find the actual error message)?  Also you mentioned attaching a picture of your workspace but it doesn't seem to be in your post.

In general, if we can't ascertain where/why we get an error from the error message, we are basically left with trying to divide and conquer to find the problem section of our deployment.  As you mentioned we could try to eliminate the LabVIEW code, or only include some sequences in our deployment to eliminate those as problems.  Hopefully by testing the code in parts we would be able to find the source of the error, and repair that code.