LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 8 Compilation Error. File permission error or DMA hardware error detected

I just upgraded my Labview code to Labview 8.5 from LV8.2.1
Then I tried to compile my code to get an .exe file
I keep getting the following error,
 
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 8 occurred at Write to Text File in AB_Engine_Update_INI_Header.vi->AB_Application.lvclass:Create_INI_File.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
Possible reason(s):
LabVIEW:  File permission error. You do not have the correct permissions for the file.
=========================
NI-488:  DMA hardware error detected.
C:\UserData\LabView\IFX Interop Test exe\GMXiTest.ini
 
I never have this problem if I compile using LV8.2.1.
Please help! Thanks.
 
0 Kudos
Message 1 of 4
(3,604 Views)

hi there

just to be sure: has 8.5 been installed under an other account than yours? make sure you have the windows access rigths to the LabVIEW - folder.

Best regards
chris

CL(A)Dly bending G-Force with LabVIEW

famous last words: "oh my god, it is full of stars!"
0 Kudos
Message 2 of 4
(3,597 Views)

Hi,

Yes I have administrator rights on the PC. It was installed with full R/W permission.

I saw in the forum that others are having the same problem and tried this work-around mentioned but it did not work.

http://forums.ni.com/ni/board/message?board.id=170&message.id=172537&query.id=115461#M172537

 

Any ideas?

Message Edited by nantha on 09-13-2007 06:57 AM

Message Edited by nantha on 09-13-2007 06:58 AM

0 Kudos
Message 3 of 4
(3,595 Views)
Hello Nantha,

here you can finde more info about the error 8 code.
Please check the file permission of the file.

http://digital.ni.com/public.nsf/websearch/F5D5F6798A9367CC86256F6C007A968D?OpenDocument

Could you post a small vi so that i could try to reproduce the error.
It would be greate if you could descripe the approach.

Kind regards,

Elmar
0 Kudos
Message 4 of 4
(3,570 Views)