From: cphuong on
Hi Chin
Lin,

I was able to run the executable on a test machine.  The test computer was
free of any National Instruments software.  I installed the LabVIEW
Run-time Engine 8.2 from <a href="http://digital.ni.com/softlib.nsf/websearch/9bced01b8f69f8a0862571bf0078ff96" target="_blank">this</a>
website, then ran the executable file.&nbsp; The executable ran without error.

Did you try to run the same executable that you used to build your
installer?&nbsp; To build an installer, you need to first build and executable
that you include in the installer.&nbsp; Try using that executable, and see if
you still get the error.

Please let me know if you have any questions.&nbsp; Best of luck on your
application, and have a great day!!
From: J. Mondry on
Hallo,
I had the identical problem and was able to determine it's cause (at least for me).
&nbsp;
What I (erraneously) did, was to install the wrong LV 8.2 Runtime on the target machine first (the "light" one [2x MB] for browsing VIs). Then I installed the proper 8.2 Runtime over it (since I could not uninstall the wrong one - it doesn't show either in "Add/Remove Programs" or in "National Instruments Software").
&nbsp;
When I then tried to run a freshly built 8.2 Executable on this taget machine then I got the very same error message about not finding the front panels of several *AA*.lvlibs ... the same error Chin Li got.
&nbsp;
So what worked for me is: radically clean the target machine of NI stuff (i.e. that being an XP machine I rolled it back to a day before I tried all this). Then I freshly installed the correct 8.2. Runtime (the big one) and now my executables run fine.
&nbsp;
So I think maybe the reason Ching P. couldn't reproduce Chin's problem is&nbsp;that he did&nbsp;exactly that on a real fresh machine and Chin's target machine only "looked" like fresh because the wrong RT still lurkes somewhere.
&nbsp;
It is very bad naming policy by NI by the way, to name both these thing "LabVIEW Runtime 8.2", lots of people will get confused ...
&nbsp;
hope this helps
Jens
From: Chin Lin on
Hi Jens:
Thanks for your information. From the day one, I&nbsp;was using the correct RTE8.2. I was using the one in the Labview Professional Development System 8.2 CD. I then downloaded the RTE 8.2 from the NI website and they look the same and have the same size.
If what you said is correct, then this is very bad because&nbsp;not many have backup their system before installing any software.
I&nbsp;think my problem maybe due to the fact that my target system is not clean. The system has been used for running LV6.02 program with many other NI drivers installed (DAQ, VISA,....). I am investigating converting my LV6.02 program to LV8.2 to deloy&nbsp;it to my production machines.&nbsp;I&nbsp;can not clean them before installing RTE 8.2. This is just not acceptable. Hofully this is not the root cause.
Thank you.
Chin Lin
From: Chin Lin on
Hi:
I finally found out the root cause. Initially I installed the LV RTE 8.2 from the NI Labview 8.2 Dev CD which getting error when running the vi .exe. I then go to the NI website to download the RTE 8.2 which is about 94MB. When executing the setup.exe, there were 5 items to select for installation:
NI Labview RTE 8.2Variable EngineDatasocketLabview Deployable LicenseUSI
I selected only NI Labview RTE 8.2. When installing in progress, I noticed that there were 7 parts in total (these are part of the package and can not be unchecked):NI EULA DepotNI MDF SupportNI Logos 4.7NI Labview RTE 8.2NI Math Kernel LibrariesNI Service LocatorNI TDMS
After installation, the .exe file was able to execute without problem. So by just installing the RTE 8.2 (lv82runtime.msi), it won't work. Then I uninstalled all the components of RTE8.2 and installed just the NI Labview RTE 8.2 and NI Math Kernel Libraries from my NI Labview 8.2 Dev CD. Now it also work.
So in summary, we need to use the RTE 8.2 from the NI website to install which will automatically install the extra components for us to get the .exe work. I was wrong to assume that we need only the RTE 8.2 to run&nbsp;a&nbsp;labview&nbsp;.exe.
Thank you.
Chin Lin
&nbsp;