New install not finding VIs

[JÞB]

Assuming you have no source code repository on the network (Another good guess right? But a SCC system would bake it fairly easy)

Use the project explorer to either

A: Create a source diststribution or a zip build

B: Use the project explore's files view to "Move on disk" by seleting what you want moved and right-clicking the selected items.  You will be prompted to save all the vis that just had their dependancies moved and the vis will be resaved with the updated dependancies.  You will need to convert the auto-populating folders to virtual folders first of course, but thats a good idea anyway.

Then start looking at a SCC provider.

[retamozarr]

Today I experienced the same problem that the original poster had, where all of the VI's in a project under a cRIO target would try to load their dependencies from: <LabVIEW Installation Directory>\Targets, including VI's from instr.lib and vi.lib.

The problem went away right after I installed LabVIEW Real Time Module, which was missing from my installation when I first tried to open my project.