Multifunction DAQ

cancel
Showing results for 
Search instead for 
Did you mean: 

building exe files

Solved!
Go to solution
I am trying to create an application to be installed on any PC (With of without labview). When building the application i get the following errors: Please help... Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.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:\Program Files\National Instruments\Shared\LabVIEW Run-Time\8.6\errors\English\SPT-errors.txt
0 Kudos
Message 1 of 10
(4,740 Views)
Solution
Accepted by topic author mo786

Hi mo786,

 

Good Morning and I hope your well today. Thanks for the post.

 

Firstly, this seems more of a LabVIEW forum question then a DAQ question - but I am happy to support you here all the same.

 

This error message has many causes so I will try to summarize my suggestions below,

 

1.  Check File Permissions:

a. Make sure you logged in as Admin

b. Try saving the build files to your user data (Desktop) rather than say Program Files - which could be READ ONLY. 

 

2. VIs need to be in the Same version of LabVIEW:

a. This tends to happen more when users have upgraded from a previous version of LabVIEW. 

b. To try to retify this I would suggest saving all VIs manually, including any your dynamically call.  (This is known as Mass Compiling),

c. You could try repairing LabVIEW by going to control panel>>Add/Remove Programs>>NI>>LabVIEW 8.6>>Repair.

 

3.  Unselect "Copy Error code files"

a. This ought to remove the error as the path is to do with the errors.txt file.

b. Follow the knowledgebase article below on how to remove this option, 

 

Error 8 With Application Builder When I Create an Executable in LabVIEW 8.5/8.5.1

http://digital.ni.com/public.nsf/allkb/BAF0ACFA708F1D19862574C8005248E7?OpenDocument

 

4. Try building a new project, and saving it in a different directory. 

5. Similarly try building a simple project with the simple error handler in it - does it still error? 

 

Please try these suggestions and let me know how you get on,

Hope this helps. 

Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help! 😉
Message 2 of 10
(4,726 Views)

Hi Hillman,

I have a similar situation here so I thought I would just reply to this thread.

I recently upgraded my LabVIEW 4.1 to 5.1.1 in Windows 2000 machine.

My VI stores data to a file every 40 pulses. When I start running it, after 40 pulses, rather than saving the data, it shows below error message.

 

Error 8 occured at opening file

possible reasons

LabVIEW: File Permission Error

or

NI-488: DMA hardware error detected.

 

Also, When I colse the VI, it is asking me to save several subVI's like GPIP error report.vi, unlisten.vi etc.

(There are currently 15VIs with unsaved changes remianing to be removed from memory.)

When I do that, it says, 

 

File Permission error occured.

Can not save VI " CAMAC Test CAM.vi"

 

or sometimes it shows,

 

Can not save VI "arraymean.vi". The VI already exists and you do not have permission to replace it.

 

As you suggested, I tried to save each VI separately (mass compiling). But I still see the same error message.

Am I missing something here? could you please help me..

I am attaching the VI for your convenience.

0 Kudos
Message 3 of 10
(4,530 Views)

Your question is not even remotely similar to the original post and sorry, but I find your statement "I recently upgraded my LabVIEW 4.1 to 5.1.1 in Windows 2000 machine." hilarious.Smiley Very HappySmiley Very Happy

 

You did not post a single one of the subVI so I have no idea what you are trying to save. Are these VIs that you wrote? Are you logged on as admin or a user? Did you check the file properties of the VIs to see if they are read only?

 

And for goodness sake, get rid of all those local variables. I see at least one race condition. And you might also seriously consider a supported version of LabVIEW and windows.

Message 4 of 10
(4,520 Views)

Hi Dennis..

Thanks for the quick reply. Sorry for so lengthy message yet not so informative. My problem is partially solved. Some of the VIs were read only now I changed it and I could save them. Let me explain more clearly what I am doing.

 

 

Right now, I have LV v5.1.1(just upgraded from 4.1) running in my Windows 2000 OS.  I have LAB-PC+ DAQ card to control some motors. I also have PCI-GPIB card connected to Lecroy 8901 GPIB interface for data aquisition.

I have NI-DAQ 6.6, NI-VISA, NI-488.2 for windows 2000 installed in my system. 

 

 

The subVIs are to communicate with PCI-GPIB card and Lecroy GPIB interface. Those VIs are belongs to two main llbs which I got from NI-488.2 for windows. Now I could save them.

 

 

But, when I run the program, it could not save the data to the file but the following error pops up at the end of the cycle.

 

Error 8 occured at opening file

possible reasons

LabVIEW: File Permission Error

or

NI-488: DMA hardware error detected.

 

-My hardware is properly installed and it should not be the problem.

 

Can you please tell me what am I missing? I did try running the program logging in as Admin and the user who has admin rights but samething.

 

P.S: Even I found it helarious when I was "upgrading" it  🙂

actually I just aquired the experiment and the program from a passing out graduate student in my lab. Thank you for pointing out my cumbursome program. I need to cleanup littlebit. 

Due to budget constraints, I dont think I can upgrade my system any further :(. 

I have to adjust with what I have.

0 Kudos
Message 5 of 10
(4,506 Views)

Hi Dennis..

Should I post this problem in different thread for better resolution?

0 Kudos
Message 6 of 10
(4,497 Views)
Not necessarily. As I mentioned, you could do is attatch the missing VIs - at least the one that is causing the problem
Message 7 of 10
(4,489 Views)

I attached the all SubVIs that I  am using.

There is no problem in those VIs now.

The only problem I am facing right now is that, when I run the program, that error is popping up.

 

Thank you Dennis for your time

0 Kudos
Message 8 of 10
(4,480 Views)
You've got a frame with a couple of Write to Spreadsheet File functions. Your front panel control with the path does not seem to define a path - just a folder. That whole section of code is silly. You not only have two functions and the paths are the same, but you convert to a 2D array and that is completely unnecessary.
Message 9 of 10
(4,466 Views)

Thank you very much Dennis..

My problem is solved. You are right.. I gave different file names  as the the path and it worked fine.

Sorry for so much confusing code. Now I am working on making the code efficient and neat.

 

Thank you once again.

0 Kudos
Message 10 of 10
(4,454 Views)