Repair VI.lib

[MrQuestion]

Is it possible to repair the vi.lib? 

I noticed that in one of my projects there were several dependencies in my project that were coming from other totally unrelated projects.

So, i started finding the callers for this VI.  It ends up that somehow some of the VI's in the vi.lib for example "General Error Handler.vi" has subVI's pointing to projects that it really shouldn't.

This is really frustrating. I tried deleting the projects that have the subVI's and now everything is broken. Even the examples that ship with LabVIEW.

I have done a repair on LabVIEW recently and that didn't fix the problem. I have also repaired LabVIEW FPGA and RT.

I would have thought that doing a repair on LabVIEW would have at least fixed the examples that shipped with LabVIEW, but the subvi's are still pointing to old locations in my old projects. This seems to be affecting several VI's in the vi.lib. I'm not sure what caused this to happen in the first place, and I can't seem to fix it.

I'm using LabVIEW 2011 SP1 11.0.1f1

On Windows XP.

[smercurio_fc · Accepted solution]

It sounds like you have copies of those core VIs somewhere in your project source, so those copies are the ones that are being opened first, wreaking havoc on linking. This typically happens when you deal with old LLBs in which the person who created it decided to save everything, including VIs from <vilib>. For example, where is it loading "General Error Handler" from? If you look at the VI Hierarchy you should be able to tell where the messup occurs. You can show the full paths in the VI Hierarchy to try to track down the problem.

You may also want to check you Paths settings. Are you overriding the default search path for VIs?

[MrQuestion]

Thank you!

You are correct, awhile ago I received an old project and several VI's were linking to the wrong location. So I changed the default path. It appears that I forgot to point the path back to vi.lib. 

This fixed the issue.