Why might a VI break when building an executable on one machine versus another?

[N8D11]

I have a large test application that is designed to work on several machines. In the process of testing I go to each machine and open the project on the machine I am testing. When I am satisfied the project is behaving as expected  I build the executable and test that it is working as expected. This is where my problem occurs.

More Background: This software was originally meant to run one test at a time and was upgraded to run multiple tests at the same time(sharing resources and the like). To accomplish this, another VI was written that opened instances of the original VI (clone). I don't know if this is common, however this has been in use for a while and is known to work even after the migration to the network(probably not the problem).

My issue is that I can build the software on one machine and it will work on another machine, yet when I try to build the same exact project from the other machine it will no longer open the instance of the original VI. I probed the error wire and it indicates that the VI must be broken. So I open the VI and it has no errors.

I have no idea how to diagnose this any further. Anyone have any ideas?

[JackDunaway · Accepted solution]

Try mass compiling the entire project hierarchy prior to making a build. Also, if you are dynamically launching VI's, you must put them in the "Always Include" section of a Build Spec.

Do either of these things help?

[N8D11]

I got it to work, thanks for the response. I re compiled the code and moved the project onto the local machine and it works. I am not sure which of the two did the trick.