LabVIEW vi fails to load with run-time engine 2017

[smercado]

Hi,

I'm getting a strange error I have a few TestStand sequences on a machine. The system has 2 windows accounts on it. One account can run all the sequences in run-time mode while the other has issues loading some of the VIs in run-time. The search directories match up and I already did a mass compile which worked since they run on the other windows account. 

Any one run into something like this?

Thanks,

[SercoSteveB]

Just a thought; is it possibly a user privilege access problem? Where are your VIs stored?  Are they stored in a location that your first user can access but your second cannot or can following some sort of privilege elevation?

i.e.  Browsing files in Windows explorer; all users are able to access files (VIs) in C:\Users\Documents\Public but user1 is only be able to access files in C:\Users\Documents\user1, all other users need a privilege elevation to access the files in C:\Users\Documents\user1.

[smercado · Accepted solution]

Hi,

That was my first thought, as I have had that happen before but it was not. 

I did figure it out. So the issue was that there were two folders on the system with identical VIs (names and code) in different locations. When in development mode Teststand sorts out the file paths but in run-time the LabVIEW project does. It just so happened that the LabView project resolved the path on one user account a few times and then when tested on the other it could not. once I deleted the duplicate folder and resolved the conflicts in the project. it all worked correctly. 

[SercoSteveB]

Good stuff.

[xiaoshuang_zhou]

Hi, 

So you just delete the duplicate folder and resolve the conflict to fix the problem?

Anything else need to be taken care of?

[smercado]

On this particular case I just needed to remove the duplicate files. You many still need to recompile your vi and/or relink you VIs. If you are having the issue after removing duplicate files.