Labview 2013 executable works only on develoment machine?

[SolPS]

Hi all

I created an executable so as to distribute my test software but it only runs on the development machine. I have successfully distributed my executables before with labview 2012 on target machines by simply creating the .exe in project explorer and then installing the nessary labview drivers and run time engine without problems. Now I created a new test programme with Labview 2013 and I can't get my new .exe test software application to run on the target machine. Has anyone seen this type of problem before?  Any assistance will be appreciated.

Thanks

[GerdW]

Hi SoIPS,

did you create an installer with your EXE? Or did you just copy the EXE and installed anything else on your own?

[AnkitG]

---

@SolPS wrote:

Hi all

I created an executable so as to distribute my test software but it only runs on the development machine. I have successfully distributed my executables before with labview 2012 on target machines by simply creating the .exe in project explorer and then installing the nessary labview drivers and run time engine without problems. Now I created a new test programme with Labview 2013 and I can't get my new .exe test software application to run on the target machine. Has anyone seen this type of problem before?  Any assistance will be appreciated.

Thanks

---

Are you using the compatible run time engine on the target machine.?

http://digital.ni.com/public.nsf/allkb/800E68EBF895BD96862570770051FF36

[crossrulz]

Sounds like you need to install the LabVIEW 2013 Run-Time Engine.  The 2012 RTE cannot run 2013 executables.  As has been said, I recommend creating an installer that includes the RTE and any other drivers you need.

[SolPS]

Crossrulz,

I did exactly that.  I developed the test software with labview 2013 and created an installer that included the 2013 RTE. I still couldn't get it to run on the target machine.

[GerdW]

Hi SoIPS,

what kind of errors do you get? Atleast the executable should not claim for missing RTE...

[Hooovahh]

In addition to the run-time engine you are likely missing some other installers.  Lets say you used RS-232 code in your EXE well now you need to install VISA run-time on the new machine.  Did you use DAQ?  Now you need DAQmx.  Did you use NI-Scope? NI-DMM? NI-Power? NI-Switch?  You'll need to install those as well.

In 2013 the process of making an installer can detect what installers you need.  In previous versions you just have to know which you used and select them in the Additional Installers section.

[SolPS]

GerdW,

The VI is a state machine. It doesn't show any error message when I try to run the executable, it simply doesn't go past the initialization state and it freezes. The stop button on the VI becomes unresponsive. I'm only able to stop it by clicking the emergency abort icon but I can run the same exe on my development machine without any issues.

[GerdW]

Hi SoIPS,

so what does your program try to initialize? Did you include any needed driver (like VISA) in your installer?

[SolPS]

Hooovahh,

I also thought I was missing some installers and deceided to create both the installers and  exe application in project explorer. I got an error message about some installers not being available on my computer when I tried to build the installer. This error message went away once I inserted my labview 2013 device driver cd in my computer.  Afterwards, I was able to build the installer without any error message. Now when tried deploying that application, it still didn't run.

Thanks