Generic Error, subVI's will not load.

[georgesmith]

Hey guys, forgive me if this is a stupid question. I googled the error code and couldn't find anything, and since the last time I posted on these boards I was swarmed with help, I figured I would try it again.

I am trying to re-open a LabView file I made several months ago, that uses several VIs from Keithley LabView drivers (I'm using a Keithley 2400 and a 2182).

I store these files on a network drive, so that I can run my instrument control from several computers around campus. Sometimes this is difficult, because when I re-open these LabView files, I have to remind LabView where I put some of the instrument subVIs. Slightly time consuming, but it doesn't bother me too much.

Until today. I get this generic error over and over trying to find the file path for these subVIs. It doesn't matter if I do it from the prompt during startup or from the block diagram..

What is this error and how do I work around it?

[Gregory]

I think I have seen what you are talking about, where LabVIEW complains every time that the instrument drivers are not in the expected location. What I usually do, is put the drivers into instr.lib when I first download them. Then I open the .lvproj and "save as..." to create a copy of the project in a new folder. This copy does not have the same desire to be in instr.lib that the original has.

Your screenshot is obscuring the important bit of information which is where it expects to find the file, can you share that with us?

[Kyle97330]

That looks like it might be a corrupt VI. (Assuming that it's always the same message about "Error query.vi".)

Can you re-download whichever driver (2400 or 2182) that gives the error and copy that file over to the location it's currently at?

[georgesmith]

Here is the un-cropped image. 

I know that the files are not corrupt, because they load immediately on my laptop, which also has access to this drive.

[billko]

I would expect the laptop to load its own version of this driver.

[Alexander_Sobolev]

Can it happen that you have not closed project and possibly Labview on the other PC after using this file and it is locked?