The build was unsuccesful AB_EXE (error 8)

[Ettepet]

I have multiple issues happening "at random" during building or execution, which might be related.  If I need to split them up I will put the second part in a new topic.

Part 1:

~~~~~

I frequently get the Build Error: "The build was unsuccesful."

Possible reasons:

An error occurred while building the application. Either you do not have the correct permissions to create the application at the specified location or the application is in use.

Invoke Node in AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller <APPEND> Method Name: <b>Build:Application</b>

I get this in Labview 2013, and had less frequent messages like this in previous Labview versions since 2010 or 2011.  There used to be a bug where the build could not be completed because Labview locked the folder where it should be placed but that got solved somewhere between version 8.6 and 2010 (inclusive).

Usually again chosing "Build .EXE" fixes this, so I can get a succesful build.

Part 2:

~~~~~

I also have another problem, also happening at "random", where after succesfully building a .EXE I get a "Side-by-side configuration incorrect" error during execution.  This one is more recent and iirc it only happens since I moved to Labview 2013.  This might be unrelated.  I can temporarily solve this by visiting the last changed .VI and make a slight change to the Block Diagram.

I already did a Mass compilation, giving me some Bad .VI's, most of which are not part of my 600'ish file project.  None of these files match a recent "Nonfatal insanity" error I got on one of my .VI's.  I did some effort to find the culprit in that file with the Object Browser but couldn't match the error-code to any line there.

~~~

Getting these issues only sporadically makes it a lot harder to get to grips with them.

[Ettepet]

Forgot to mention...

The "The build was unsuccesful" also has the following "Details":

Click the link below to visit the Application Builder support page. Use the following information as a reference:

Error 8 occurred at AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi

Possible reason(s):

LabVIEW:  File permission error. You do not have the correct permissions for the file.

[tst]

I don't know about the second problem, but I regularly see the error 8 issue if I have the EXE folder open in Windows Explorer when building and then I have to close it before building. My understanding was that this has to do either with the indexing that Windows Explorer does or with the anti-virus program, but I never looked into it closely. I usually just sigh, close the window, rebuild and then run into it again.

[Ettepet]

---

@tst wrote:

I don't know about the second problem, but I regularly see the error 8 issue if I have the EXE folder open in Windows Explorer when building and then I have to close it before building. My understanding was that this has to do either with the indexing that Windows Explorer does or with the anti-virus program, but I never looked into it closely. I usually just sigh, close the window, rebuild and then run into it again.

---

The other option is that the mechanism in Labview to keep track of the last selected / used folder is somehow still acting up.  I remember having serious issues with whole windows folders being locked.  The "tracker" Labview used to keep track of the last selected / used folder erroneously locked the folder it focused on.  NI solved the issue (3 years ago?), but not necessarily in a flawless way.

Well, it isn't a big issue for me, I brought it up mainly because of the more serious second part (in the opening post) thinking they might be related (and easier to solve).  Will have to open a dedicated topic for the second part then.

[tst]

---

@Ettepet wrote:

The other option is that the mechanism in Labview to keep track of the last selected / used folder is somehow still acting up.  I remember having serious issues with whole windows folders being locked.  The "tracker" Labview used to keep track of the last selected / used folder erroneously locked the folder it focused on.  NI solved the issue (3 years ago?), but not necessarily in a flawless way.

---

That's just the current directory. Windows keeps a current directory for every process, which it locks. Certain things set a directory to be the current one (such as the browse dialog), but I don't remember the app builder doing it often. For me, the error 8 usually comes from having the folder open in Explorer (usually because I built a version recently and went there to take it). I'm assuming that the solution you're referring to is simply setting another folder to be the current one at the end of the build.

[Ettepet]

---

@tst wrote:

---

@Ettepet wrote:

The other option is that the mechanism in Labview to keep track of the last selected / used folder is somehow still acting up.  I remember having serious issues with whole windows folders being locked.  The "tracker" Labview used to keep track of the last selected / used folder erroneously locked the folder it focused on.  NI solved the issue (3 years ago?), but not necessarily in a flawless way.

---

That's just the current directory. Windows keeps a current directory for every process, which it locks. Certain things set a directory to be the current one (such as the browse dialog), but I don't remember the app builder doing it often. For me, the error 8 usually comes from having the folder open in Explorer (usually because I built a version recently and went there to take it). I'm assuming that the solution you're referring to is simply setting another folder to be the current one at the end of the build.

---

No, I'm the type that has 5 (or more) windows permanently opened.  So in my case one of the windows is permanently looking at the Build folder.