Error 8 while building App

[Quan2um]

Hello,
    I am having an issue with an app I am trying to build.  I get the folowing error message during the build:

Error 8 occurred at Invoke Node in ABAPI Dist read linkages.vi->ABAPI Dist Cmp Settings to Disk Hier.vi->ABAPI Get Settings From File.vi->EBEP_Invoke_Build_Engine.vi->EBUIP_Build_Invoke.vi->EBUIP_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  File permission error.

---

NI-488:  DMA hardware error detected.

Method Name: Linker:Read Info From File

C:\Documents and Settings\. . . . \Notes Popup.vi

The odd thing is the VI filename that is listed is one that is not used or exists anymore. 


I am using LV 8.0 on Win XP

Thnaks

[Ecleamus]

Hi Quan2um,

This appears to be a popular error message on the DF.  I'm not sure what you meant by the "VI filename that is listed is one that is not used or exists anymore" Does this mean you had this VI in your project at some point?  At any rate, take a look at this Discussion. Let me know if it helps.

Ecleamus Ricks, Jr.
National Instruments
Applications Engineer

[Quan2um]

Ecleamus R,
    As far as the "VI filename" goes, yes, it was one that I had in my project at one point.  I updated the VI and changed the name to reflect changes I made.  I also removed it from the project. 

    I had previously read the thread that you referenced.  I could not find any .aliases files on my machine.  Are they stored anywhere in particular? 

Tom

[Justin D]

Tom,

The .aliases file is usually stored in the same directory as your .lvproj file.  If you are missing this file for some reason here is something you can do to recreate it.

1) Go into Labview 8 and create a new Project.

2) Save the project on your desktop (you can give it any name)

3) A .aliases file should have been created on your desktop when you saved your project in the previous step.  Copy this file into the same directory as your main project (the same directory as the .lvproj file).

If you follow these steps you will now have a .aliases file and this will most likely fix your problem.

I hope this helps,

Justin D.

Applications Engineer

National Instruments