How to find & repair the missing Subvis in EXE ?

[parthabe]

I m literally breaking my head due to the above-stated problem.

When I try to build the EXE & run it, the message in the attached png pops-up & thats the end of it.

This problem started when I installed both the 8.2 & 8.5 evaluations in my PC before a month or so...

I didnt care much about the problem because I thought it might ve been due to the two evaluation installations.

But today when my evaluation expired & I built the EXE using my LV 7.1 PDS & ran it, immediately the same thing happened as before. Now, it is quite annoying me much. I repaired, reinstalled LV 7.1; still of no use. I again uninstalled every NI stuff using the msiblast.exe & reinstalled LV 7.1 alone in my PC. Then also, this problem erupted again.

Please see to the picture & suggest me some solutions regarding this...

Using LV 7.1, WinXP, SP2.

[parthabe]

Sorry to add more seperately here...

I did open the missing VIs directly from the ...\VI.llb\... folder itself, & everything works fine. I mean the VIs themselves open without any corruption happened & also function normally when run there.

I dont know ways to fix this problem.

Anybody please shed some light on me...

[tst]

These all seem to be analysis VIs and my guess is that for some reason lvanlys.dll which is needed for them to run is not included in your build. When you build the application, this file should be put in a support diectory which is called "data" by default and is found in the application folder. Try seeing if you have that DLL there and whether the application works when you put the DLL in there. If it does work, the next step would be to find why LV doesn't put it into that directory.

[parthabe]

All these days LV doesnt put them in the "data" folder except our 2 other own dlls built in VC++ for our HW, because I think LV will take them from the run-time engine.

Moreover, in my PC, where LV 7.1 is installed, the VIs that use this dll work fine, which means that LV takes the dll from the original path.

So, what is the problem for the EXE to take the dll from the same location as of the VI ?

I ve attached the screenshot of the non-corrupted lvanlys.dll to cross-check with someone about the size of it.

Can you please do me the favour ?

[parthabe]

If I try to include the lvanlys.dll in the build process, I m getting the attached error.

[tst]

I guess you'll need someone from NI to help explain that build error, but just as a guess - are the read\write permissions OK? Do both locations exist?

Also, did you try manually copying the DLL into the data directory?

[parthabe]

It has been a repair/reinstallation job for the umpteen time today. So, in my guess, it would ve set/reset the necessary file permissions to default. I had already tried the time-tested method of copying/pasting manually the lvanlys.dll into the "data" folder. After doing it also, I got the same error.

Normally, LV doesnt put these dlls intothe "data" folder, unlike what you told earlier [maybe in LV 7.0, but not in LV 7.1]. I m quite sure about that because the run-time engine takes care of all the necessary LV dlls required by the EXE [whether stand-alone or installed on a non-LV installed PC]. IMO, that is the job of the run-time engine, after all...

So, tomorrow as a first thing, I d contact NI to fix up this.

But any help from you is still much appreciated.

[tst]

---

@parthabe wrote:

Normally, LV doesnt put these dlls intothe "data" folder, unlike what you told earlier [maybe in LV 7.0, but not in LV 7.1].

---

I guess you're right about that. Looking in the RTE folders on my PC, the DLL is there in 7.1, 8 and 8.2, but not in 7.0.

In that case, one other thing you can try is placing the DLL in the same folder as the EXE itself, but I'm not sure whether that would help either.

[lmtis]

When I build my exe, which uses lvdaq.dll, it does put it in the data folder.  You are adding the dll as a support file before starting the build aren't you?

Jim

[parthabe]

tst,

Please tell me the location of the RTE folder, I cant find.

Jim,

What version of LV re you using ? See tst's reply above.