The program crashes as soon as the IMAQdx session control on the 64-bit labview front panel is used

[Bob_Schor]

I wonder if this is a "licensing issue".  A number of years (maybe 10?) ago, I helped a colleague install a program that monitored animal behavior and used a Web Cam to visualize the behavior.  When we went to install it on the off-campus site, we got asked for a license number for the run-time component of IMAQdx (I think that was VAS, but don't quote me on that).  Once we purchased the license and ran License Manager, we were good.

I suggest opening License Manager on the machine that doesn't work, look at Local Licenses, and see if anything "lights up" (turns Yellow).

Bob Schor

[AS_PV]

That was also my first thought, but i could rule that out. The IMAQdx as well as the VDM Runtime were activated and there were no further prompts for activation while starting any compiled vis.

I even did uninstall everything related to NI just to be sure that there is no version conflicts with IMAQdx and LabView runtimes, with no success. The patchnotes are also kind of kept short 😅 so i could not find anything specific related to this issue.

[SardarM]

Hi all,

Did you find a better solution rather than using 32-bit version? I am getting exact this error on two of the computers. One of the computers was fine last year, but this issue just kicked in.

Thanks!

[aeastet]

I am able to run this in LabVIEW 2024 Q3 64 bit without crashing.

[Bob_Schor]

This is really "far out there", but are any of your PCs running Windows 11?  [I, personally, am dreading when our stable Windows 10 systems are going to be "forced" to use Windows 11.]

Bob Schor

[aeastet]

We have upgraded all our systems to Windows 11. We only have a few more systems to change over. So far the change has been pretty smooth.We have a couple of hundred system running in testing and production environments. We have had more issues with drivers for connected systems than we have with LabVIEW. 

There was a bigger issue when we switched from LabVIEW 2020 to LabVIEW 2024. 2024 was buggy and crashed a lot. So much so that we almost switched back. The patch 2 release help a lot. I just installed the patch 3 last week. Newer versions of LabVIEW seem far more unstable that I am used to over the last 25 years of using LabVIEW. LabVIEW 2024 crashing is a bigger issue. The only way to fix this seems to be to build the code on a different machine. 

[AS_PV]

Sadly, since switching to 32 bit the system at production runs fine (Windows 10), so at least for me, it does not look like an OS issue. But my customer wants to upgrade to win11, we will see if that changes anything 😅

[ChrisM1]

I had that exact same issue. Note that I could stream from a GigE camera without problem in Vision assistant 32-bit while the 64-bit version did not see the camera at all. The issue was caused by the SentinelOne agent antivirus installed on the PC. Disabling it solved the issue.