09-18-2020 02:30 PM - edited 09-18-2020 03:23 PM
Hello LV Community,
I have an application that runs fine in development but breaks when I build and run from a LabVIEW .exe.
I've narrowed the issue down to a native LabVIEW call to HTTP GET (I'm using LabVIEW 2017)...
I've created a simple example to reproduce my issue. See attachment.
Any ideas what the issue is here? I have to run in LabVIEW runtime (.exe) so any ideas how can I get around it?
Solved! Go to Solution.
09-18-2020 02:56 PM
It appears that you didn't include that file in your build.
09-18-2020 03:03 PM
Thanks for response.
I'm calling that VI dynamically so I don't want to include in build...
But... just for testing I did try to rebuild with the VI included in build and I still see the same issue.
09-18-2020 03:37 PM
I've uploaded an updated project and build...
See attachment. Again,
Any ideas what the issue is here? I have to run in LabVIEW runtime (.exe) so any ideas how can I get around it?
09-18-2020 04:02 PM
@SharkoNext wrote:
I've uploaded an updated project and build...
See attachment. Again,
- Run Launch_TopLevel.vi and no issues...
- Run builds/LaunchReads.exe and you'll see an error that the sub VI HTTP GET cannot be found
Any ideas what the issue is here? I have to run in LabVIEW runtime (.exe) so any ideas how can I get around it?
I’m not where I can look at this right now. Put an indicator on the path that you are using for the dynamic call. It may be different in the exe from running in the development environment.
09-18-2020 04:07 PM
I have a popup to indicate the path in .exe and it confirms that it's correct.
09-18-2020 04:16 PM
I took it a step further to demonstrate that the issue only occurs with remote ansynch VI call to a VI that contains HTTP GET. I need to be able call this VI asynch so direct call is not an option. See attachment...
09-18-2020 05:56 PM
the executable have to find all needed VIs. Create a source distribution for GetTestInfo.vi into a separate folder (or directly into builds). Then you get all needed files into a new folder. Copy all these files into the builds folder and LaunchReads.exe works like expected. Ok, its quick and dirty 😮
09-18-2020 06:06 PM
I fogot to append the sources...
09-19-2020 12:41 PM
@Martin_Henz, could you save in LV 2017 for me?