EXE runs only on machines with LV installed

[Wafer_Mapper]

I updated a program that made the following changes:

Added a set up panel VI to consolidate data input information,starting quadrant control and added a user input for default file location.  This VI opens a new front panel and closes when completed.  The EXE version of this works only on machines that has the full LV installed.

The EXE of the old version distributed fine as an EXE with the app builder.  Now the new version does not run on the LVRT machines.

I'm sure I'm missing some check box in some set up panel like "re-entrant execution" or something like that.  Any clues will be greatly appreciated.

Thanks

DWH

[ben64]

DWH, have you tried with a recent run-time engine version? You can download the latest version from http://joule.ni.com/nidu/cds/view/p/id/1101/lang/en

Ben

[Wafer_Mapper]

Hi Ben,

I have not considered that since I haven't changed LV versions.  I'm using LV 8.5 and use the LV 8.5 RT engine.  That run-time engine still works fine on the old EXE's.  Is there an update for the LVRT 8.5?

Thanks,

DWH

[ben64]

DWH, My first post is a link to LabVIEW 8.6 run-time engine and this should be used only if you modified you vi with LV 8.6. If your vi update was made with a more recent version of LabVIEW than the original vi you should upgrade the run-time engine to match you LabVIEW version.

Ben

[ben64]

Check this link, there is a  LabVIEW85RuntimeEngineFull.exe version, maybe this version will work.

http://joule.ni.com/nidu/cds/view/p/id/861/lang/en

Ben

[Wafer_Mapper]

Thanks Ben, I'm downloading it now and will try it.  I'll post the results later

DWH

[Dennis_Knutson]

If the previous exe worked with the run-time that is loaded, then it is not an issue with the run-time engine.

How are you opening the new front panel? Are you calling the VI dynamically? If you are, did you manually include the VI in the build? If you are specifying the path, are you using the Current VI's Path function?

[Wafer_Mapper]

Hi Ben

Thanks for your replies.  I installed the LVRT but it still didn't work. 

[Wafer_Mapper]

Hi Dennis,

I'm not sure what is considered calling the VI dynamically.  I have it open when the VI is called and it closes when it is completed.  The VI does show up in the "dependancies" section when I'm building the app so I left all other items at their default settings.  In the source files of the app builder, I'v set the main file as the start up window, then used both the default settings and tried to have the files included as part of the EXE file.  I have seen a message box flash on the screen and was able to capture it on a slow running PC. It is eraching for NIAALpro.lvlib and it is found in an instr.lib.  What I think I need to do is have the EXE not call any external files.  Any hints on how to do that?

Thanks

DWH

[Dennis_Knutson · Accepted solution]

That's not in the instr.lib. It's an analysis lvlib in vi.lib. Did you create an installer for the exe or did you just copy the exe over? You should really always use an installer. I suspect one of the support files is missing - lvanlys.dll that is supposed to be in the data folder under the app.