DIAdem Error: (Hex 0x3EB) The VI Is Not Executable

Issue Details

• I am calling a LabVIEW VI from DIAdem, but I keep receiving error 0x3EB. What causes this?
• I would like DIAdem to use LabVIEW Runtime to execute a VI. However, DIAdem states that "The VI is not executable", even though the VI does not have a broken run arrow. How can I fix this?
• When my DIAdem VisualBasic Script (VBS) launches a LabVIEW VI, it displays the below error. 

LabVIEW: (Hex 0x3EB) The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select <b>File>>Open</b> to open the VI and verify that you can run it.

Solution

DIAdem can generate error 0x3EB due to one of the following reasons:

• Missing Source Distribution.
• Missing dependencies in the LabVIEW Source Distribution.
• Broken VI or subVIs.
• Incorrect LabVIEW Runtime version.
• Mismatched LabVIEW and DIAdem bitnesses.

Follow the steps below to check and verify each point:

• The LabVIEW VI(s) that DIAdem executes must be built into a Source Distribution that includes subVIs and vi.lib dependencies.
  1. If you are not building a Source Distribution, follow Creating a VI Source Distribution for instructions.
  2. Right-click the Source Distribution and select Properties:
     1. On the Source Files tab, ensure that all VIs are set to Always Included.
     2. On the Additional Exclusions tab, ensure that Exclude files from vi.lib is unchecked.

• Ensure that no VIs or subVIs have a broken run arrow.
  • This can be easily verified by opening the top-level VI in LabVIEW and confirming that the run arrow is not broken.

• In the DIAdem script, use LVRuntime.Init "<version>" to explicitly set the version of LabVIEW Runtime to use.
  • Replace <version> with the actual version number. For example, LabVIEW 2024 Q3 would be 24.3.

• Ensure that you are using LabVIEW 64-bit to develop your code.
  • The LabVIEW and DIAdem bitness must match, and DIAdem only comes in 64-bit.