LabVIEW CLI Error Code Family
Below are all of the Error Codes that belong to the LabVIEW CLI Error Code Family (see Error List for list of Families).
Code | Description |
---|---|
-350053 | LabVIEW CLI: (Hex 0xFFFAA89B) The CLI for LabVIEW failed to run the operation due to missing or bad files. Ensure all the required modules or toolkits are installed and all the necessary files for the operation are in a good state, for example, no broken or missing VIs in the operation folder. By default, all the predefined operations are stored in one of the following directories:
(Windows) C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI\Operations (macOS) /Library/Application Support/National Instruments/LabVIEW CLI/Operations (Linux) /usr/local/natinst/nilvcli/Operations |
-350052 | LabVIEW CLI: (Hex 0xFFFAA89C) You cannot initialize the logger multiple times. |
-350051 | LabVIEW CLI: (Hex 0xFFFAA89D) The CLI for LabVIEW failed to run the operation because the command contains illegal arguments. |
-350050 | LabVIEW CLI: (Hex 0xFFFAA89E) The CLI for LabVIEW failed to run the operation because one or more required arguments are missing in the command. |
-350008 | LabVIEW CLI: (Hex 0xFFFAA8C8) The CLI failed to launch LabVIEW. Check that you are using a licensed version of LabVIEW. |
-350007 | LabVIEW CLI: (Hex 0xFFFAA8C9) The CLI for LabVIEW failed to run the operation because the specified path(s) contains multiple operations with the specified operation name. |
-350006 | LabVIEW CLI: (Hex 0xFFFAA8CA) The CLI for LabVIEW failed to run the operation. Ensure all the necessary files of the operation are stored in a folder with the same name as the operation in one of the following directories. If the folder is in another directory, you must specify the directory using the "-AdditionalOperationDirectory" argument.
(Windows) C:\Program Files (x86)\National Instruments\Shared\LabVIEW CLI\Operations (macOS) /Library/Application Support/National Instruments/LabVIEW CLI/Operations (Linux) /usr/local/natinst/nilvcli/Operations |
-350005 | LabVIEW CLI: (Hex 0xFFFAA8CB) The CLI for LabVIEW failed to close LabVIEW. Ensure LabVIEW does not hang. |
-350004 | LabVIEW CLI: (Hex 0xFFFAA8CC) The CLI for LabVIEW failed to run because the path to LabVIEW is unknown. You must specify the path to LabVIEW using the "-LabVIEWPath" argument on macOS or Linux. |
-350003 | LabVIEW CLI: (Hex 0xFFFAA8CD) The CLI for LabVIEW failed to establish a connection with the specified LabVIEW because the port is currently in use by another version of LabVIEW with VI server enabled. To fix this error, close the other version of LabVIEW or switch to a different port number by selecting "Tools>>Options>>VI Server" and entering the port number under "TCP/IP" |
-350002 | LabVIEW CLI: (Hex 0xFFFAA8CE) The CLI for LabVIEW failed to launch LabVIEW. Ensure the specified path to LabVIEW is correct. |
-350001 | LabVIEW CLI: (Hex 0xFFFAA8CF) The CLI for LabVIEW failed to get the path to the most recent version of LabVIEW used on the machine. You must specify the path to LabVIEW using the "-LabVIEWPath" argument. |
-350000 | LabVIEW CLI: (Hex 0xFFFAA8D0) The CLI for LabVIEW failed to establish a connection with LabVIEW. Ensure LabVIEW is running with VI server enabled on the correct port number. To enable VI server in LabVIEW, select "Tools>>Options>>VI Server" and enable the "TCP/IP" checkbox. If the port number under "TCP/IP" is not 3363, you must specify the port number using the "-PortNumber" argument. |