An exception occured within the external code called by a Call Library function Node

[molecularvisions]

Good Morning,

I built a VI that contains Matlab nodes in Labview 8.0.  I made an executable and gave it to a colleage to use who is running Windows XP.  I see in the folder C:\Program Files\National Instruments\Shared\LabVIEW Run-Time that she has 7.1 and 8.0 run time engines installed.

On Friday the executable ran great on her machine.  Today, when she tried running it I received the following error.  "LabVIEW:  An exception occured within the external code called by a Call Library Function Node.  This might have corrupted LabVIEW's memory.  Save any work to a new location and restart LabVIEW.  'my vi' was stopped at node 0x0 of subVI "NI_AALBase.lvlib:Real A x B.vi:1".  This error occured after part of the program ran properly.  More specifically, two of the matlab nodes ran perfectly.  I am unsure about the third because the program stopped too early.  I do have to multiply two matrices using the subvi Real A x B.  Is this causing the error?

I also saw this error when I installed it on another computer.  However I do not see this error when I run the executable or the main vi on my machine  I know there are other discussions on this topic, however I do not know why it would affect some machines and not others.  Also, I do not know why it would work on Friday and not on Monday.  Should I have checked the box that said "Enable Debugging" under the advanced section when building the executable?

If anyone could help, I would be very appreciative.

Thanks,

-Richard

[Ipshita_C]

Hi Richard,

As the message already mentions NI_AALBase.lvlib:Real A x B.vi:, it appears that there could be two possibilities:

1. Something in that VI is referencing a memory location that does not exist or it is accessing memory locations too many times which would fill up memory everytime that VI is fetched. So there is a likelihood of it being a memory problem.

2. There could be an exception caused at something the Call Library Function Node is referencingin LabVIEW internal files.

I would definitely enable debugging for the next time and when LabVIEW crashes again, send the log file to National Instruments--the program itself will give you an option to do so. 

Ipshita C.

[rolfk]

---

molecularvisions wrote:

Good Morning,

I built a VI that contains Matlab nodes in Labview 8.0.  I made an executable and gave it to a colleage to use who is running Windows XP.  I see in the folder C:\Program Files\National Instruments\Shared\LabVIEW Run-Time that she has 7.1 and 8.0 run time engines installed.

On Friday the executable ran great on her machine.  Today, when she tried running it I received the following error.  "LabVIEW:  An exception occured within the external code called by a Call Library Function Node.  This might have corrupted LabVIEW's memory.  Save any work to a new location and restart LabVIEW.  'my vi' was stopped at node 0x0 of subVI "NI_AALBase.lvlib:Real A x B.vi:1".  This error occured after part of the program ran properly.  More specifically, two of the matlab nodes ran perfectly.  I am unsure about the third because the program stopped too early.  I do have to multiply two matrices using the subvi Real A x B.  Is this causing the error?

---

This is most likely an error with the use of the Call Library Node, but not in the Real A x B.vi itself. This is a VI that comes with LabVIEW and has been tried and tested many times and unless your LabVIEW installation is messed up simply shouldn't fail in such a way on its own.

However you do include Matlab code somewhere and that might be more likely to cause this. Are you using the built in MathScript node or some other way to communicate directly to a Matlab DLL or such?

Are you using anywhere Call Library Nodes that you have created or that did at least not come standard with LabVIEW?

Rolf Kalbermatter

[molecularvisions]

I was really interested in this call library node, because I am not familiar with what it is.  As such, I did not place one in my VI.  However, I doubleclicked on the the Real A x B subvi and found its block diagram has a call library node.  So, what I did is move the real matrix multiplication from the labview Real A x B subvi into a Matlab node.  It has run fine since.

As for the Mathscript node, I am unimpressed.  Calculations take much longer to perform and not all command lines are compilable as of yet (what the NI guy told me at an expo).  For my Matlab node, I just right click and add it to the block diagram.  I had to update the mathscript.dll file in order for the Matlab command window to pop up however.

Thank you all very much and you all have been very helpful.

Best,

-Richard