Unable to find all subVIs from saved VIs, again

[Neurotikart]

TestStand 4.1.1, LabVIEW 8.6.1f1, WinXP

Trying to build a deployment in TestStand.  This had been working, now it's not. 

During the build, I get the now-infamous popup:

Title: "Save Modified VIs?" 

Text: "An error occured while trying to read the dependencies of your VIs; a possible cause for this problem is VIs not saved in the current version of LabVIEW. Would you like to save any modified VIs now?"

I select "yes", and the build then fails with errors in the log pane of the "Build Status" window.  The error is:

Error: Unable to find all subVIs from saved VIs, either a subVI is missing or the VI is not saved under the current LabVIEW version.
The missing file path is:  etc, etc.

I go to said missing path.  The VI is in fact present.  I open the VI and do "Save All", try again.  Same thing.  (There are subsequent errors, more on them later.  Then, from the front panel of the VI in question, I do View -> VI Hierarchy.  Double click on every VI in the hierarchy, and from the front panel, right-click on the icon and select "VI Properties."  All those VIs are also present and saved in the current verison.  Attempt to build again, same error.

The other two errors I'm getting are as follows:

Try loading the following top level VIs and using File->Save All:

C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.1.1\UserInterfaces\Simple\LabVIEW\TestExec.llb\custommenu.rtm
C:\Documents and Settings\All Users\Documents\National Instruments\TestStand 4.1.1\UserInterfaces\Full-Featured\LabVIEW\TestExec.llb\Full UI - Top-Level VI.rtm while Processing VIs...

So, I try to open and save "custommenu.rtm" and "Full UI - Top-Level VI.rtm" from within their respective LLBs.  I can re-save anything else in the LLBs, but for these custom menus, the save option is grayed out.  (Of course, I haven't *DONE* anything with these files or LLBs, so I can't imagine why all of a sudden they need to be re-saved...)

This type of thing is unfortunately not a new problem in our organization.  The problem is that the error message that gets generated may or may not point to the actual problem at hand.  This is also happening when I'm two days over the deadline for my project, so my lower torso is on the line here.  Is there a debugging option or log file or some kind of trace I can do to dig into this and find out the state of things causing the error?  Please help me out here.

-Mark

[Manooch_H]

Mark -

Is it alright if I ask our forum administrator to give me your email address?

[Neurotikart]

Sure.  Meanwhile, I've used our source control system here to go back to a date when the project built, then perform successive approximation to find out exactly *when* the build broke and perhaps what change brought it about.  Thanks.

[Manooch_H]

Neurotikart -

It looks like this issue was caused by cross-linking in some of your VIs. Some of the VIs called from TestStand were expecting to find SubVI A at a location such as C:\foo but SubVI A did not exist at location C:\foo.

The TestStand VI Search Tool might have been helpful in identifying this type of cross-linkage, in case you run into something like this again in the future.

[Jauron]

I am getting this same error message. Same scenario, all my VIs are present.

I have yet to get a good build.

I tried the VI Search Tool, but it did nothing. No status window or anything.

I have an open ticket # 7347305. I sent a log into the engineer assisting me last night, and spoke to him this morning...haven't heard anything about this.

PLEASE HELP!!!

[marianito]

I am running into same problem, is there any known solution anywhere?

All my VI are present, i can run my sequence from the developement environment but deployment fails...

[JL@NI]

Hello marianito,

Could you please provide more detail about your version of TestStand and LabVIEW?

Regards,

Jeff L.

[Al.B]

Hi,

This issue can occur for a number reasons.  We are currently working to improve the information provided to help with debugging this error, but in the meantime, please try the following:

1. Ensure that all VIs are mass compiled in the same LabVIEW version
2. As manooch mentioned, this issue can occur if VIs are linked incorrectly.  Make sure that there are no duplicate files, and open any projects you are using and ensure there are no linking issues (even with VIs that are not included in the deployment, but are in the same project as VIs that are included)
3. In the LabVIEW options within the distributed files tab of the TestStand Deployment Utility, check the "remove unused VI components", and see if the build behavior changes
4. Try to create a LabVIEW source distribution with the problematic VIs.  This can often provide more details on what is causing the TestStand Deployment Utility to fail.

Please let me know what the results of these steps are!

[ATE_Dude_22]

What else could possibly cause this type of problem?? This is a copy of the log I get. All of these vi's are whole, and work just fine when using the development system, only when I go to build the testStand deployment do i get these errors???

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 - Trans Pwr Drop - Connect Battery Sense Lines.vi
2 - pipx40 Set Channel Pattern.vi (missing)
3 - pipx40 Get Channel Pattern.vi (missing)
4 - RFSG Frequency Sweep - Setup.vi
5 - niRFSG Configure Generation Mode.vi (missing)
6 - niRFSG Configure RF.vi (missing)
7 - niRFSG Initialize.vi (missing)
8 - RFSG Frequency Sweep - with CW source.vi
9 - niRFSG Close.vi (missing)
10 - niRFSG Commit.vi (missing)
11 - niRFSG Configure Output Enabled.vi (missing)
12 - niRFSG Abort.vi (missing)
13 - niRFSG Initiate.vi (missing)
14 - Noise Immunity - Add FM White Noise.vi
15 - niRFSG Write Arb Waveform (Complex Input).vi (missing)
16 - niRFSG Write Arb Waveform.vi (missing)
17 - rfsg_FindWaveformParamsForFrequency.vi (missing)
18 - niRFSG Ref Clock Sources.ctl (missing)
19 - Noise Immunity - Check Generation.vi
20 - niRFSG Check Generation Status.vi (missing)
21 - Noise Immunity - Stop and Release ARB.vi
22 - niRFSG Clear All Arb Waveforms.vi (missing)
23 - Buzz.vi
24 - niSwitch Wait For Debounce.vi (missing)
25 - niSwitch Disconnect Channels.vi (missing)
26 - niSwitch Connect Channels.vi (missing)
27 - Close.vi
28 - pipx40 Close.vi (missing)
29 - niSwitch Close.vi (missing)
30 - Initialize - NI 32x1 Mux.vi
31 - niSwitch Disconnect All Channels.vi (missing)
32 - niSwitch Initialize With Topology.vi (missing)
33 - niSwitch Revision Query.vi (missing)
34 - niSwitch Topologies.ctl (missing)
35 - Position Select - Clear.vi
36 - pipx40 Reset.vi (missing)
37 - pipx40 Clear Card.vi (missing)
38 - Position Select - Set.vi
39 - pipx40 Set Channel State.vi (missing)
40 - Show Relay States.vi
41 - pipx40 Get Channel State.vi (missing)
42 - Switch - Read IDs.vi
43 - pipx40 Get Card ID.vi (missing)
44 - Switch Initialize.vi
45 - pipx40 Initialize.vi (missing)
46 - pipx40 Self Test.vi (missing)
47 - Close.vi
48 - niFgen Close.vi (missing)
49 - Config RF SigGen with hardware timing.vi
50 - niFgen Write Named Waveform (I16).vi (missing)
51 - niFgen Write Named Waveform.vi (missing)
52 - niFgen Allocate Named Waveform.vi (missing)
53 - niFgen Delete Named Waveform.vi (missing)
54 - niFgen Query Arb Waveform Capabilities.vi (missing)
55 - niFgen Send Software Trigger.vi (missing)
56 - niFgen Initiate Generation.vi (missing)
57 - niFgen Write Script.vi (missing)
58 - niFgen Export Signal.vi (missing)
59 - niFgen Configure Software Edge Script Trigger.vi (missing)
60 - niFgen Configure Trigger (poly).vi (missing)
61 - niFgen Configure Digital Filter.vi (missing)
62 - niFgen Configure Analog Filter.vi (missing)
63 - niFgen Configure Clock Mode.vi (missing)
64 - niFgen Configure Output Mode.vi (missing)
65 - niFgen_ctl Exported Signal Identifiers (Ring).ctl (missing)
66 - niFgen_ctl Exported Signal Name Values (Ring).ctl (missing)
67 - niFgen_ctl Trigger Script - trigID Values (Ring).ctl (missing)
68 - niFgen Output Mode.ctl (missing)
69 - niFgen Clock Mode.ctl (missing)
70 - Config RF SigGen.vi
71 - niFgen Set Named Waveform Next Write Position.vi (missing)
72 - Configure CW RF.vi
73 - niRFSG IVI Error Converter.vi (missing)
74 - Configure RFSG_v01B.vi
75 - niRFSG Reset.vi (missing)
76 - HFTR Script Trigger.vi
77 - niFgen Send Software Edge Trigger.vi (missing)
78 - niFgen_ctl Trigger SW - TrigIdentifier Values (Ring).ctl (missing)
79 - niFgen_ctl Trigger SW - TrigName Values (Ring).ctl (missing)
80 - Init RF Sig Gen.vi
81 - niFgen Get DAQmx Task.vi (missing)
82 - niFgen Configure Ref Clock Frequency.vi (missing)
83 - niFgen Configure Ref Clock Source.vi (missing)
84 - niFgen Initialize.vi (missing)
85 - niRFSG Initialize With Options.vi (missing)
86 - niFgen Ref Clock Source.ctl (missing)
87 - Stop.vi
88 - niFgen Abort Generation.vi (missing)
89 - Cal - Analog Connect Prompt.vi
90 - niDMM Function.ctl (missing)
91 - Close.vi
92 - niDMM Close.vi (missing)
93 - Config AC.vi
94 - niDMM Initiate.vi (missing)
95 - niDMM Configure Measurement Absolute.vi (missing)
96 - niDMM Config Measurement.vi (missing)
97 - DVM Initialize.vi
98 - niDMM Initialize.vi (missing)
99 - Read.vi
100 - niDMM Fetch.vi (missing)
101 - niDMM Read.vi (missing)
102 - niDMM Is Over Range.vi (missing)
103 - Close.vi
104 - hp66xxbc Close.vi (missing)
105 - DC Init.vi
106 - hp66xxbc Initialize.vi (missing)
107 - Error Message Popup.vi
108 - hp66xxbc Error-Query.vi (missing)
109 - Get Battery Voltage.vi
110 - hp66xxbc Measure.vi (missing)
111 - Set Battery Voltage.vi
112 - chr52912 Error-Query.vi (missing)
113 - hp66xxbc Configure Output Enabled.vi (missing)
114 - hp66xxbc Configure Current Limit.vi (missing)
115 - hp66xxbc Configure Voltage Level.vi (missing):

[Daniel-E]

ATE_Dude,

One troubleshooting step we can try is to look at the LabVIEW project created by the TestStand Deployment Utility as part of the deployment process. Although this behavior is always subject to change in the future, current versions of TestStand create a LabVIEW project "behind the scenes" and build a source distribution from it as part of the deployment. This project is created in your Temp directory (open a Windows Explorer window and type %temp%). If you sort the folder by file type and scroll down to .lvproj files, the most recent one will be a Deployment project created by TestStand. 

You can open this project and examine it for conflicts or errors. You can even try building it (There should be a build specification in the project for a source distribution) and examine any errors that occur during the build. This can often give us additional information to help track down the errors.

I hope this helps, and please let us know how it goes. You might also consider making a new thread--some forum users may not notice the new questions since the initial post is old.