LabView crash the second time I'm configuring Call Library Function node.

[Michel_Gauvin]

When configuring the .dll for the first time in LabView I'm able to save
that configuration and execute the VI. I'm executing the function
PxLInitialize (one of my .dll function), and I'm getting at the output the error code 0x80000001 which
is the error code corresponding to Unknown error (error from the .dll). When re-configuring the
.dll in LabView I see the exported functions from the .dll in the
configuration panel as before in the "Call Library Function Node" but when I
click "OK" on the configuration panel it's telling me that "The function
node specified for this node cannot be found in the library." ----- This
error is generated in LabView 6.0

If I do the same exercice in LabView 6.1 the second time I'm trying to
configure the .dll LabView.exe process crash.

Here is the output data from Microsoft Visual Studio .NET debbuging
processes tool when LabView.exe (Version 6.1) process crash:

'LabVIEW.exe': Loaded 'C:\WINNT\system32\PixeLINKAPI.dll', No symbols
loaded.
'LabVIEW.exe': Loaded 'C:\WINNT\system32\JPEGDLL32.dll', No symbols loaded.
First-chance exception at 0x77eab2f0 in LabVIEW.exe: Microsoft C++
exception: OutOfMemoryException @ 0x0012e0b0.
'LabVIEW.exe': Unloaded 'C:\Documents and Settings\miga\Desktop\MIGA
TEST\PixeLINK_Wrapper\PixeLINK_Wrapper\Debug\PixeLINK_Wrapper.dll'
'LabVIEW.exe': Unloaded 'C:\WINNT\system32\PixeLINKAPI.dll'
'LabVIEW.exe': Unloaded 'C:\WINNT\system32\JPEGDLL32.dll'
First-chance exception at 0x008f9526 in LabVIEW.exe: 0xC0000005: Access
violation reading location 0x00000000.
Unhandled exception at 0x008f9526 in LabVIEW.exe: 0xC0000005: Access
violation reading location 0x00000000.

It's doing it by configuring the Call Library Function node as UI Thread and reentrant. I don't need to execute the VI to get that crash, simply re-configuring the .dll the second time everything crash, so I don't resize any array...
Another way LabView crash is by configuring the Call Library Function Node, save the VI, close the VI without exiting LabView and then re-open the VI, LabView crash.
Can somebody help me on this one??????

[JRA]

It sounds like this is a problem with the DLL which you are calling. I have never had anything like this happen before, and I have called many DLLs through LabVIEW. One thing I would suggest is check to see if this DLL depends upon any other DLLs to run. If so, confirm that those are located on your machine. It sounds like it is hanging, so this is most likely due to the fact that it is looking for something that does not exist on your machcine: DLL, ActiveX server, etc. When you find out about this, let us know what you learn, and hopefully we can help you further with this.

[Michel_Gauvin]

Thanks for the answer, I've work on this issue with our customer and it turns out there was an unhandled exception being generated by the API if
it was loaded multiple times by the same application.

[JRA]

That is very interesting. I bet that it was tough to track down, but I'm glad you found it. Best of luck with your application!