LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabView Application Fails to Run

I created an EXE file using LabVIEW 2021 SP1f6 (because of myRIO support).
It runs perfectly on my PC (with the full version of LabVIEW 2021), but on another PC with only LabVIEW Runtime 2021, the following error occurs (see iamge)

 

Do you have any ideas what might be causing this?

0 Kudos
Message 1 of 8
(895 Views)
Hi Johann,
 

There are several possible reasons why an EXE might fail while the code works fine in the LabVIEW IDE (missing DLLs, incorrect file paths, incompatible runtime version, etc.).

Could you post the contents of the error report? That might help narrow down the cause.

Best,
Juan

0 Kudos
Message 2 of 8
(858 Views)

Hi,

 

The error report is an unreadable dmp file...

 

- I have built the exe with LabView 2021 SP1f6, the installed (and just reinstalled) runtime is LV 2021 SP1f6.

- It looks like that all DLLs are available (If the main used DLL is missing, the application opens with a broken arrow and does not execute. A DLL check of this DLL shows, that no DLLs are missed for this main DLL.)

- An installer for this application would install only the LV runtime, nothing else is needed.

 

 

Thanks!

Hannes

0 Kudos
Message 3 of 8
(847 Views)

Hi Hannes,

 

I had a look at the crash dump using WinDbg. I wasn't able to identify the root cause directly, but I noticed something interesting: according to the dump, the application was running with the LabVIEW 2025 Runtime Engine (lvrt.dll, version 25.1.3.4003), although you mentioned building the EXE with LabVIEW 2021 SP1 f6.

If you want to ensure that the EXE uses the Runtime Engine version it was built with, you can uncheck "Allow future versions of the LabVIEW Runtime to run this application" in the Advanced section of the EXE build specification.

 

Could you double-check which Runtime Engine versions are installed on the target PC?

 

Does the EXE run correctly on your development PC?

 

If both PCs are on the same network, I would suggest building an EXE with debugging enabled (including the "Wait for debugger on launch" option). You can then connect to the application running on the target PC from your development PC, open the block diagram, and step through the execution to identify where the problem occurs.

 

Best,
Juan

0 Kudos
Message 4 of 8
(816 Views)

Apparently you start with an invalid parameter.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 5 of 8
(803 Views)

Hi Juan,

 

Thanks for your comments.

I double checked, the PC were I tried used LV Runtime 2025. But the application is not running on two other PCs with definitely LV RunTime 2021.

 

In addition, I have a set of applications. Three of them are running without problems, only this one makes troubles.

 

I will try to start the application with the debugger (I have never tried this).

 

Best,

Hannes

0 Kudos
Message 6 of 8
(790 Views)

Hi Hannes,

Remote debugging is super useful in my opinion, here is an official NI article on how to do it:

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YHpiCAG&l=de-DE

Beware that for this also the Runtime Engine version is important: if it is not the same as your IDE LabVIEW will not be able to find the running exe.

Best,
Juan

Message 7 of 8
(773 Views)

Hi

 

The error seems to refer to a special VISA driver ??

 

I would as first step open NI MAX and use  File -> Create Report on each computer, working and not working, and then compare the reports to see if something is different.

 

Regards

Message 8 of 8
(747 Views)