LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Failure to initialize lvanlys DLL

See this solution (also read the entire thread). Good luck!


LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
0 Kudos
Message 11 of 16
(405 Views)

Hi,

 

If you have installed 64-bit LabVIEW: Then install runtime engine also 64-bit.

 

Note: LabVIEW 64 bit is not supported with many functionalities, libraries, and dll's. So if possible please use 32-bit.

 

0 Kudos
Message 12 of 16
(388 Views)

@Bathank wrote:

If you have installed 64-bit LabVIEW: Then install runtime engine also 64-bit.

 


No, if you have LabVIEW installed, installing the run time engine is already included and not needed. Please don't spread false information. Thanks.

 

 


@Bathank wrote:

 

Note: LabVIEW 64 bit is not supported with many functionalities, libraries, and dll's. So if possible please use 32-bit.


Most modules and toolkits are now supported in 64bit LabVIEW. Here is the current list with further links.


LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
0 Kudos
Message 13 of 16
(386 Views)

That solved my problem, but it took me a while to implement the change.

 

For the next person who isn't experienced with modifications to their environment, this is how I did it (Windows 10):

1. In the search box (bottom left), type "environment", and select "edit the system environment variables".

2. In the System Properties window, selec the "Environment Variables" button

3.Select "New"

4. Type "MKL_DEBUG_CPU_TYPE" in "Variable Name"

5. Type 4 in "Variable Value"

6. Accept the changes, close back out, restart, and everything works

 

 

PS.  I chose to assign the variable =5  for reasons that were raised on other BBs and it works too

Message 14 of 16
(369 Views)

@Bathank wrote:

Hi,

 

Note: LabVIEW 64 bit is not supported with many functionalities, libraries, and dll's. So if possible please use 32-bit.

 


This blanket statement was true a few years ago but definitely doesn’t anymore. While there are third party providers who haven’t updated their Toolkits and binary drivers to work in 64-bit applications, there are nowadays also third party suppliers who will only dupport 64-bit anymore.

For most NI drivers and Toolkits, except legacy ones, both are supported and the time is quickly approaching where 32-bit support belongs to the legacy software!

Rolf Kalbermatter
Averna BV
0 Kudos
Message 15 of 16
(352 Views)

Same issue with my Ryzen 7 4800 8 cores CPU. Problem solved with the steps proposed but with 5 instead of 4 core. Thank you.

0 Kudos
Message 16 of 16
(185 Views)