call library function node error 13

[Rammer]

We just upgraded to LV 2010. Now one of our VI's does not function. It calls a custom dll with the call library function node VI. It now reports error 13. The path to the dll is correct. Does anyone have any suggestions?

John

[crelf]

Error 13 (you can find error code descriptions under Help > Explain Error, or by right-clicking on an error cluster code and choosing "Explain Error") means:

Possible reason(s):

LabVIEW: File is not a resource file.

=========================

NI-488: Shareable board exclusively owned.

It fails when you run it, or is the run arrow broken?

[Rolf Kalbermatter]

We just upgraded to LV 2010. Now one of our VI's does not function. It calls a custom dll with the call library function node VI. It now reports error 13. The path to the dll is correct. Does anyone have any suggestions?

John

One possible problem might be that the DLL is a 32bit DLL and you were using it in the 32 Bit version of LabVIEW and now have upgraded to LabVIEW 2010 64Bit. LabVIEW only can call DLLs compiled for the same environment as it is itself. If this is the case you have two options:

1) Install LabVIEW 2010 32Bit which will work fine on a 64 Bit Windows version

2) Recompile your DLL for Windows 64Bit (and review it for any bitness issues)

This review would encompass things such as that the Call Library Node is configured right: Windows 64 bit uses obviously different pointer sizes which could be a problem if you have configured pointer parameters to be treated as integers, but using the new pointer sized integer type since LabVIEW 8.5 would then be the right thing instead of explicit 32 bit or 64 bit integers

Also there is a difference in size between long: Windows treats longs always as 32 bit while everyone else treats a long as 32 bit on 32 bit platforms and 64 bit on 64 bit platforms. Use of long long instead in the C code avoids that problem as it is always 64 Bit but it is a C99 feature only so it may have problems with older compilers and also C++ compilers who don't support the upcoming C++0x standard not being able to recognize it.

[abrissbirne]

We just upgraded to LV 2010. Now one of our VI's does not function. It calls a custom dll with the call library function node VI. It now reports error 13. The path to the dll is correct. Does anyone have any suggestions?

John

Same problem here. After updating LV to LV2010 (32 Bit) and MS Visual Studio 2010 my dll causes error 13. Anybody fixed that prob?

thx

[abrissbirne]

I fixed the problem but it isn't really a fix. It is more a workaround.

- Place the Cll library function node on the blockdiagram of the vi that generate the error.

- Set the properties by hand.

- Replace all call library function nodes like this.