Permission error when building exe

[itronChiraldude]

Does anyone else have the issue where the executable build fails at the very end due to a file permission error in the destination directory?  This happens randomly.  For some reason LabVIEW tries to write the files in the build directory and Windows blocks it.  This is no big deal for small projects but most of my projects are quite large and the build takes 5-7 min.  

Feature request would be to offer a retry dialog during the build to give an opportunity to remedy the permission issue or at least show the problem file and offer to save to a different path.

[GerdW]

Hi itron,

I could guess two options:

• your antivirus tool interferes with the App builder
• you have the FileExplorer open and showing the build directory: don't do that!

[Bob_Schor]

Tell us a little about your environment.  What version of LabVIEW are you using (include bit-ness)?  Did you do a (I forget the correct terminology here ...) a "Trial Build"?  Was it successful?  Do you "include" items not in your Project in the Build Specification?  Do you use "Pre-Build" or "Post-Build" actions?

Bob Schor

[Andrey_Dmitriev]

---

@itronChiraldude wrote:

Does anyone else have the issue where the executable build fails at the very end due to a file permission error in the destination directory?

---

Yes, same for me (and not only in LabVIEW) and the corporate antivirus is the answer for my case. The probability is bigger with larger projects. How to check - perform build on the "clear" PC with Windows "out of the box" or under Virtual Machine. For me it works, but slower that on native environment.

[BertMcMahan]

Open the Start menu and type "Virus and thread protection" then open "Protection history"- see if there are clues there.

My computer has a REAL affinity for blocking "Protected folder access" which has been a massive pain in the butt. I have to tell it "No, it's OK" all the dang time.

[Andrey_Dmitriev]

---

@BertMcMahan wrote:

Open the Start menu and type "Virus and thread protection" then...

---

The only problem is that on corporate environment any or most of settings for antivirus are locked by administrator (but it depends).