LabView: Resource not found
LabView: Resource not found, a forum discussion on Cleverscope Mixed Signal USB Oscilloscopes. Join us for more discussions on LabView: Resource not found on our Installation Issues forum.
I am trying to launch the app but I keep receiving
"LabView: Resource not found.
lvanlys.dll "
I am using Windows 11. Can that be the problem?
You must be logged in to post a reply
![]() |
![]() |
murat
10 Oct 2022
Posts: 2
I am trying to launch the app but I keep receiving
"LabView: Resource not found.
lvanlys.dll "
I am using Windows 11. Can that be the problem?
bartschroder
10 Oct 2022
Posts: 471
Hello Murat,
Do you have Labview already installed on your system?
Also, which version of the app are you installing - the 32 bit or 64 bit versions?
Make sure you run setup.exe to install, and answer yes to all install questions.
Thanks,
Bart
Cleverscope
Do you have Labview already installed on your system?
Also, which version of the app are you installing - the 32 bit or 64 bit versions?
Make sure you run setup.exe to install, and answer yes to all install questions.
Thanks,
Bart
Cleverscope
murat
10 Oct 2022
Posts: 2
I did not install Labview.
The version is x64.
And yes, I clicked on "yes" to all install questions.
The version is x64.
And yes, I clicked on "yes" to all install questions.
Hi Murat,
There is a bug in Labview running on AMD processors. It has been fixed in v2020 but we currently use v2017. The problem is actually with the loading of lvanlys.dll and Windows make the wrong call so we have to tell it the correct value.
Here is the fix-
1) Add a new environmental variable in Windows: Control Panel » System » Advanced System Settings » Advanced » Environment Variables » System variables (the bottom part of the dialog) » New
2) Put MKL_DEBUG_CPU_TYPE as Variable name
3) Put 4 or 5 as Variable value
4) Confirm OK multiple times to close all dialogs
5) (A Windows restart might be needed.)
Ng? mihi,
Roger
There is a bug in Labview running on AMD processors. It has been fixed in v2020 but we currently use v2017. The problem is actually with the loading of lvanlys.dll and Windows make the wrong call so we have to tell it the correct value.
Here is the fix-
1) Add a new environmental variable in Windows: Control Panel » System » Advanced System Settings » Advanced » Environment Variables » System variables (the bottom part of the dialog) » New
2) Put MKL_DEBUG_CPU_TYPE as Variable name
3) Put 4 or 5 as Variable value
4) Confirm OK multiple times to close all dialogs
5) (A Windows restart might be needed.)
Ng? mihi,
Roger
[editor:html]
Back to Forum Index : Back to Installation Issues |
![]() |