08-18-2010 10:24 AM
I have some external code in a dll that is being called thru LabVIEW. In 2009 service pack 1 this was working fine. I just installed LabVIEW 2010 and when this dll is called LabVIEW freezes up and Windows 7 says the program stopped working and closes LabVIEW.
Is there a new setting for dlls that I need to be aware of? Did something change in the way the dlls and used?
08-18-2010 10:26 AM
Is it a Windows DLL or is it a DLL you wrote?
08-18-2010 10:28 AM
It is a dll that was written by someone else in the company.
08-18-2010 01:59 PM
Try setting the Error Checking Level to Maximum in the Call Library Node configuration, see if it provides a more helpful error?
10-08-2010 09:42 AM
I have exactly the same problem.
Does anyone got an idea what has changed???
10-08-2010 09:49 AM
I emailed NI about this problem and it turns out I was using the wrong calling convention for the dll and it worked in 2009 because 2009 had some security settings not set. Here is what NI sent me.
"I have been looking into the LV crash a little more and found out why.
You are using the wrong calling convention in their Call Library Function Node.
If you change it to WINAPI instead of C call the program does not crash.
The problem is not with 2010, its with 2009 . LV 2010 has more security settings enables. If you change the error checking in the CLFN in LabVIEW 2009 to Maximum. Run the VI and you will see that an error is reported. "
10-08-2010 09:57 AM
Problem solved.
It is running again.
Thanks a lot.