Loading sequence dynamically causes deployment of shared variables to fail?

[Taylorh140]

It seems when I use have TestStand load a VI  that references shared variables it gives me the error message.

Unable to load LabVIEW Project '<PROJECT LOCATION THAT IS CORRECT>'

TestStand failed to automatically deploy the shared variables found in project libraries in the specified LabVIEW project. Please ensure that the project library only defines shared variables and does not contain any VIs. Also, make sure the host exists and it is in the network.

LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct

Is this behavior to be expected? Or is this a bug?

[Taylorh140]

I must also mention i am using an OI that launches the Shared Variables. (disabling automatically launch variables in the adapter menu fixes this problem) 🙂

[Al_Niz]

Hi,

i had same problem, i removed the virtual folder from the library and it worked fine. it seems that it not allowed to use in Teststand  Shared Variables in Virtual folders from a LabVIEW Project.

 

the guileful thing is that when trying the vi in labVIEW everything works fine.