Fatal Error "can't locate DSSetHandleSize"

[Doug Asselbergs]

I’m having problems with one of my applications that I can’t debug.  I’ve been having a lot of problems lately with com ports not getting passed to subvis properly so the subvi doesn’t work because the com port isn’t correct.  Simply rebuilding the app fixes it but now I can’t even troubleshoot that far. 

Now, for some reason, this application keeps crashing when I try and do a remote debug.  I can open the app using remote debug but when I open the subvi, I get a Fatal Error “Labview.lib could not locate DSSetHandleSize” on the target computer.  Near as I could tell from searching in the forums, this has something to do with linking DLLs or something but I’m doing nothing of the sort in this application.  This is an application that hasn’t changed at all in the area that I’m debugging in many months. 

I’ve tried rebuilding the app to see if would magically disappear like the com port problem I’ve bee trying to debug but that didn’t seem to work.  This app is an EXE that I’ve built using Labview 8.0 running on one of the test computers in the manufacturing area that seems to run all the other labview apps OK including this app with the exception of the comms problem I’m trying to debug.  This target computer doesn’t have a file labview.lib but then it shouldn’t need to since it’s not running Labview, right?

Does anyone have any idea what this message could mean?

Like I said, this app was built using Labview 8.0 on Win XP.  The target computer is running Labview Run time 8.0, DAQmx 8.0.0f0, NI VISA 3.4, NI Serial 1.8.1., and Win2k.

Thanks,
Doug

[Rudi_N]

Doug:

Sorry for the late reply. It seems like the issue may still be related to the com ports. I would suggest to write a simple application that opens a visa session, reads and writes from an instrument and closes the session. You could also post the portion of your VI that causes the error so that I can reproduce it on my end. I hope this helps.

Thanks,

Rudi N.

[Doug Asselbergs]

I’ll try to strip out all the proprietary stuff and see if the error is reproducible with that.  The problem is that it only happens with the built executable running on a machine that doesn’t have full labview installed.

Thanks,
Doug

[Rudi_N]

Doug:

Thank you very much for getting back with me. Please let me know when you are able to reproduce the issue with a stripped down version of the code.

Thanks,

Rudi N.