This is a common error if you are using LLB files to load VI's and you selected on or perhaps even all three options in the LLB source distribution:
Additional exclusions:
- exclude files from vi.lib
- exclude files from instr.lib
- exclude files from user.lib
Building an LLB like this will end up with broken VI's inside the LLB, although ofcourse from the development environment such as LabVIEW, you will never see a broken arrow since LV fills in the missing VI's.
In the runtime environment however, this is a different story and will leave the VI as it was: broken since you excluded all the necessary files.
File exclusions from LLB's is only necessary when transporting the code from one place to another, for instance between 2 programmers: one in America, one in Japan. Since both programmers have a LV version, they can easily exclude common code from the LLB and still share the code.
In runtime environments excluding code will generate these error's when building the code, although the VI's do not appear to be broken...
I do not know whether this is relevant information for you, but I ran into the same problems when I started to build reconfigurable programs by using LLB's to ship VI code to "update" a program. That's why I post this possibility here..
best regards
