Missing subVI Error When Installing EXE

[nrpratt]

I have a program that uses the Multicore Analysis and Sparse Matrix toolkit and am attempting to install the executable on another machine. When I attempt to open the executable, I get the following error. 

The file MASMT_LINALG.dll is included in the project and in the "data" folder where the program is in installed in the program files of the destination computer. Any ideas on why I'm seeing this error or how I can get LabVIEW to point to that file's location?

Thanks.

[Bob_Schor]

Do you have the appropriate Run-Time Engine installed on the Remote Machine?  I'm also am curious about your statement regarding the data folder where the program is installed in the program files of the destination computer.  When LabVIEW builds an Executable, it usually puts it in a Read/Write Folder (often in the Developer's LabVIEW Data folder), and my practice is to place it in a LabVIEW Builds folder in Public Documents.  Forum Users with more experience in porting Executables than I can comment on whether this could be an issue or not ...

Bob Schor 

[David22JRA]

Hello nrpratt

To avoid any other issue like that one, it is recommended to create an installer instead of an executable. Because in the installer we can include the correct Run-Time Engine and some others file the VI uses.

Regards

[nrpratt]

Thanks for the reply.

I created an executable and installer for this project, and the installer contains LabVIEW Run-time 2016 (the project was also built in LabVIEW 2016). I am able to run other executables I have made on the destination machine, so it looks like the Run-time engine is working. I've included a screenshot of the project. 

As far as the data folder goes, on the destination machine, the installer installs the project in C:\Program Files\Inverse Timer. In that folder is a folder called "data" that contains MASMT_LINALG.dll (which is the file LabVIEW says it cannot find), as well as lvanlys.dll (which it seems to be able to find without problem). I've included a screenshot of the folders in Program Files.

I have built executables and installers using the same method I'm using for this project and they have worked without incident. The only difference on this project is that I'm using a VI from a new toolkit I installed on the development machine. 

[RavensFan]

Check out this current thread.

http://forums.ni.com/t5/LabVIEW/Dll-works-in-project-but-not-in-executable/m-p/3565864#U3565864

It sounds very similar to the issues you are having.

[Alexander_Sobolev · Accepted solution]

Can you check if you have sparce matrix toolkit run-time engine in the list of additional installers? 

you can download one from here,

http://www.ni.com/download/labview-multicore-analysis-and-sparse-matrix-toolkit-2014/4741/en/

2014 version is the latest I could find. 

Toolkits versions do not necessarily match LaBVIEW version, MASMT_LINALG.dll should interface correct one

[nrpratt]

I couldn't find the MASM toolkit run-time engine in the additional installers list. However, downloading it from the link you provided did work, so thank you! Is there any way to get MASM toolkit run-time engine included in my installer, so the end user doesn't have to download the RTE seperately?

[Alexander_Sobolev]

It does appear for me

Should be right before Labview run-time engines. It does not care about LV version.

PS. If it does not appear, can you check you installed correct bitness and restarted labview after installing toolkit

[nrpratt]

Finally got it! I only installed the development version of the MASM toolkit on the development computer. I just installed the run-time engine on the dev machince and the option for the MASMT RTE now appears in the additional installers. 

Thanks for all the help Alexander_Sobolev!