NI Variable Engine stops when exe installer is run

[DavidU]

Hello,

I have a built executable that uses shared variables. The exe and the NI Variable Engine are both running fine.

I have also built an installer for it that includes the LabVIEW 2017 run time engine and the NI Variable Engine. 

I regularly update the executable, and rebuild the installer. When I then run the installer it installs the executable no problem. But it also stops the NI Variable Engine service and I have to go into windows services and restart it. Is there any way to avoid this?

The NI Variable Engine works fine when running, and shared variables are available. It is pain to have to restart the Variable Engine everytime I run the installer.

LabVIEW 2017

Windows 10

Thanks

David

[RHadley]

Hi David,

If the installer you have created contains the NI Variable Engine, then whenever you run the installer, it will reinstall the NI Variable Engine, and this will be what stops the Variable Engine processes from running.

In the Additional Installers tab of the Installer Build Specification, you can deselect "Automatically select recommend installers", which would allow you to create a version of the installer to use on computers which already have the NI Variable Engine.

Kind regards,

Richard Hadley

Technical Support Engineer

NI UK

[DavidU]

Hi Richard,

Thanks for the reply.

I will try creating an installer without the variable engine when I have the opportunity.

Why does it reinstall the variable engine? In the installer dialog it doesn't say that it will, it just says it will update the exe. It certainly doesn't reinstall the runtime engine, which is also bundled in the installer.

Regards

David