Test Stand Deployment; Internal Error Code 1

[CobhamDC Blackburn]

Hi,

I get the following message from the deploymeny tool when trying to deploy my system...

Internal error code 1 Processing VIs...
An installer was not created due to an error

I have mass compiled everything and all the VIs are working, my workspace processes okay and the sequences run okay in the Run time Engine adaptor of Test Stand.

Any ideas what could be causing this? I have Test Stand 4.0.0 and labview 8.5.

Many thanks

Matt

[Rick_Francis]

Matt,

There are a few possibilities- could you check the DeploymentUtility.log file in the TestStand\cfg directory to see if there is any more information on the error?

-Rick Francis

[CobhamDC Blackburn]

Hi Rick, see below cut and paste from this file, does this help?

08:55:43:Starting Log.
08:55:45:Starting Analysis
08:55:45:Starting to process workspace file
08:55:56:Done processing workspace file
08:55:56:Finished Analysis
08:55:57:Building...
08:55
08:57:01:Internal error code 1 Processing VIs...
08:57:01:Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Error copying files.
Source:
Destination: <Not A Path>

Librarian Path Location.vi
<Call Chain>Error 1 occurred at ABAPI Dist Copy Non-VI Files.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

Possible reason(s):

LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488:  Command requires GPIB Controller to be Controller-In-Charge.
08:57:01:An installer was not created due to an error
08:57:01:The build is finished
08:57
08:57:01:Aborted
08:57:01:---------------------------------------

Many Thanks

Matt

[Rick_Francis]

Matt,

Given there error code and location I suspect that there is an invalid path somewhere in your VI hierarchy.   I've seen a similar problem before with the LV Properties-> Documentation -> Help Path.   This path isn't used by the VI unless you try to bring up help so the VI will run if it is bad.  However, deployment can error out as they try to copy the the help file.   

I would suggest trying to narrow down which VI causes the error.  Start by picking half your source VIs add them to a workspace and deploy that workspace.  If that half doesn't shows the error then the error should be in the other half- try it out to be certain though!  When you see the error in your subdivision then subdivide that set of VIs in half again and find which half gives the error.   Note that once you are down to 1 top level VI you can divide all of it's subVIs into two sets and narrow it down further.

This process is the most efficient way to narrow down the problem- each step removes half of the VIs.   Using this method you could narrow a set of 1024 VIs to a single VI in ten steps.   Once you have it narrowed down to a single one of your VIs, you can post that VI and I can do further debugging to find the underlying problem.

-Rick Francis

[RayFarmer]

Hi Rick,

Good suggest but its a shame the deployment code did report the actual VI it had the problem with rather than report the error of the VI that was executing. After all it must know what VI its processing.

Regards

Ray Farmer

[RayFarmer]

Hi Rick,

There are a load of VI's in the Tools \ Deployment Utility folder but is there a complete set to re-build the deployment utility.exe, as there appears to be no project file or older build script file?

Regards

Ray Farmer

[0044]

Hi Ray/Rick

I’ve been working with Matt on this and we have managed to narrow the problem down to two VIs which both use .NET sub VIs.

The application runs fine in both runtime and development environment using LV8.5 and TS4.0.1 and previously been deployed using TS3.5 deployments tools. However the problem started since we upgrade to TS4.0.1, any suggestions?

[Anand_Jain]

Hi

Can you please post a simple example (VIs, sequence file, etc) that reproduces the problem.


Thank you
Anand Jain
National Instruments


Message Edited by Anand Jain on 04-04-2008 09:47 AM

[Rick_Francis]

Ray,

We do have the full source but we don't ship it, just like we don't ship the the source to the TestStand engine, sequence editor, LabVIEW etc.  If National Instruments ever adopts an open source policy then we would... was there a particular problem you want to solve?

-Rick Francis

[Rick_Francis]

>I’ve been working with Matt on this and we have managed to narrow the problem down to two VIs which both use .NET sub VIs.

>

>The application runs fine in both runtime and development environment using LV8.5 and TS4.0.1 and previously been deployed using TS3.5 deployments tools. However the problem started since we >upgrade to TS4.0.1, any suggestions?

This doesn't seem to be a familiar problem- if you could post an example VI I can debug it here and find out what is happening behind the scenes.  When it was working with TS3.5 was it also using LabVIEW 8.5.0 or some other version of LabVIEW?

-Rick Francis