Error 1069 on Invoke Node

[GaryN]

Hello all,
I'm trying to build an application we have. In one of the sub-vi's there's a call to invoke node to start another vi. When I run the program from the VI this works fine as it should. When I build my executable and have my .llb for the executable, the program gets to this point and I get the above error, Error 1069: The sub vi is not executable. I know there's no executable for this and the spawn vi that calls it is in the llb. Any ideas as to why it will work as a vi but not as an exe? Thanks for any help.

Gary

[Aaron_G]

Gary,

A common reason for error 1069 is because you are attempting to launch the code from the executable environment and not a develoment environment. When it attempts to launch the VI, it may not find all of the subVIs, causing the VI to be reported as non-executable. One way around this is to open the VI that is dynamically launched, go to File>>Save With Options and choose Application Distribution. This will allow you to create an Application Distribution LLB file. If your executable launches the version of the VI that is in the Application Distribution LLB, it will work. As a word of caution, when saving files as an Application Distribution, the block diagrams are removed from the VIs, DO NOT OVERWRITE your existing VIs. You will never be able to edit them again if you do this. Alternatively, when you build the application, make sure that the VI is included as a dynamically launched VI in the list of included files.

Regards,
Aaron

[GaryN]

---

@Aaron G wrote:
Gary,

A common reason for error 1069 is because you are attempting to launch the code from the executable environment and not a develoment environment. When it attempts to launch the VI, it may not find all of the subVIs, causing the VI to be reported as non-executable. One way around this is to open the VI that is dynamically launched, go to File>>Save With Options and choose Application Distribution. This will allow you to create an Application Distribution LLB file. If your executable launches the version of the VI that is in the Application Distribution LLB, it will work. As a word of caution, when saving files as an Application Distribution, the block diagrams are removed from the VIs, DO NOT OVERWRITE your existing VIs. You will never be able to edit them again if you do this. Alternatively, when you build the application, make sure that the VI is included as a dynamically launched VI in the list of included files.

Regards,
Aaron

---

Aaron, thanks for the reply. I am saving with options and doing the Application Distribution. I'm also getting error 1003 but it's still saying the possible cause may be that the vi is not executable. The vi's that the invoke fails on are not included in the llb but according to the previous version of the software (in LV 6.1) it's not needed. (I checked the old llb file and the options in application builder.) I have the spawn vi which calls the invoke in the llb. The spawn takes a path, creates a reference and then does the invoke on this path. The vi's themselves are not in the llb. Will these need to be moved in? And if so will the paths need to be changed?

[Aaron_G]

Gary,

To clarify my post, the VIs that are the target that you are invoking dynamically are the ones that need to have the Application Distributions libraries created. The path that you are using should be to the "exectuable" version of the VI which resides in the llb you created.

Regards,
Aaron

[GaryN]

---

@Aaron G wrote:
Gary,

To clarify my post, the VIs that are the target that you are invoking dynamically are the ones that need to have the Application Distributions libraries created. The path that you are using should be to the "exectuable" version of the VI which resides in the llb you created.

Regards,
Aaron

---

Thanks for your help. I no longer get the executable error I was getting now I get a whole other error that I'm investigating. Error 1000: The VI is not in a state compatible with this operation. I've seen the NI explanation for this error in the Knowledge Base and have a few ideas on it but nothing concrete.

I have a general question though, did anything change in the invoke node from version 6.1 to 7.1? On our system that has LV6.1 our software still works like it should. I copied the folder to the new system and fixed any VIs with broken arrows in 7.1 but this invoke thing is screwing everything up. Any known issues or suggestions?

Gary

[KileenC]

Hi Gary,

It's possible that changes have been made to the list of available methods supported by the Invoke Node between LabVIEW 6.1 and 7.1 that is causing your programs to show up with an error. Especially when opening up VIs from LabVIEW versions more than 2 previous iterations, LabVIEW might have difficulty resolving the function that has been updated in the newer version of LabVIEW and therefore a manual resolution is necessary.


Kileen