Error 13 When Building a Build Specification in LabVIEW 2017

Updated May 23, 2023

Reported In


  • LabVIEW

Issue Details

I have a build specification in my LabVIEW 2017 project that includes an item with an extension other than *.vi or *.ctl, such as a *.vim or *.ctt. When I try to build that build specification, I receive Error 13. Why do I receive this error and how can I resolve it?


This behavior is a known issue in LabVIEW 2017 when building a build specification with a non *.vi or *.ctl file and using the Fast File Format advanced build option. The error will only occur if the following conditions are met:
  • Fast File Format is enabled in the Advanced category of the build specifications
  • The code being built calls a *.vim, *.vit, or *.ctt
  • The *.vim, *.vit, or *.ctt has at least one dependency on another file, such as through the inclusion of a Help file in the VI Properties of the file
  • The code being built calls at least one DLL (for example, the lvanlys.dll used by many LabVIEW functions or some external DLL)
Upgrading to LabVIEW 2017 SP1 is the recommended solution to resolve the error.

If you must stay in LabVIEW 2017, see the recommended approaches below:

DLLs and Executables
For DLLs and executables, the easiest solution is to disable the Fast File Format in the Advanced category of the build specification properties.
Packed Project Libraries
Packed Project Libraries (*.lvlibp, PPL) have the fast file format option enabled for all builds, and this option cannot be turned off. In this case, the current recommended workaround is to avoid using the file types in question when building a Packed Project Library.