New install not finding VIs

[ecb1123]

Hello,

I have two computers with installations of LabView 2011, both installed from the same discs in the same manner. However, when I try to take a project developed on Computer A and run it on Computer B, I get dependency errors for a number of basic functions.

For example, in the project explorer, under RT CompactRIO Target\Dependencies\vi.lib, there is an error with Write To Spreadsheet File.vi [Warning: has been deleted, renamed, or moved on disk]. When I click on it, I get the following message:

Loading:

C:\Program Files\National Instruments\LabVIEW 2011\Targets\vi.lib\Utility\file.llb\Write To Spreadsheet File.vi

Searching:

C:\Program Files\National Instruments\LabVIEW 2011\Targets\instr.lib

and it prompts me to Find the VI Named "Write To Spreadsheet File.vi".

Now, I can find that file under the C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\Utility\file.llb\, and select it. However, then it has the same error for every single VI called by that one. I imagine I could just manually remap all these, but it would take a week and there must be a better way.

A related anomaly is that if, from the Project Explorer, I make a new VI under the RT CompactRIO Target, the 'functions' and 'controls' palettes come up completely empty. In contrast, making a new VI under 'My Computer' works normally, and the VI lists populate as expected.

Thanks for any advice you may have.

Cheers,

Elizabeth

Edited: I select the file from C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\Utility\file.llb\

not

C:\Program Files\National Instruments\LabVIEW 2011\Targets\vi.lib\Utility\file.llb\

as I'd mistakenly written in the original post

[ecb1123]

Oh, and to complicate things, on Computer A, there is no 'instr.lib' under C:\Program Files\National Instruments\LabVIEW 2011\Targets\, so I don't know why it would be looking there in the first place.

-Elizabeth

[RavensFan]

Something is wrong with the path.  Write to Spreadsheet File is not located in a directory path that includes "Targets".

Perhaps somebody had moved it on Computer A, or somehow found/made a copy of it under the "Targets" path and used that.

To fix the VI, go find the file under "C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\Utility\file.llb\Write To Spreadsheet File.vi" .  Once the errors are fixed, then resave the VI.

Then I'd recommend reinstalling LabVIEW on Computer A to fix the installation.

"However, then it has the same error for every single VI called by that one".  I'm not clear if you are dealing with VI's at a higher level, or subVI's below your VI.

I'd recommend creating a VI and dropping a copy of Write to Spreadsheet File in it.  While that is open, then open any VI that has the problem with the file path.  Since the WTSSfile VI is in memory, the newly opened VI's should grab the opened copy without trying to search for it.  Then save the VI (which should show an asterisk because there are unsaved changes now that the WTSSfile is linked to a different location.

---

@ecb1123 wrote:

Oh, and to complicate things, on Computer A, there is no 'instr.lib' under C:\Program Files\National Instruments\LabVIEW 2011\Targets\, so I don't know why it would be looking there in the first place.

-Elizabeth

---

Maybe the VI's that have the file path linked incorrectly occurred on some PC before computer A, or with some installation of LabVIEW before LV2011.

[RavensFan]

Oh, and to complicate things, on Computer A, there is no 'instr.lib' under C:\Program Files\National Instruments\LabVIEW 2011\Targets\, so I don't know why it would be looking there in the first place.

-Elizabeth

[ecb1123]

Thanks for your advice, RavensFan.

I mistyped when I listed the path I selected the file from; although the error message was as I wrote, I found the file under the path you suggested. However, once I select that file, It continues to ask for 'General Error Handler," and then "LVBoundsTypeDef.ctl", etc.

It appears that this is only a problem for VIs on the cRIO, which MAX lists as connected and running. In fact, in a blank VI running on the cRIO, there are no functions or controls listed in the respective palettes.

-Elizabeth

[JÞB]

Elisabeth,

Somebody did something bad to your LabVIEW directories.  Most likely an accidental folder drag in windows explorer.  A "Clean" install puts Write to spreadsheet file.vi at C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\Utility\file.llb

C:\Program Files\National Instruments\LabVIEW 2011\Targets\

Should only contain support for FPGA and RT

[ecb1123]

Hi Jeff,

Thanks for your help.

I'm afraid I made an error in the original post; I select the file from C:\Program Files\National Instruments\LabVIEW 2011\vi.lib\Utility\file.llb\

not

C:\Program Files\National Instruments\LabVIEW 2011\Targets\vi.lib\Utility\file.llb\

as I'd mistakenly written in the original post

This (the former directory) is also where the file is located on Computer A.

Thanks,
Elizabeth

[RavensFan]

Where is LabVIEW actually trying to look for the file?  That is where the file was when the VI was last saved or created.  Is the "targets" directory a part of the search path?

It doesn't matter now whether the file is in the correct path on the previous computer now.  The VI will always try to load the subVI from the location where it thinks it was before until you manage to correct it to be from the correct, current path.

[mr_goodlife]

hey guys,

i actually have the same problem as mentioned before.

a labview vi was created in 2012 SP1 and when you try to open it in 2013 on the compactRIO, then labview always asks for the directory.

even if i save the VI after having rewired all necessary links, it always does the same when you close the vi and reopen it.

does anybody of you have a solution or explanation to that?

cheers,

stefan

[JÞB]

Let me guess.   (you haven't really shown us what you mean and, that post was rather ambiguous but,  We do try to help!) So I shall guess

~~~Oh, Magic 8-Ball...~~~

Your project uses "Auto-Populating" folders and you just used windows explorer to move the files on disk.

Spoiler

Pretty good guess, right?

[mr_goodlife]

Hey Jeff,

actually that guess sounds right.

Now how do I correctly move the data from the first PC (LabView 2012 SP1) to a USB-stick (or similar) to make it work with LabView 2013 SP1 ?

Thank you very much!

Regards,
Stefan