Error 1003 Occurs When Trying to Create an Executable

Issue Details

Error 1003 occurred at C:\....\internal.llb\...​

Error 1003 occurred at C:\....\[my_filename].lvlib\...​

Error 1003 occurred at [a VI's path and name].vi

Solution

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. Try running LabVIEW as administrator. 
3. If you are using absolute paths, make sure that the executable can find all the files being called. It is always recommended to use relative paths when building an executable that calls VIs or files by reference nodes. 
4. 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.
5. Perform a forced recompile by holding Control+Shift while clicking the Run button.
6. If you installed the LabVIEW Application Builder separately, make sure its version matches your LabVIEW version (i.e. LabVIEW Application Builder 2018 with LabVIEW 2018).
7. Mass compile your VIs before you build the executable.
8. Ensure that all VIs used in the distribution have unique names.
9. If you used Diagram Disable Structures during development, be sure to enable the code or delete these structures.
10. If you are using VI Server, see Error 7 or Error 1003 Occurs when Using VI Server in a LabVIEW Application
11. In Application Builder, under the Application Settings tab, deselect Disconnect type definitions and Remove unused polymorphic VI instances:

9. It is possible that the dependency files are accidentally saved in several different locations and cannot be correctly added to the build. To ensure the files are located together, test the following: In the Project Window, go to menu File » Save As » Duplicate .lvproj file and contents, selecting Include all dependencies. Afterwards, open this newly created project file, and try building your executable from it.

10. If you are using NI-SoftMotion, this issue may be due to editing the Axis control and saving it as a Type Definition. Please ensure that you are not editing the Axis controls.
11. 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 bottom dependencies to the top-level-vi of your project (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 a VI to fix it.
• If two VIs of the same name located in two different places are called, the Application Builder may give an error due to potentially cross-referencing. Please be aware that a VI inside a library can have the same name as a VI outside of an library, as the library name is used to identify a VI as well. E.g. using library.lvlib\my.vi and my.vi in the same application will work.
• In case you are using LabVIEW 7.0, make sure you do not have enumerated typedef with an empty element. This situation can cause Application Builder to return Error 1003.
• In rare cases, a corrupt stock VI may cause Error 1003 to occur. To fix this, locate the .llb folder containing the corrupt VI and replace it with a different version of the .llb folder. You should be able to copy the .llb folder from another version of LabVIEW to replace it. If you do not have an additional version of LabVIEW that you can copy this file from, contact NI Support for assistance.
• If you are using LabVIEW classes, check that there are no circular references since this could cause error 1003. If you remove the circular dependencies you should be able to rebuild the exe successfully.
• This error might appear when trying to compile an FPGA VI, in that case, reinstalling LabVIEW and the LabVIEW FPGA Module might solve the issue.