Error building Application that runs correctly

[Gsonnenf]

Dear NI engineers,

I am attempting to build an exe and it give me the following error:

>>The VI is broken. Open the VI in LabVIEW and fix the errors.

>>C:\Documents and Settings\Desktop\Desktop\IsomerXDistribution\MAIN.vi

The VI is not broken, and runs perfectly fine, the sub VI's and classes are not broken either.  

>>Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

>>Error 1003 occurred at ABAPI Open VI and Check For Broken.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller

>>Possible reason(s):

>>LabVIEW:  The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located.  Open the VI in LabVIEW using File>>Open and verify that it is runnable.

All of the VI's in the hierachy and project and executable and located. Why will it not compile?

Thank you for your quick response.

[Gsonnenf]

The code i am using is a very large (about 350 VI's and methods) complex data structure that runs exceptional well in labview.

I am posting a very small code that demonstrates the problem. Apparently passing a class by reference causes a broken VI error when compiling. It works perfectly fine when running threw labview. It would be costly to rewrite the VI's in a different format, for something labview internally supports and all other OOP language support, simply because of an erronous compiler.  

Why will this not compile, and how can i make it compile?

http://128.123.180.148/IsomerX/DemoError.zip

Serious responses only please.

-Greg Sonnenfeld

New Mexico State University

IsomerX project

Message Edited by Gsonnenf on 01-17-2007 05:12 PM

[Doug M]

Greg,

I can see one other instance of this in our database, however it does not seem related to Object Oriented code.  Please post a version of your code that reproduces this problem, the link you posted does not work...

[Gsonnenf]

Technical support helped me find a work around over the phone. Apparently the software wouldn't compile when using the tools->Build executable command.

When i created a new project, and added only my main.VI, and created an executable using the project explorer->build specifications, it would compile.

It won't compile if I use a project manager with my classes included, or i used the tools->build executable from within the VI.

Thanks for the help in getting the executable built,

-Greg Sonnenfeld

IsomerX project

New Mexico State University

http://www.isomerx.net

P.S. we'll be releasing a free beta edition of the IsomerX project to the scientific community mid feburary! Check it out!

[Qia.sky]

I got the same error , But still can not find the answer

[Pie56694]

Qia.sky,

Is your program as complex as the one mentioned above?  Can you reproduce the error with a subset of the VIs from the larger application?

[Qia.sky]

Hi Pie56694

My Application have 7XX vis.

It is happening when I add .net Notify Icon into my application.

But now I don't do what, the problem is gone

I Open the Project, Build the application, failed! then I run my application in deveopment mode, work fine. then I build again. It works.

then I try this again and again, it repeat again and again.

Finially I decide to delete All the Notify Icon part and Rewrite it.

It works.

So I cannt figure out where the problem come from.

I found LabVIEW 8.5 Fix the bug, But I don't know whether it is a bug or not

[Qia.sky]

error come out again

Like this

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 1003 occurred at ABAPI Open VI and Check For Broken.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located.  Open the VI in LabVIEW using File>>Open and verify that it is runnable.

[Qia.sky]

But When I Restart LabVIEW and Not Open Main VI, Directly Build application. It works

I don't know why this happen, it seems uncertain

[Gsonnenf]

Hi,

I encountered this error more than a year ago with 8.2. I remember one problem that occurred during the build, before I found a solution, was that some of the references in my application were delinked in the build process. After build, Instead of the refence having a colored border coresponding to a specific data type, it turned the border black and gave me a broken wire, indicating it referenced an invalid data. It still had the correct variable name, but if i used the pull down menu to select a reference to another variable, then changed it back to its orginal name, it would fix the delinking. It was pretty strange.