Problems loading steps that use Network Shared Variables

[BonbonBLou]

Hi there,

I am having repeated problems loading LabVIEW steps that use Network Shared Variables in TestStand.

When I try and run a sequence I get an error message with the code -17600 - Failed to load a required step's associated module. I believe it is the shared variables which are causing this, as if I skip the step it mentions, I get the same error message for a different step further down that also uses the network shared variables and other steps seems to load without issues. The VIs are not broken and I have had the sequence working previously, but I made some changes in the LabVIEW project and now suddenly I cannot get it to run any more.

If I go to the step and check the module settings, the module is unable to load in TestStand, displaying the message "Unable to load VI with the LabVIEW Run-Time Engine version 16.0. The version of a subVI might not match the version of the run-time engine or a VI dependency might be missing. Configure the LabVIEW adapter to use the LabVIEW development system, then run 'Update VI Calls' from the TestStand Tools menu."

I have done this, and when I change the LabVIEW adapter to use the development system, the VI then loads successfully and the sequence can be run. However, as soon as I go back to the run time engine, it cannot load again.

Things I have tried so far:

- Updated all VI calls in TestStand after changing the LabVIEW adapter to development system

- Undeployed and redeployed all network shared variables

- Mass compiled all VIs in the LabVIEW project.

- Recompiled the problem VI using 'Ctl + Shift + Run arrow'

Previously one of the above steps has fixed this issue before, but now none of them are working.

The issue seems to come back every time I move between different versions of code, so I think there must be some underlying issue that I might need to address. For now, I'd be happy to just get it working right now so I can run my sequence file again, but if there's a permanent fix I can try then that would be fantastic.

Any advice would be appreciated!

[SercoSteveB]

Hi vascibean

I have seen something similar before ("VI is not executable error"), but not with Shared Variables.   

What's frustrating is the lack of feedback you get from TestStand of what is causing the error to be returned when using the LV RTE.  In the end we had to use the LabVIEW Diagram Disable Structure to comment out sections of the Block Diagram and then try and call the VI from TestStand.  By commenting out different aspects of the Block Diagram we were able to trial and error our way to the cause of the issue.  Not much of a solution I know but at least you should be able to confirm that it is the Shared Variables that are causing your issue or identify if it is something else.

NOTE:  We started by commenting out the entire Block Diagram, to see that the method was working.  Be sure to unload in TestStand in-between your VI changes otherwise TestStand will keep running the version it has in memory.

Steve

[Chris_Märki]

I have already seen something similar.
At that time the problem was a "private" Sub-VI of a library.

I recommend the procedure that Steve has suggested.

Kind regards

Chris

[bjenkins]

I'm quite late to the party here, but recently ran into the same problem and found a solution.  My sequence was complaining about a wrong runtime version but it turns out it didn't have access to the subvi's that it needed.  Open up the step and click the refresh button (in my version it was two green arrows in a circle).  This brought up a search box asking for the specific subvi's that the main VI couldn't reach.  After loading a ton of subVIs, the step worked!