LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEWV.lib could not locate NumericArrayResize

Hi,

 

I have a LabVIEW application that was created a while ago by someone who left the company. It was created  with 8.2.1 and  runs smoothly most of the time,

 

every once in a while, we get a MessageBox with title bar "Fatal Error" and text "LabVIEWV.Lib Could Not Locate 'NumericArrayResize'" as shown in the attachment.

 

The setup includes several measurement equipment (GPIB and LAN),  and also  a couple of DAQ modules and a RIO module,   not sure which of them is being used by the application.

 

The error message seems to occur at random.

 

The LabVIEW application uses a lot of LabVIEW features that I wish never existed ex.  sequences, shared variables, and the shared variables are used to communicate between different LabVIEW executables running simultaneously on the same machine

 

is there any workoarund for this problem

 

thanks

Joe

Download All
0 Kudos
Message 1 of 4
(2,482 Views)

Can you post the code? That would be the easiest way for us to assist.

 

It sound to me like somewhere in the program a reference to a vi is opened and at some later point closed but a different part of the code still needs the VI. My best guess.

Tim
GHSP
0 Kudos
Message 2 of 4
(2,479 Views)

Thanks,

 

it is difficult to post the code, all I can say is that  all the code  is written in LabVIEW, and  uses drivers for vaious instruments.

 

I searched on the internet and found only 1 other  situation where the exact same message appeared, however his/her  request was not resolved

 

 

http://forums.ni.com/t5/LabVIEW/Labviewv-llb-could-not-locate-NumericArrayResize/td-p/1092781

 

Thanks

Joe

0 Kudos
Message 3 of 4
(2,458 Views)

Hello, Joe!

 

It looks like that particular file is missing from the labviewv.lib file. Note that "labviewV.lib" is not actually a type, it is its own library file native to LabVIEW.

 

Have you tried repairing LabVIEW, as suggested by the other thread?

 

Once you've tried this, there are a few steps to take if it does not fix you issue. First, you'll need to determine (if possible) if your VI is linking the libraries statically (at startup) or dynamically (while running). See Calling a LabVIEW-Build Shared Library (about half way down) for more info on linking types. Also to note, you said this is a LabVIEW application, meaning a built .exe? Or do you have a project file used to build the application?

 

Please let us know if the repair does not do the trick!

 

Will Hilzinger | Switch Product Support Engineer | National Instruments
0 Kudos
Message 4 of 4
(2,441 Views)