Building stand alone application Error 21

[ceties]

Hi,
I compiled my application (LabView 7.1) to exe and installed RunTime 7.1 on test target machine. I obtained error (graph.jpg). It was because of incorrect version of cw3dgrph.ocx - higher than in LV 7.1. When I installed RunTime 8.0.1 on test target machine it solved the the problem. Error maybe occured because I have in my Labview some OpenG software installed, but I'm not sure it was the reason. (I'm using LabView 7.1; 8.0 never installed)

Everything looked good until I installed my software on final target machine. You can see the errors (error 21) on pictures. I read some threads obout error 21, but nothing helped. Strange is that on the first pc everything was ok.
On the final target computer is installed Runtime engine 6.1 as well because of other application. And some DAQ. Is this the problem? (older version of Runtime?)

Where could be the problem?
I attached my application. It is optimalized for 1600x1200 resolution, but don't care about it.
Why it bugs with analyze vi's?

[ceties]

application and last error

[JLS]

Hello,

I think you will want to have your client machines only have a single version of the runtime engine installed corresponding to the version you build your exe in.  Then, if you need a newer version of the cw3dgrph.ocx, you should simply install and register that on the client machines.  You should be able to automate this as well.  Here's what you can do so that the client doesn't have to manually install anything:

1. instead of just building an exe, build an installer for your exe (this will allow you to install the appropriate runtime engine as well)

2. you will also have the option in the installer settings to run an executable before completing - this executable could be a simple LabVIEW exe which uses the command exec vi to register the necessary version of the ocx file, which you would include as well.  You could use relative paths (the current VI's path vi for example) to get the path to the ocx you included, and then register it with the appropriate command (the command form is: regsvr32 <path & filename of ocx> ) using the command exec VI.

I hope this helps!

Best Regards,

JLS

Message Edited by JLS on 04-25-2006 02:21 PM

[ceties]

Hello JLS,
Thank you very much but it solves only half of my problem. The main part still remains. When using my program on system with RunTime 6.1 for older program (and 7.1 for my program) it still bugs me (error 2-4). When using on PC with only runtime 7.1 installed everything is OK (but the older program doesn´t work of course).
Does anybody know why it happens? 😞

[JLS]

Hello,

I understand, I have seen problems having more than one version of the runtime engine on client machines.  Is there anyway you can upgrade your 6.1 application to 7.1?  You should be able to open your 6.1 source code (with the correct version of NI-DAQ installed) and then build the exe in 7.1.  This should eliminate the need for two runtime engines altogether, and would make for cleaner client machines.

Best Regards,

JLS

[ceties]

Problem is that the 6.1 application was written by someone other and only exe is available. 😞
No Way

[JLS]

Hello,

I see.  So we'll have to keep exploring this!  First, is it possible that the 7.1 runtime engine was installed before the 6.1 runtime engine on the machine of interest?  If so, let's try uninstalling the runtime engines, and then installing 6.1 and 7.1 in that order.  It would also be interesting to try running a very simple 7.1 exe on that machine, to see if it has the same problem.  Perhaps we can link this to the use of lvanalysis functions and the corresponding dll.  With that in mind, I have attached a simple 7.1 built exe which simply adds two numbers.  Try executing this on the machine which gives you the error with your 7.1 built exe.  Also, please attach a screenshot of the newest error message you receive when running the 7.1 built exe (error 2-4 I believe you noted), as well as any error you receive with the simple add.exe attached.  Hopefully any difference in the error message or behavior of your 7.1 exe and the attached add.exe will give us clues to what's going on!

Thank you,

Best Regards,

JLS

PS - I have attached the file with extension .txt - just right click on it below and choose "Save Target As..." to save it to your machine, and then right click to rename it on your machine to have .exe as the extension (.exe files cannot be attached in this forum).

Message Edited by JLS on 04-28-2006 05:39 PM

[ceties]

Hello, I'll try everything you have written but it will take some time (week) then I'll write.
Thank you very much!

[JLS]

Great, and I look forward to your next post!

Best Regards,

JLS