09-09-2010 08:56 AM
In LabVIEW 2010, I am getting an Error 6 about 50% of the time when I Build my VI into an Application.
I may fail several time in a row. It may fail every other time.
VI runs fine in LabVIEW debugger.
Why does the Build work fine sometimes and Fail other times?
How do I fix this?
Error message:
Error 6 occurred at Delete in AB_Engine_Delete_Internal_Files.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
=========================
NI-488: I/O operation aborted.
C:\Users\Don\Documents\OnSpex\builds\HTT\My Application\Application.exe
09-09-2010 10:24 AM
Do you by change have Google Desktop running. Google Desktop can lock some of the files where we are trying to write to causing this error.
Try disabling Google Desktop and see if this error goes away.
Also, make sure you don't have any other programs that could be scanning and locking certain files.
09-09-2010 10:53 AM
I am not running Google Desktop. It is not installed.
Nothing that I have should be locking files that LabVIEW is working with.
09-09-2010 03:41 PM
@Jon S. wrote:
Do you by change have Google Desktop running. Google Desktop can lock some of the files where we are trying to write to causing this error.
Try disabling Google Desktop and see if this error goes away.
Also, make sure you don't have any other programs that could be scanning and locking certain files.
I have no Google software installed on this machine.
There should be no other programs working with files that LabVIEW is trying to access.
CPU is fast (i-5, four cores) and access should be good.
What else could cause this problem?
09-10-2010 03:48 PM
The error mentioned is thrown when LabVIEW is trying to delete the internal files that application builder creates during the build process. If for some reason LabVIEW doesn't have access or permission to delete the file then this error could be returned. Can you try to reproduce this on another machine, preferably one that is relatively clean? If not is it possible to post the code so we can try it out here?
09-10-2010 03:55 PM
The machine that this is happening on is very clean. About 1 week old. New Windows 7 Ultimate. Core i5-750. lots of RAM. Very little software installed. Used for LabVIEW dev.
09-10-2010 03:55 PM
Code is developed under NDA and can not be shared.