Error 8 when building a program

[TCWITT@APTAR]

Here is the error. For the sake of confidentiality, I had to block out the actual program name. You can basically substitute "My Program" for any of the white boxes. 

As a note, the actual project files are stored on the desktop in a separate folder

[aputman]

Try creating a new build specification from scratch and use as many default settings as possible.  

[TCWITT@APTAR]

Thank you for the suggestion. I tried that as well, but ended up with the same error. Seems like nothing is going to fix this issue.

[aputman]

Yeah, I'm fresh out of ideas.  There are a lot of posts on the forums about this error but it seems that you've tried most of the solutions offered.  

Actually one last thing I can think.  What happens if you create a simple VI that does nothing but loop, wait for 50ms, and display a random number?  Are you able to successfully build an EXE with this one VI as the only file?  

Is this a new issue?  Have you successfully built an EXE in the past for this project but something changed and you're not able to do so any longer?  Have you built other applications in the past on the same laptop?  

If you are able to share a portion of the offending code, I can try to compile it on my machine.  If it compiles here, that tells me that you indeed have a security issue.

Those pesky I.T. guys can really be a nuisance when you can't even do your job because of their policies.  

[TCWITT@APTAR]

Thanks for all the help. I attempted to build a VERY simple program (basically 2 input boxes for numbers, an add function, and an output), and when I went to build that program it also failed with the same error. So, I'm not sure what to do at this point. I'm guessing it has something to do with the permissions of this account on this laptop.

[TCWITT@APTAR]

I made another program that was a counter, but still got the same error. Seems like it only happens with that lvapp.lib file for some reason. When it takes it out of the NI folder as lvapp.lib and puts it in the temp file as lvapp.lib.tmp it kicks out that error.

[aputman · Accepted solution]

---

TCWITT@APTAR wrote:

I made another program that was a counter, but still got the same error. Seems like it only happens with that lvapp.lib file for some reason. When it takes it out of the NI folder as lvapp.lib and puts it in the temp file as lvapp.lib.tmp it kicks out that error.

---

I don't think it is trying the take the file out of the NI folder.  It should be trying to copy all of the dependencies into a common directory so that they can be compiled into the binary.  However, copy commands do not need full permission, they only need read.  If the file didn't have read permissions, Labview wouldn't work.  So I don't think the source directory is the problem but I could be wrong.  I am not a file systems expert by any stretch. 

So the only option left, in my mind, is the temp directory.  But if the temp directory is set to read only by your IT guys, that seems ludicrous because many applications use the temp directory for storing temporary files, hence the name TEMP. 

You can try changing the temp directory within the Labview options box (Paths subheading).  Pick a location in the user directory (maybe a TEMP folder in My Documents).  Make sure you have full permissions on the folder.  You will have to restart Labview for that change to take effect.  If it doesn't work, it's probably best to change that back to default or wherever it was set previously.  No sense clogging up your Documents directory with unnecessary files. 

Also something you can try is to right click your Labview shortcut and click "Run as Administrator" and maybe the privileges will be elevated enough to get a successful build.  I meant to tell you this earlier but forgot to list it out. 

[TCWITT@APTAR]

One of those two things did it! 

I added a folder on the desktop and named it "LabView TEMP", then went options>paths and changed the temp file to that folder. I also opened LabView by right clicking and selecting "Run as Administrator". One of those two things (or both) allowed the build to finish. Thank you so much for your input!

[aputman]

Awesome.  Now try to figure out which one by only using one suggestion and not the other.  If the temp directory fixes it, tell you IT guys to lighten up a bit.   

If Run as Administrator fixes it, tell you IT guys to lighten up a bit.  

It either case, your IT guys are the cause of the problem.