Invoke Node in AB_Source_VI.lvclass Error

[apalrd]

I seem to get this funny build error when I do a full build but not when I hit the Deploy button in Robot Main.vi

Here is the error I get:

An error occurred while saving the following file:

C:\Users\YOUR NAME HERE\Documents\LabVIEW Data\Buzz15\Robot Main.vi

Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_RTEXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>

I have no idea where this error is coming from or what it means, searches on the NI site have turned up nothing.

I only use the Invoke Node during Autonomous, and have removed that code to see if it is the cause. It is not.

[Greg McKaskle]

The app builder error messages just seem to get worse and worse.

Interpreting the gibberish, my guess is that it has to do with file permissions for where it is copying files to. I suppose it could also be an issue with the source of the copy not existing.

If you've made edits to the build distribution, look them over and see if a path is no longer correct or if the destination folder is locked. Also try running as admin and see if that corrects it.

Greg McKaskle

[apalrd]

LabVIEW created the build folder (Documents\LabVIEW Data\Buzz15\Builds\c\ni-rt\startup\), and a quick check of permissions shows it as Read Only and denys me access to change that.
Deleting the Builds folder and making LabVIEW re-create it dosen't work either.
No changes to default build.
I am running on Vista on an administrator account. None of the other Killer Bees computers run Vista or have this problem. I am the main programmer, so I need to get my laptop to work.
Running LabVIEW as administrator does not solve the problem.
When I run Explorer as Admin, I still do not have authority to change permissions on the build folder.

Edit: All of the folders in LabVIEW Data\Buzz15 are listed as Read Only, but I can still put files in there for some reason.

[Greg McKaskle]

So now we know what the problem is. If we only new the solution. I'm not that confident in making Windows do what I want, but I'd look at making the folders be read/write, or perhaps moving the build location to a new location.

If anyone else knows more about the permissions, please speak up.

Greg McKaskle

[apalrd]

I found that all of my folders in Buzz15 (drivetrain, auton, etc) all show the read-only flag, yet I can still write to them. Using advice from someone else on the NI forum, I tried enabling debugging in the build properties and all was well. It rebuilt in the same directory and was happy. Now to figure out why it won't build when not debugging.