LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 21 and lvanlys on non labview machines

I posted this earlier today and it has not shown up so I am re-posting it.

I created an application using labview 7.1 under Windows XP. I create an executable using App Builder. I burn a CD with the application and all of the 7.1 runtime files. I take it to a non-labview machine and it refuses to load giving error 21 for all of the analysis routines.

lvanlys.dll is on the CD. This has come up before and the answer is always Build an Installer. I have good reasons to not want to Build an Installer. Furthermore, I have succesfully done what I am doing in Labview 6. It is only since upgrading to 7.1 that the problem occurs.

Furthermore, programs which use non-math runtime facilities such as LVSound.dll work fine. I am puzzled why the executable doesn't see lvanlys.dll. It is certainly there.

I have attached a very simple executable to demonstrate the problem. It just calls sine pattern.vi and writes the output to a graph. Take it to any windows machine which does not have labview installed and it will fail with an error 21.

Can anyone help?

Note: I am posting this without the example because it seems to be creating a problem. You can demonstrate it by simply creating a vi with sine pattern.vi or any other math routine, building it, copying the 7.1 runtime into the same folder and taking it to a non-labview machine.
0 Kudos
Message 1 of 3
(2,823 Views)
David,

The way the lvanlys dll works changed between versions 7.0 and 7.1. I won't get into the details, but in order for it to be called correctly now, the LV run-time engine must be installed. This doesn't mean that you have to bundle it into an installer when you create the executable, but you should at least download it from our website to the target machine (it's free!). A possible workaround is that you could replace the 7.1 version of the lvanlys.dll with a previous version and it may work for you, but this could cause problems later on. First of all, there may be other dlls that you need the run-time engine for. Secondly, there could be bugs in the previous version that were fixed in the 7.1 version.
0 Kudos
Message 2 of 3
(2,804 Views)
Thanks for the information. I am not happy about it but it helps to know the score.

We build educational software. A lot of educational institutions do not allow users to do installs, or they require that it be done by IT professionals requiring scheduling and long lead times.

The ability for a student to be able to carry around an application on a CD, pop it into any machine and run it with having to do an install is a major plus for us.

I will try running our application bundled with a 6.1 or 7.0 runtime and see what happens.
0 Kudos
Message 3 of 3
(2,792 Views)