LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Call Library Function Node: Library not found or failed to load

Solved!
Go to solution

Hello Everyone,

 

I have reviewed other topics that have been opened for the error that you can see in the photo below and tried many things but I did not succeed.

 

I am uploading the files so that you can try them. I would be grateful if you can help me. I spent too many days on this 😞

 

CekirgeBey_0-1734508155363.png

 

0 Kudos
Message 1 of 6
(140 Views)
Solution
Accepted by CekirgeBey

First, that DLL is 32-bit only. If you are not using 32-bit LabVIEW it won't be able to load it at all.

Second, that DLL has three hard dependencies. One is the Microsoft Visual C Runtime library 14.0 (that should be fullfilled on any system that runs Windows 10 or 11), one is wpcap.dll and the other is packet.dll.

wpcap.dll is from the WinPCap package, but that's unsupported since several years and considered obsolete. You can install NpCap instead and select during installation to install WinPCap compatibility support. That usually works but there is no warranty!

Packet.dll is another component from the WinPCap package. But I 'm not sure that NpCap's compatibility mode goes as far as supporting that too.

 

If you check on the Siemens site you can find https://support.industry.siemens.com/cs/document/99684399/sinamics-g-s-profinet-connection-with-labv... and on there also https://support.industry.siemens.com/cs/attachments/99684399/99684399_SINAMICS_LabView_connection_v4... which tells you all these dependencies.

 

But basically, PNIO.DLL is from an old Siemens product "PROFINET IO-Developer’s Kit" that has been discontinued long ago. Use of that in new applications is simply unsafe and unsupported. It will definitely fail once LabVIEW is 64-bit only, as it does not seem like Siemens will go and update that DLL to support 64-bit.

Rolf Kalbermatter
My Blog
Message 2 of 6
(131 Views)

@rolfk wrote:

First, that DLL is 32-bit only. If you are not using 32-bit LabVIEW it won't be able to load it at all.


Yes, this is true, but in this particular case it is 32-bit already, nowadays the latest version are different by icon's color:

Screenshot 2024-12-18 10.23.25.png

So, it looks like missing dependencies.

 

0 Kudos
Message 3 of 6
(109 Views)

@Andrey_Dmitriev wrote:

@rolfk wrote:

First, that DLL is 32-bit only. If you are not using 32-bit LabVIEW it won't be able to load it at all.


Yes, this is true, but in this particular case it is 32-bit already, nowadays the latest version are different by icon's color:


That was just my first thought. MSVCRT14 is unlikely to the be the problem, but I doubt he has installed WinPCap. And considering its current status it is rather questionable if you should try to install that. Operation on recent Windows 10 systems is most likely not possible and even if it is possible, it is highly unsafe.

Rolf Kalbermatter
My Blog
0 Kudos
Message 4 of 6
(96 Views)

Thank you very much! 

 

I install WinPCap package and Microsoft Visual C Runtime library 14.0 than it works. Before I have already added wpcap.dll and packet.dll.

0 Kudos
Message 5 of 6
(88 Views)

@CekirgeBey wrote:

Thank you very much! 

 

I install WinPCap package and Microsoft Visual C Runtime library 14.0 than it works. Before I have already added wpcap.dll and packet.dll.


Never randomly copy DLLs if you can avoid it in any way. The only one knowing of any specific dependencies, is the actual installer of a component. In the case of WinPCap it's most likely for instance an older version of the Microsoft C Runtime library, which is not guaranteed to be present on a Windows 10 and 11 system anymore.

Rolf Kalbermatter
My Blog
0 Kudos
Message 6 of 6
(62 Views)