LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Call dll in 2010 no longer works

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?

Brad Remenak
Certified LabVIEW Architect
0 Kudos
Message 1 of 7
(2,849 Views)

Is it a Windows DLL or is it a DLL you wrote?

Cory K
0 Kudos
Message 2 of 7
(2,845 Views)

It is a dll that was written by someone else in the company.

Brad Remenak
Certified LabVIEW Architect
0 Kudos
Message 3 of 7
(2,842 Views)

Try setting the Error Checking Level to Maximum in the Call Library Node configuration, see if it provides a more helpful error?

Message 4 of 7
(2,819 Views)

I have exactly the same problem.

Does anyone got an idea what has changed???

0 Kudos
Message 5 of 7
(2,693 Views)

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. "

Brad Remenak
Certified LabVIEW Architect
0 Kudos
Message 6 of 7
(2,683 Views)

Problem solved.

 

It is running again.

 

Thanks a lot.

0 Kudos
Message 7 of 7
(2,678 Views)