DSC 2018 Executable does not work/missing components

[jvc]

Hello,

I am trying to build a LabVIEW DSC executable, and I am having issues when I try to run the built executable.  I have built many executables before, but this is my first for DSC, and it is kicking my butt.  I have a license for the DSC runtime engine and it is the same version as the toolkit as in Capture.png.  I am trying to run the executable on my development machine before I try it on a deployment machine.

The build seems to go OK I get all the files that I expect as shown in Capture2.png, but when I go to run it, it acts just like a VI and I get the following issues:

- The executable cannot Error Ring.xnode, and presents a dialog for it.  I found it in the LabVIEW shared folder, but thought it would be part of the exe or the run time engine.

- I press cancel and ignore all and I come up wtih this load and save warning list as shown in capture3.png.

- I can now go into the executable's block diagram (no kidding), and the SharedVariableIO node is bogus as shown in Capture4.PNG.

I did see a couple of forum entries on building DSC executables, but they are old (2011).

I have also included the build log as well.

Thanks,

Joe (CLA)

[Trevor.H]

Hi Joe,

From the activation screenshot, everything is looking good to go from a licensing perspective.

In screenshot 3, it notes the problem is arising from "DB Tools Open Schema.vi".  In case something got corrupted there, could you try deleting and replacing that function?

Additionally, in the final screenshot, if you go back to that section in the source code, does it still show the broken wire there as well?

Finally, it may not hurt to run a mass compile:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9BESA0&l=en-US

[jvc]

Trevor, thanks for the reply, and I will try your suggestions.  The first error I run into is the executable not finding the following item, "Error Ring.xnode".  Any ideas on what is going on here?

[jvc]

Hey Trevor,

I did a mass compile from the project (right click on the Project: <Your project here>) and the tools -> mass compile of my main application's directory.

DB Tools Open Schema.vi is located in: C:\Program Files (x86)\National Instruments\LabVIEW 2018\vi.lib\addons\database\Auxilliary.llb, and is not used by my project.

The source code runs with no discrepancies, and has been used running source for the past seven years.

I created and ran the executable, and here is the order of how the errors stack up (this is how it executed previously).

1) The runtime engine is looking for Error Ring.xnode, and brings up a dialog box looking for it (SS1.png).

2) So I went ahead and loaded it from the NI installation directory as shown in ss2.png

3) The next file not found is "Get Text Rect.vi", so I went ahead and loaded it from the NI shared directory in ss3.png

4) Next is XNodeRExt32.ctl

5) Next is Draw Rect.ctl

6) Next is Draw Rect.vi

7) Next is Picture to Pixmap.vi

😎 Next is trim white space.vi

9) I get to the code screen, and I get the dialog with a broken executable as shown in ss6.png

10) The dependencies show that a whole bunch of vi.lib files are not making it into the executable, and the DB Tools Open Schema.vi are not making into the executable.

So, it looks like all the dependencies that are needed in the executable are not making it into the assembly.  Also, DB Tools Open Schema.vi is not used by the executable directly, but most likely by DSC.

Not sure where to go from here now.  Thanks for you help!

Joe

[Trevor.H]

It may be useful to send us a copy of the build specifications.  Additionally, we can try adding all dependencies to the "always included list".  That way if the compiler did fail to pick up a file, we can manually force its hand.

It seems like this issue may require some more in depth troubleshooting that may be more efficiently handled as a service request.  To that end, I think it may be useful to open up a service request with us at NI.  Feel free to call into 866-275-6964 to create a service request, or make one online.  

[jvc]

Thanks Trevor.  I spoke to my NI field engineer a couple of days ago, and he suggested the same as well.  I did try including the dependencies in the build spec in the executable and in the data folder.  The result was the same.

[Trevor.H]

Sorry to hear that didn't do the trick.  I did hear from one of my colleagues though that you opened the service request.  Once we get to the bottom of this, it would be great for us to share with the forum!

[pat_creely]

Hi Trevor,

I am having the same problem with the ZeroMQ VIs as the others in this forum. It works great from the project but not with the executable. In reading some of the other letters and I get the impression that some support VIs may not be included as part of the installation but I have no clue as to what they might be. I have attached examples of the transmit and receive loops used in my overall program (2111 Auto Mode Comm Simulator) and in the Remote Control Simulator that I created to verify communications.  As long as the Auto Mode Comm Simulator is running from the project, it works OK. If you open the Auto Mode Comm Sim project, you can see how the installer is configured. The ZeroMQ VIs are included in a folder within the Auto Mode Comm Sim project.

Regards,

Pat Creely

[pat_creely]

Trevor

I found the cause of the ZMQ executable problem (see attached). When creating the executable, two .dll files need to be added to the source file selection in the Always Included window; libzmq32.dll and lvzmq32.dll . I hope this helps others with a similar problem.

Regards,

Pat Creely