Hello Larry,
This particular error message appears to come from a Windows
function called during the build process.
I believe it to mean that it simply can’t access a file because some
other process is using it. LabVIEW
should be handling its file accesses appropriately (and I don’t see much in the
way of other occurrences of this problem) so I think you could be on to
something with suspecting the GateKeeper program. I am unfamiliar with the workings of the
program but a Google page I found mentions:
“DataKeeper works in the background, monitoring file
activities and making compressed backups automatically as you make changes to
data. Since there is no need to schedule backups, you don't have to worry about
forgetting to do them.”
Automatically makes backups as data is changed? This sounds like datakeeper could be
detecting all the file IO going on and automatically coming in to backup
data. If datakeeper is in the middle of
a backup when LabVIEW is attempting to delete a file I could see this access
error occurring. Furthermore, since the
timing of all of this is unpredictable it also might explain why it only
sometimes happens.
It’s only a theory, but at least it’s a start. You might consider either disabling the
datakeeper or trying the build on other computers.
Hopefully this helps, please let me know how it goes!
Travis M
LabVIEW R&D
National Instruments
