LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Failure to initialize lvanlys DLL

The actual version (2022.1.0.192) of Intel oneMKL was installed following this guide.

It looks like now I should somehow link the installed library with LabVIEW IDE, but I have no idea how. The automatic approach to set environment variables via setvars.sh was not appropriately performed due to the absence of the required IDE Visual Studio in my configuration.
Maybe Link Line Advisor can be used for creating the interface with LabVIEW, but I'm not sure about all configuration parameters and how it should be implemented.

0 Kudos
Message 21 of 23
(481 Views)

Unfortunately upgrading the LabVIEW provided MKL library isn't as trivial as that document makes it appear. LabVIEW uses the MKL library since a very long time (more precisely somewhere around the millennium change). And the MKL back then was a self contained fairly monolithic library that had specific requirement installations when used from other products. It's license also was different back then even for commercial use of it.

 

NI had before that maintained their own advanced analysis library developed in C, but eventually decided that they can't possibly compete with the Intel specialists in trying to squeeze out another percentage fraction of performance out of ever improving CPUs cores and to use the Intel MKL instead of maintaining their own library. But the interfaces for LabVIEW and LabWindows/CVI had been already defined, so they developed a small middle layer that would translate between these two. This middle layer takes care of locating the NI installed version of the MKL, loading it into memory and initializing it accordingly. Intel eventually integrated the MKL in their bigger OneAPI initiative (a few years ago), changed the entire licensing structure that made commercial use of the MKL considerably more expensive as they argued that you get the whole OneAPI infrastructure with it. But they couldn't just change the ongoing agreements with clients on a whim, so NI is still most likely on the old agreement for the MKL only.

 

Currently NI installs their version of the MKL into C:\<Program Files>\National Instruments\Shared\MKL according to the bitness of it. It is shared between NI software packages but independent of any other OneAPI or whatever MKL installations.

So if you want to have this upgraded you will need to install a newer version of an NI provided software installer. A newer LabVIEW runtime version would come to mind.

Rolf Kalbermatter
My Blog
Message 22 of 23
(463 Views)

Thank you, rolfk for your participation and detailed answer.

Upgrading NI Installer and runtimes didn't help with the issue.
I figured out that I should upgrade my LabVIEW version or downgrade the laptop's processor.

0 Kudos
Message 23 of 23
(433 Views)