LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Exe gets deleted

hi there!

i am trying to build an application on labview. when i build by application it generates a .exe in builds folder but when i run that exe it shows an error that the file doesn't exists and deletes that exe. and dont let me delete that build folder (unless i change its name) giving permissions error (my build folder is in primary drive).

0 Kudos
Message 1 of 4
(816 Views)

@aliana wrote:

(my build folder is in primary drive).


What does that mean?

What's the OS?

What kind of AV/security software is running on that PC?


LabVIEW Champion. It all comes together in GCentral GCentral
0 Kudos
Message 2 of 4
(806 Views)

Aliana,

 

I agree with altenbach's questions. I would suggest you to make sure your user has the privileges required to perfom read/write operations in the primary drive and location you're building to. I'd also suggest turning off any antivirus/firewall software that might be causing this behavior to happen. Finally, I encourage you to be more detailed as for the errors you're seeing. Usually a screenshot can give a lot of cokntext on what the cause of a certain issue can be.

 

Warm regards, and happy new year,

 

0 Kudos
Message 3 of 4
(750 Views)

Usually when you build an Executable, you do so from the context of a LabVIEW Project.  Usually a Project and all its LabVIEW VIs and controls are contained (along with the .lvproj file) in a single folder.  If you compress the folder and attach the .zip file, we can not only examine your VI for problems, but can also see the Build Specification and might spot the issue.

 

One good place to build an Executable is in (assuming a standard Windows 7/8/10 configuration) C:\Users\Public\Documents\Builds.  In (all?) Windows configuration, the Public Documents folder is read/write to all authenticated users, so there are no permission problems when other users want to run the program.  Another trick is to create a Shortcut to the .exe file (this works best if you've made an Icon for it) and place the Shortcut on the Public Desktop, where it (should) inherit the Read/Execute privilege for all users.

 

Bob Schor

0 Kudos
Message 4 of 4
(713 Views)