LabVIEW Error 1498 Occurred at Get LV Class Default Value

Updated Jul 31, 2023

Reported In


  • LabVIEW
  • Data Record AD

Issue Details

  • When I try to build an executable in LabVIEW, I get the error message described below.
  • I developed an application in LabVIEW that contains the base class for dynamically dispatching plugins during run-time. After building the executable, when the application tries to launch the child class, I get the error message described below.
  • My application calls some dlls via Call Library Function Nodes, which works in source code, but I am getting this error when running the executable.
Error 1498 occurred at Get LV Class Default
Possible reason(s):
LabVIEW: Library has errors. Fix the errors before attempting this operation.



This error occurs because the library is unable to run properly. Often this is because a dependency is missing, but it can also be down to a corrupt install.

If calling a .dll from within your class, LabVIEW will copy the .dll called when making the library. It cannot see any other dependencies of that original dll, so you need to ensure these are included in the build by:
  • Add the called dll and it's other dependencies to the Always Included of the LabVIEW project Build Specification.
  • Also note this Knowledgebase article about executables and dlls specifically.

Other methods that have been seen to maybe resolve this issue are:

Method 1: Separate compiled code from source code

For you to overcome the issue, follow the mentioned steps:

  • Click on File and open VI Properties.
  • Uncheck the box mentioning Separate compiled code from source code (As shown in the diagram).
  • Save the VI.
  • Build the executable with the new VI and run it again.

Method 2: Build child class into source distribution file

You can try to build all the related child class into source distribution file. When building executable, include all child class that is built into source distribution file. For more information on how to build source distribution file, please refer to this article.

Method 3: Reinstall the software

If previous methods don't fix this issue, then it is suggested to uninstall and reinstall the software. This issue can be also related to corruption of the programming environment.

Additional Information

When you separate compiled code from the source file, there are some benefits such as smaller file size and source code control. However, when calling a VI in run-time engine dynamically, the application will look for the compiled code and if it is not available, then it will fail to run the VI.