Executable build error

[Rashid-Malik]

I am getting the following error while trying to build an executable;

Error 1 occurred at AB_Application.lvclass:Create_INI_File.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_EXE.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_EXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller

I am using LabVIEW 2010 SP1 f4

I observed the same problem using LabVEW 2012

but the executable did compile on a colleague'e system which had LabVIWE 2010 (the original version, unpatched).

Any solution, ideas?

[dstrandb]

Hi C_.DOT,

Have you tried disconnecting the type defs? You can do this by navigating to the Additional Exclusions category in the build and checking the option to Disconnect Type Definitions. I've seen a similar error resolved by checking this box. 

If that doesn't help, have you tried recreating an identical build in LabVIEW 2010 SP1 f4 or LabVIEW 2012? It could be that bringing the build into different versions has corrupted it somehow, so recreating it could help. 

[ChristianH]

Hi,

I have the same problem building a RT Application on LabVIEW 12.0.1f3

Error 1 occurred at AB_RTEXE.lvclass:Create_INI_File.vi -> AB_Application.lvclass:Copy_Files.vi -> AB_Build.lvclass:Build.vi -> AB_Application.lvclass:Build.vi -> AB_RTEXE.lvclass:Build.vi -> AB_Engine_Build.vi -> AB_Build_Invoke.vi -> AB_Build_Invoke.vi.ProxyCaller

Disconnecting the type defs doesn´t help.

Christian H.

[dstrandb]

Hi ChristianH,

Have you tried enabling debugging in your build? Take a look at this forum post, which talks about resolving that error.

[ChristianH]

Thanks,

i have not found that posting. I tried several things, but not enabling debugging. (At least i think so).

In the end i got it running, but in a different way.

The NI Support proposed to create a new project file, which was quite a bit of work since the project contains cRIO, fifos , memory blocks and so on.

But with the new project file it does not work also.

Out of desperation i started a build process again with the original project file which surprisingly completed successfully.

If that happens again i will try the debugging solution, since it is a quicker way than a new project file.

Christian H.