'Call Library Function Node' error

[VictoryNeal]

Hi all,

I am stuck at an error from the function called 'Call Library Function Node'. I wired correctly and wired all inputs and outputs that need to be output, but there is still the error here.

I also set the right library path.

To be clearer, the folder is also attached here:

Any advice will be appreciated. Thanks in advance.

LabVIEW 2013 sp1 32-bit in Windows 10

[LLindenbauer]

The culprit is this setting:

With "Specify path on diagram", the node expects the input to be wired (it's the top one with the path symbol). So you could either wire that one up or uncheck the box and use the "Library name or path" field like you already do. There are some more automagic tricks going on when LabVIEW tries to sort out which DLL to load and what to do with them afterwards - I'd like to refer you to the manual, which is possibly accessible here: https://www.ni.com/docs/en-US/bundle/labview/page/glang/call_library_function.html

[VictoryNeal]

Hi LLindenbauer,

Thanks for your reply. Check or uncheck the box doesn't make the program run. I also read the link and found it only introduces the basic fact about the function node.

[VictoryNeal]

The error message changes to below, which still makes no sense because the library name is completely right.

I also found many solutions to this error from internet, but none of them works here.

[rolfk · Accepted solution]

The DLL itself may be there but one of its dependencies is not. LabVIEW can’t (and shouldn’t even try to) check the dependencies of a DLL. All it does is to ask Windows to load that DLL. Windows analyzes it and tries to load any dependencies that DLL has (and any dependency those dependencies may have and so on) and if any of them fails, the DLL can’t be loaded and Windows simply tells LabVIEW: “Sorry pal but I can’t load the DLL you asked!”

So you have to find out what other dependencies your DLL has. One common culprit is the C runtime library for the compiler version that was used to create the DLL. But it can depend on any other DLL the developer found useful to use. This is something the developer should have understood and providing a real installer for the DLL that makes sure all the requirements are installed too for the actual OS version. Copying DLLs between computers is a pretty sure way to run into such problems (or worse) and you should use a real installer instead.

[VictoryNeal · Accepted solution]

Hi Rolf,

Thanks for your adivce. It is very helpful because there are a few dependencies missing. The program I am using is indeed directly copy from other computer, without a installer, because the author didn't write one. The problem is solved, so I share some information I used below:

I use

https://github.com/lucasg/Dependencies

to check the file 'StackWritterWrapper.dll' and found there were 3 DLL files missing. Then I found the missing 3 dependencies are in other folders, so I move them to the same folder as 'StackWritterWrapper.dll'. Problem solved!