05-09-2017 12:25 PM
Hi all,
I have a labview project that was left behind by a former co-worker that I've been tasked with investigating. When I try to open his main VI, I get an error that the VI could not be opened due to missing dependencies in the dynamic library. I already updated a bunch of links to missing VIs in the lvproj file. As far as I can tell, the main VI was loading a bunch of functions from a LLB that I have unpacked and re-linked to, and I can open the VIs in the LLB.
Does anyone know a way to show which dynamic library (I'm assuming this is a .dll) is messed up?
Thanks
06-06-2017
09:05 AM
- last edited on
01-10-2024
01:51 PM
by
migration-bot
Hello,
You are provided a link on how to access functions contained in DLLs.
Please note that this method requires Primary LabVIEW version 2011.
Obviously it will work with later LabVIEW versions as well
Does it solve your problem?
06-06-2017 09:16 AM
How large is the application? I'd scan through it quickly (assuming this is possible) looking for a Call Library Function Node.
That at least tells you which DLLs you're looking for. From there, I'd want to know how many there are. If it's possible, I'd start using a Diagram Disable around some of those CLFNs to see which DLL is throwing the error. From there, I'd focus my effort on that single DLL call.