Error 1003 while dynamically calling a VI from EXE

[RadhikaPriya]

Hello,

My Test Executive is an EXE and the test modules or the Test Vis are in Source Code format. From the Test Executive the test

modules are called dynamically and executed.Some of the test modules use NI Sound and Vibration toolkit VIs from the

\Vi.lib\AddOns directory.The problem I'm facing is that when the test modules are called from EXE it is not able to locate

and link to the NI Sound and Vibration toolkit VIs and hence returns Error 1003(Open VI Ref error).

Is there any other method other than Source Distribution or including the test modules too while creating the Test Executive

EXE.
Please let me know if anyone has the solution.

Thank you in advance.

Radhika

[SMeserve]

Radhika,

Here are some KnowledgeBase articles that may help you toward a solution:

Error 1003 When Using VI Server in a LabVIEW Application
http://digital.ni.com/public.nsf/allkb/410F2EC66F60F9B0862569EE006F4FA0

Error 1003 with Test Executive Launcher
http://digital.ni.com/public.nsf/allkb/55D9A5578881DCE286256706006DC6F9

These articles are located on National Instruments KnowledgeBase.  You can find the KnowledgeBase and perform searches there by navigating to NI.com, clicking on the Support tab, and selecting KnowledgeBase.

I hope these help.

Stephen Meserve
Applications Engineering
National Instruments

[mesmith-ut]

This thread might help

http://forums.lavag.org/Calling%20an%20external%20LabVIEW%20VI%20from%20an%20EXE-t3161.html&s=9e962b...

[RayFarmer]

Hi Radhika,

With each exe there is an INI file. If you include the searchPath key to include the labview directories then your exe will beable to find the VI.lib vi's.

Have a look at the labVIEW.ini file for this key.

Regards

Ray Farmer

[SAS]

Hi,

I added the following key to my application ini file and have added all dynamic code under this folder-  but this didnt help. I still getting file not found error.

"visearchPath="C:\test"

i have attached the sample exe which just loads any vi dynamically. Try to load a vi with subvis (keep subvis in a separate folder from the toplevel vi). You can see that the dynamically loaded vi couldnt find its subvi and is broken.

Thanks in Advance - I will appreciate your inputs

Sas

[MehakD]

Hi,

Are you running this on a a computer with LabVIEW Development System or just LabVIEW real time?

Try putting "C:\Program Files\National Instruments\<LabVIEW>\vi.lib instead of the Test directory. Also I would recommend you to always include the dynamically called VIs in your source files for the project.