02-23-2018 06:14 PM
On a new HP computer running Windows 10, I've installed LabVIEW 2017, and am encountering the following error.
When I try to load any code that contains subVIs which initialize the lvanlys library, or I try to place such a subVI (for example, the "Mean" subVI) into a code, I get the following error message:
Error loading "C:\Program Files\National Instruments\LabVIEW 2017\resource\lvanlys.dll" A dynamic link library (DLL) initialization routine failed.
For the "Mean" example (code example attached), this error occurs twice, and then the subVI will place in the code. However, the code will still return an error (see attached PNG file).
Digging into the subVI, I see that it's trying to call the path:
e:\builds\penguin\labview\branches\2017\dev\dist64\resource\lvanlys.*
I assume this is a part of the build environment, but don't really understand it.
Looking at other forum posts, I've checked:
I've tried uninstalling/installing three different ways (through my campus software library link, through the National Instruments website, and through the National Instruments website using the online installer), including deleting all National Instruments folders when I uninstall, and get the same error each time, and my department IT has been unable to solve it.
Thank you for any help!
02-23-2018 06:36 PM - edited 02-23-2018 06:42 PM
02-23-2018 06:45 PM
02-23-2018 07:59 PM
I still don't understand your comment about run time engines.
02-24-2018 05:17 PM - edited 02-24-2018 05:17 PM
I'm having trouble finding the precise forum posts that I saw before, but from at least one where a similar dll intialization issue was occurring, one of the comments was to check the installed run-time engines using NI MAX:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P8WzSAK
It could very well be that run-time engines aren't actually relevant to this issue. I'm not very knowledgable about many things under the LabVIEW surface, so I appreciate any insights.
02-25-2018 10:32 AM
After you get the dialogues pop up, it sounds like the code runs. Is that correct? Or, am I misunderstanding that entirely?
If it does, will saving the VI bring it up a second time without error?
02-25-2018 04:18 PM
No, the code won't run.
The VI will visually place onto the block diagram once I get through however many error pop-ups are generated, and similarly, the code will load after these errors. For example, for the "mean" VI, the error is returned once when the code tries to load, LabVIEW then searches for the resource again, and returns the error a second time. More complicated mathematical subVIs return the error more times, probably because they call the lvanlys dll more than once.
Saving the VI and reloading it results in the same errors. Once loaded, the code is still broken, and returns the attached error list if I try to run the code.
04-04-2020 10:59 AM
I have the same problem. Did you ever resolve it?
04-04-2020 11:15 AM
Does your computer contain an AMD Ryzen CPU?
04-04-2020 02:47 PM
My system runs AMD Ryzen 7 3700X 8-Core Processor 3.59 GHz