Scilab Script and Application Builder Error "This VI is Not Executable"

[Glibby1234]

I'm trying to build a standalone .exe with a VI that contains a Scilab script using the Scilab gateway. On the actual program I created I get an error message stating that the front panel cannot be loaded on the SubVI that contains the Scilab script node. If I delete the node the program runs fine. 

I decided to create a very basic VI containing a Scilab script to troubleshoot, and I get the following error: "This VI is not executable, The full development version of Labview is required to fix the errors". I don't understand this at all, since I do have the full development version of labview. Also, the code runs fine as a native VI, and this error occurs on my development machine, so all required files should already be in the correct locations. Additionally, I've added "ScriptScilab.dll" as an always included source file. 

What am I missing here? .Zip of may sample application attached. 

[oscarfonseca]

Hello John2787,

I also see the error on my side with the application you developed. Have you checked the KnowledgeBase article: This VI is not Executable Error?

Another option is to mass compile, force recompile, and make sure your dynamically called VIs are in always included.

Hope any of these work for you. Let us know your results!

[Glibby1234]

The .Net solution doesn't make sense because it doesn't run as a .EXE on the development machine but does run as a VI on the development machine. I updated anyway and it still doesn't work. Also, recompiling doesn't seem to help. 

I did some testing and found that the Scilab Script node seems to run fine (both development as an executable) when compiled under Labview 32bit, so I'm guessing there's some issue in the gateway itself. 

[oscarfonseca]

Hi John2787,

I would try to get suport from Scilab Enterprises directly. I see in their product page they have a contact email you might want to try: LabVIEW to Scilab Gateway - Scilab Enterprises.

On the other hand, you might want to try building a simple VI that doesn't use those VIs, to check if the issue relies in the Scilab Script node, or in the complier/RunTime itself.

Let us know your findings.

[Glibby1234]

---

On the other hand, you might want to try building a simple VI that doesn't use those VIs, to check if the issue relies in the Scilab Script node, or in the complier/RunTime itself.

Let us know your findings.

---

That's exactly what that VI I posted was. It was nothing more than a Scilab node to multiply X*Y with an output Z, plus 2 controls and an indicator. It runs fine as a VI, it gives me the error when compiled and run as an .EXE. 

[oscarfonseca]

I apologize for the confusion, John2787 .

By simple VI I meant a block diagram with just an add function, so we can test it's not a compiler issue, or the RunTime not being correctly installed.

If this "Add" VI succeeds, perhaps the issue is in the Scilab node indeed, and they can provide more assistance to figure out why it doesn't behave as expected in deployed applications.

[Glibby1234]

Yes, all other standard Labview functions run/compile without issue. 

[BonbonBLou]

Hi,

I realise this is an old dead thread, but wondered if you ever managed to fix this issue?
I am having the same problem with the Scilab node, in that it works fine when running in source but breaks my application when built into an executable.

Do you have any advice in getting this to work?