Error 1003 Occurs When Trying to Create an Executable

Updated Oct 2, 2018

Reported In


  • LabVIEW Application Builder Module
  • LabVIEW
  • LabVIEW SoftMotion Module

Issue Details

My VI runs correctly in the LabVIEW development environment. However, when I try building an executable out of the same VI, the build terminates, and I receive the following error message:
Error 1003 occurred at C:\....\internal.llb\...​


This error message can be the result of many different scenarios. To correct the problem, try these troubleshooting steps:
  1. Make sure that all of the subVIs are running correctly (no broken arrows). Error 1003 can occur if any subVI is not executable.

  2. If you are using any Conditional Disable Diagrams in your program, check each subdiagram and ensure that the code in each case is not broken.  If a subdiagram that only executes under the Run Time Engine setting contains broken code, the run arrow for the top level VI will not appear broken in development mode, but Error 1003 can occur upon building .
  3. Perform a forced recompile by pressing Control + Shift, and clicking the Run button.
  4. If you installed the LabVIEW Application Builder separately, make sure its version matches your LabVIEW version (i.e. LabVIEW Application Builder 8.6 with LabVIEW 8.6). 
  5. Mass compile the VI before you build the executable.
  6. Ensure that all VIs used in the distribution have unique names
  7. If you are using VI Server, see Error 7 or 1003 Occurs When Using VI Server in a LabVIEW Application
  8. In Application Builder, under the Application Settings tab, deselect the Disconnect type definitions and Remove unused polymorphic VI instances option. 
  1. It is possible that the dependency files are saved in several locations and are not correctly added to the build. To ensure the files are located together, in the Project Window Select File >> Save As... >> "Duplicate .lvproj file and contents", making sure to Select "Include all dependencies". From this new project file, you should be able to build the executable.
  1. If you are using NI-SoftMotion, this issue may be due to editing the Axis control and saving it as a Type-Def. Please ensure that you are not editing the Axis controls.
  2. If the steps above on this page don't work, it may be an indication of a deeper corruption of your LabVIEW installation. If this is the case, a forced reinstallation is likely the best next step.

Additional Information

  • Step 3 forces LabVIEW to recompile, re-link, and recheck data dependencies from the ground up (as does the application builder), rather than in segments. After this is performed, the run arrow may become broken, which will allow you to trace the error list to the broken part of the VI and to fix it.
  • If two VIs of the same name located in two different places are called, the Application Builder may give this error
  • If you are using LabVIEW 7.0, check to make sure you do not have enumerated typedef with an empty element. This situation can cause Application Builder to return Error 1003.


Not Helpful