Exception occurred with external code called by Call Library Node w/IMAQ Draw Text

[sundance]

Following reinstallation of LV7.1 & IMAQ 3.1.1 & LV Vision 6.0 I was unable to run VI's that formerly ran fine. First there were typedef errors, followed by non-executable sub-vi's and now I get the following: "An exception occured within the external code called by a Call Library Node. this might have corrupted LabVIEW's memory......VI...was stopped at node 0x1D8 of subVI "IMAQ Draw Text" ". I've tried the Draw Text vi in small demo programs and it seems to work fine outside of my main program. There may be more of these exceptions but I can't get past this first one.

I'm running a single PCI-1411 board & when I run MAX there is no problem.

Can anyone help? 

[MacleanG]

Hi Sundance,

Thanks for posting on the NI forums!  When you say the VIs ran fine previously, do you mean they were created with the same version of installers you listed?  Have you tried a Mass Compile of your NI directory? It sounds as if for some reason the subVIs in your program are pointing to the wrong directories, and a mass compile would highlight/correct those errors.  If that doesn't work, or if you do find subVIs that are broken, replace the subVIs manually in the block diagram, which will replace the old subVIs with subVIs from the LV7.1 library directories.

I hope this helps,

[sundance]

Regarding the recompile suggestion...I will certain keep that idea in my bag of tricks for the future. I got my programs to run just prior to receiving your note. Here's what I did to get things running: First, I totally uninstalled all LabVIEW products from the PC. Then I reinstalled LabVIEW 7.1 with a minimum number of drivers (IMAQ 3.1.3 which came with it, NI-DAQmx & NI-DAQ and the Motion Control Drivers). Then I reinstalled NI-Vision 6.0.1 immediately followed by installing the Vision upgrade to 6.0.3. Then I transfered all of my user vi's, which had been on a separate server, to the user vi folder in the LV7.1 folder on the PC (part of the pointer problem you referred to?). My program came up normally on the first try as if nothing had ever been wrong.  In further investigation on the website I found that LV7.1 isn't supposed to be compatable with Vision 6.0, but evidently something in the procedure above worked.