LabVIEW installs built-in LabVIEW error codes and error codes for related drivers, toolkits, and modules as XML-based text files.
You also can select Help»Explain Error to display an error code description in the Explain Error dialog box. Enter the error code number in the Code field or, if the error code number is in hexadecimal format, in the Hex Code field. Press the <Enter> key or click anywhere in the dialog box to display a description of the error code in the Explanation field. This description is the same description that appears in this help file. You also can generate error cluster reports to obtain descriptions of built-in error codes.
If the VIs do not return a description, the error code text files might have been moved, deleted, or corrupted. This problem usually occurs when you use user-defined error codes, applications or shared libraries, or drivers released before LabVIEW 6.1.
Undefined errors can occur for many possible reasons. The following are some suggestions and ideas for ways to identify and handle undefined errors.
|Tip ActiveX error codes are documented by Microsoft in winerror.h.|
If you are developing an application or shared library, you must distribute any relevant error code text files with the application or shared library.
If you are using a driver that was released before LabVIEW 6.1, the driver installed a version of error.llb that contains all the driver error codes. The driver did not install error code text files to describe the driver error codes.
If you installed the legacy driver after installing LabVIEW 6.1, you must replace the driver's version of error.llb with the version of error.llb installed with LabVIEW 6.1 or LabVIEW 7.0.