TestStand Deployment: "Save Modified VIs?" problem.

[Manooch_H]

Gitanjali -

If you look at the Status Log that you provided, the TestStand Deployment Utility informs us that it is unable to find some of the subVIs of your top-level VIs (VIs called from TestStand or VIs added to the workspace). In TestStand 2010, we made an effort to provide more information in cases where this error arises. You'll notice in the status log that we provide a call chain for the missing VIs (give the name of the VI that is calling the VI that can't be found, followed by the name of the VI that can't be found). You'll also notice that after the call chain information, we provided the paths of the VIs that are calling the missing VIs and the path where we expected to find the missing VI, but couldn't.

In troubleshooting this, you can open one of the calling VIs in LabVIEW and see if you receive a warning about re-linkage of subVIs within the VI, or see if the VI is modified upon opening it. For example, you can open the BKVSP_GPIB_Close.vi from C:\Program Files\National Instruments\LabVIEW 2010\instr.lib\BK VSP GPIB\BKVSP_GPIB_ Close.vi and look to see if it's able to find the BKVSP_GPIB_Error Query.vi. If it finds it, find out where BKVSP_GPIB_Error Query.vi is being pulled from and see if it is a different directory than <instrlib>:\BK VSP GPIB\BKVSP_GPIB_Error Query.vi.

You should try mass-compiling the following directories:

LabVIEW instr.lib directory

LabVIEW user.lib directory

C:\Projects\DCTT

Also, I noticed that some of the TestStand Utility VIs are being located in <userlib>:\Deere\TestStand\ directory. The TestStand Utility VIs should be located in the LabVIEW\vi.lib\addons directory. The best practice is to call the TestStand Utility VIs from that directory as the Version Selector places the correct versions of the Utility VIs in that directory when a version of TestStand is made active.

Hope this helps.

[eric.atherton]

Attached are 2 screenshots that I have, one (NoLoad) that shows that TestStand did not load my VI because it could not find a VI.  The second screenshot (Load) shows that TS can now load my VI by simply removing the "Simple Error Handler.vi".  Many of my VIs are now dependant on error.llb and will not load into TestStand.

Will a recompile of vi.lib help me at this point?

[Manooch_H]

Eric -

Can you provide a screenshot with your mouse over the error provider (red circle with exclamation mark) in the LabVIEW Module tab? Have you tried mass-compiling the VIs that you call from TestStand? You can try first mass-compiling just one of the VIs that are showing this problem, then see if TestStand can load it. Before mass-compiling, be sure to make sure that none of your VIs are read-only.

Please let me know the outcome of this troubleshooting step.

[eric.atherton]

Manooch,

Since this is a different issue than posted here, I have posted it as a separate problem:

http://forums.ni.com/t5/NI-TestStand/Unable-to-load-LabVIEW-VI-into-TestStand-using-LV-Run-Time-only...

The new issue deals with the VI not loading into TestStand, whereas this thread is about the TestStand distribution tool not working properly.

[kewsvnet]

Hi Guys,

I have been having a similar problem.

I am using Labview 2011 and TestStand 2010 SP1.

I have already mass compiled the project, as well as TestStand and Labview folders with full Admin rights. I do get a number of warnings when mass compiling labview and teststand VIs saying that it could either not find some or they are read-only.

When doing a build using the Deployment Utility in TS it tells me that an error occurred possibly because some VIs are not saved in current version and asks me to save them.

After clicking yes, it brings up a list of VIs that need saving.

Clicking save it brings up another message saying 'Cannot load diagram of "Clear Errors.vi"', and the only option I have is to 'Cancel Save'

I do not understand why it seems to think there VIs which are not in the current and asks me to save them even after I have mass compiled all that I can.

Also why can it not load the diagram of "Clear Errors.vi" which I have been able to open in LV just fine and it is not locked.

I am attaching the screenshots of the errors as well as mass compile log for TestStand.

[kewsvnet]

somehow it only allowed me to attach 3 files so here are the rest!

[kewsvnet]

logs from the build!!!

[Shawn_S.]

Hello kewsvnet,

I received your logs.  Have you tried opening some of the VIs mentioned in your Deployment Utility Status log to check for a warning about relinkage of sub-vis as suggested by Manooch on 04-22-2011 11:49 AM?

[kewsvnet]

I have opened the VIs that it shows in the logs in Labview and they open fine. All the VIs reside in the paths that the Deployment Utility seems to be looking for in the log as well!

[V_T_S]

The same issue exist wiht Labview 2010 SP1 + TestStand 2010 (with patch)

The deployment complains about all the modules from the user.lib folder

While Processing VIs...
Error: Unable to find all subVIs from saved VIs. Either a subVI is missing or the VI is not saved in the current LabVIEW version.
The call chain to missing VIs:
1 - ZCAT - Get User List.vi
    2 - Sort 2D Array (String)__ogtk.vi (missing)
    3 - Sort Array__ogtk.vi (missing)
4 - Modify Header.vi
    5 - Search or Split String__ogtk.vi (missing)
6 - StringCutWhenError.vi
    7 - Multi-line String to Array__ogtk.vi (missing)
8 - OnNewStep_Fixed TestID_Dialog.vi
    9 - String to 1D Array__ogtk.vi (missing)
    10 - Search 1D Array (String)__ogtk.vi (missing)
    11 - Search Array__ogtk.vi (missing)
12 - Post_DelayActionResult.vi
    13 - ZCAT - Post Result Message.vi
        14 - Post Message.vi
            15 - Post Event.vi
                16 - Post Data to Respective_Master_Q.vi
                    17 - Enqueue Element.vi (missing)

1 - ZCAT - Get User List.vi     ->  C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 2010\Components\Callbacks\FrontEnd\ZCAT - Get User List.vi
2 - Sort 2D Array (String)__ogtk.vi  ->  <userlib>:\_OpenG.lib\array\array.llb\Sort 2D Array (String)__ogtk.vi
3 - Sort Array__ogtk.vi         ->  <userlib>:\_OpenG.lib\array\array.llb\Sort Array__ogtk.vi