failed to load shared library

[kmc]

I am getting a "Failed to load shared library myDLL.dll:myFunction:C on RT Target Device" error when attempting to deploy a VI which contains a call to myDLL on a RT PXI.  If I open the VI with the Call Library Function Node and simply reselect myDLL within the Library name or Path box and save the VI, it will then deploy without error.  This continues to work until I start changing the VI at which point I attempt to deploy the VI again and get the failed to load error.  Once again I open the VI, reselect myDLL, save, and the failed to deploy error goes away.

Does anyone have any ideas about whats going on here?

Thanks in advance

Kevin C.

[NI-Bob]

Hello Kevin,

Thank you for contacting National Instruments!  There are a few questions that I have regarding this issue.  First of all, what version of LabVIEW are you using?  What type of RT Target are you using?  I found some information that may pertain to your issue if you are using an older version of LabVIEW.  Please read this Knowledgebase Article and see if this pertains to you.  If it does not then please post your DLL here so that I can try to replicate the issue on my end.  Any extra information that you have would only help to troubleshoot this issue.  I look forward to hearing from you!  Have a great day! 

[kmc]

Hi Bob,

Thanks for responding.  I am running LabVIEW 8.5 and running on an 8106 Embedded Controller.  Unfortunately, I cannot post my DLL however, I did some troubleshooting and found that the issue seems to be that myDLL calls another one of my DLLs which doesn't seem to be loaded onto the RT box.  If I deploy and run a VI which calls this second DLL and then run my original VI, it deploys without issue.  I guess I can understand why it didn't work in first place, since the 2nd DLL is not called from any VI and only called from myDLL, however I don't understand why simply opening the VI which contains the call to myDLL and reselecting it fixes the problem.  Also I have run the DLL thru the 8.5 DLL checker and it says that the DLL is OK, in fact the DLL checker new that myDLL had a dependency on the second DLL.  Is there something that I can do other than pre-deploy the second DLL to the RT box to get around this issue?

Thanks again,

Kevin C.