Build error when using custom error codes

[nglasser]

When I try to build my application using custom error codes I receive the following error:

Error 1 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:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488:  Command requires GPIB Controller to be Controller-In-Charge.

C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\errors\BPMS-errors.txt

This only occurs the first time I attempt to build my application. If I build again immediately after receiving the error, everything works fine. My custom error codes were created using the provided editor, and I have included the file in my project. I have also checked the "Copy error codes" box in the advanced build specification settings.

[Donovan_B]

Hi,

Do you get this error only when including custom error codes or does it occur when you build other applications as well?  I am a little confused why the build would be successful the second time when it is not on the first attempt.  Are you using GPIB calls or only LabVIEW?  This will help us narrow down where this error is occurring.  Also, when the application does build, does it run as expected or do you get other errors?

[nglasser]

Hi Donovan,

I do only get this error when including custom error codes. I have never had the problem with any other application I have built, but this is the only one utilizing custom error codes. If I uncheck the box to include error codes in the application properties, the error does not occur. I am only using LabVIEW calls (this is a machine vision application utilizing the Vision Development Module). After the application builds, it behaves completely as expected. I have tested it fully and found no errors at all.

[Donovan_B]

Have you tried building another application that includes custom error codes or does it only happen with this particular application?  Could you post a small project that exhibits this behavior?  I have not been able to recreate this issue, but I will keep looking into it.

[nglasser]

Hi Donovan,

The attached project is giving me the error previously discussed. Thanks for your help.

[Donovan_B]

I'll take a look at it and see what I can figure out.

[mprimrose]

Donovan,

I am getting the same error.  Have you found anything or a work arround?

Thanks,

Mark

[Devin_K]

mprimrose and nglasser,

I believe that the problem is the name of the error code file.  All error code files must follow the format "filename-errors.txt".  This format is case sensitive, so filenames cannot contain capitals.  Try changing your error code filename to "test-errors.txt" instead of "Test-errors.txt".

[mprimrose]

Devin,

Thanks for the response.  Unfortunately my custom error filename is already all lowercase.  It is named: kf-errors.txt

Mark

[Devin_K]

Would you be able to post your file?