LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to find & repair the missing Subvis in EXE ?

tst,

The point I m repeatedly trying to emphasise is, as you know well, LV should NOT AT ALL ask for a dll that is already owned by it, during the build-time or ever thereafter.

All these years this project has been existing in our company [now the 4th yr running], LV has not ever asked for that dll [for that matter, any other dll owned by it] during build-time or after that or even in a non-LV PC.

The dlls that re going to be put into the data folder are those that re supplied by us, meaning used by our application [EXE].

I reiterate this because I use the Browse Folder.vi posted by you in a old thread to give the user a Windows Folder Dialog for the look of it. It uses the shell32.dll for calling two functions. But, LV wont put this dll into the data folder because this is a windows dll & there is no point for LV to doubt that whether this dll will be available in a particular PC.

Similarly, LV wont put its dll into the data folder because it cannot doubt its existence in the PC where the application is to be run. But, to avoid the worst-case scenario, anyhow LV binds it with the run-time engine to make sure it gets installed in the PC where the EXE is installed.

Am I right ?! Or, correct me please...

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 11 of 29
(1,943 Views)
Partha,
I am building applications in LV6.02 and 7.1.  Some use lvdaq.dll and others use lvdaq.dll and lvanlys.daq.  In all cases there is a data sub-folder with the dlls in them.  I have run into cases where the daq files were not installed (incorrect choices during installation I suppose) and I had to create the directory and copy the lvdaq.dll file manually to get a VI to work.
Jim 

Message Edited by lmtis on 09-25-2007 09:17 AM

Jim

LV 2020
0 Kudos
Message 12 of 29
(1,938 Views)
Partha, with 7.1 (unlike 7.0) you need to check Analysis vis support in the Advanced Installer Settings in order to include lvanlys.dll into the installer. This dll does not appear in the support and installer file lists, so it's not copied to the support file (data) directory.
By comparison, with 7.0 there is no such option, the dll appears in the support-installer file list and is copied to the support file directory.
I'm not sure this is your problem, but take a look...

Message Edited by pincpanter on 09-25-2007 04:33 PM

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 13 of 29
(1,929 Views)

The RTE folders are in National Instruments\Shared\LabVIEW Run-Time.

As you said, it looks like in 7.1 lvanlys.dll should already be in the RTE folder and the application should take it from there.
If it's not like that on your computer, that would seem to be the likely reason why you're getting this error.


___________________
Try to take over the world!
0 Kudos
Message 14 of 29
(1,924 Views)

tst, I checked all the locations, but the problem has not get solved yet.

One more thing I m unable to understand is ho come LV RTE 7.1.1 is installed in my PC & also the corresponding folder doesnt exist in its location.

Please see the attached pics.

I m also following everybody's advice, but still nothing seems to work out in my favour.

Will the devie drivers of LV released Nov 2006 install 7.1.1 RTE ? Anybody please explain to me.

I m totally clueless. Smiley Sad

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 15 of 29
(1,914 Views)


@pincpanter wrote:
Partha, with 7.1 (unlike 7.0) you need to check Analysis vis support in the Advanced Installer Settings in order to include lvanlys.dll into the installer. This dll does not appear in the support and installer file lists, so it's not copied to the support file (data) directory.


Paolo,

It is getting built without any fuss in my team-mate's PC just 5 min before, after I posted my previous reply.

Now the in-house production testing is going on & ll go all thro' the night. Smiley Wink

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 16 of 29
(1,903 Views)
Partha, LV 7.1.1 is a patch to the 7.1 version, so I think it's installed in the same directory (not sure, though).
What's the File Version of your lvrt.dll?
Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 17 of 29
(1,900 Views)
I don't believe you get a separate folder for 7.1.1 run-time. I know that I have 8.2.1 on my system (never had 8.20) and the run-time folder is just called 8.2. I seem to remember that one of the device drivers installed 7.1.1 run-time. If you are building with 7.1, that could be part of the problem. I would suggest doing an uninstall of the 7.1 run-time and then re-installing the run-time from your 7.1 LabVIEW CD. On the other hand, if you are building with 7.1.1, you want to make sure that the run-time is 7.1.1. You can open MAX and expand the software listing. the actual versions of the run-time engines and LabVIEW should be listed there.
Message 18 of 29
(1,895 Views)

Paolo,

It is 7.1.1, see the pic.

How did it get installed without my knowledge & permission ? I m annoyed.

I ve not installed anything unknown to my capabilities.

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 19 of 29
(1,893 Views)

Dennis,

My MAX shows LV 7.1 RTE only. Please see the pic.

But my Control Panel Add/Remoce Programs shows LV RTE 7.1.1. Please see my earlier post.

Could this have happened due to the installation of the Device Drivers of Nov 2006 ?

If I uninstall RTE & reinstall using the old CDs of 2005 or before, will it become OK ?

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 20 of 29
(1,881 Views)