The Storage/DataPlugin VIs and the TDM Streaming VIs and functions can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.
| Code | Description |
|---|---|
| −68026 | Failed to delete data from the .tdms file, because channel names contains digital data. |
| −68025 | Failed to delete the index file after writing data to the TDMS file. National Instruments recommends that you delete the index file manually. |
| −68024 | The TDM Streaming VIs and Functions do not support extended-precision floating-point numbers on Linux, OS X, and VxWorks. |
| −68018 | Failed to update the .tdms file. This file might be incomplete due to an application crash during the logging process. You can still read the existing data from this file, but you cannot append new data to this file. Consider creating a new .tdms file for your application. |
| −68017 | The hierarchy of certain channels or groups in the file is not supported by the current version of LabVIEW. Upgrade LabVIEW to the latest version to fix this error. Contact National Instruments if this error persists. |
| −68016 | The data in certain channels or groups of the file is not supported. LabVIEW skips these channels or groups when listing content of the file. Upgrade LabVIEW to the latest version to fix this error. Contact National Instruments if this error persists. |
| −68015 | This channel contains multi-dimension data that is not recognized by the current version of LabVIEW. Upgrade LabVIEW to the latest version to fix this error. Contact National Instruments if this error persists. |
| −68014 | Failed to append data to the specified channel because the dimension of the new data does not match that of the existing data. |
| −68013 | Failed to access the specified channel because this channel is protected by LabVIEW. You cannot rename the group that contains the protected channel because renaming a group affects all channel names under that group. If you are creating a new channel or renaming an existing channel, use another channel name. |
| −68010 | File is still in use. Close all other references to this file before truncating the file. |
| −68009 | TDMS asynchronous mode is not initialized properly. Make sure the enable asynchronous? input of the TDMS Advanced Open function is TRUE. If you are writing data to a file, also make sure the TDMS Configure Asynchronous Writes (Data Ref) function exists. If you are reading data from a file, also make sure the TDMS Configure Asynchronous Reads (Data Ref) function exists. |
| −68008 | The data type input of the TDMS Configure Asynchronous Writes function is not wired. If the pre-allocate? input of this function is TRUE, you must wire a supported data type to this function. LabVIEW uses the data type information to determine the size of each pre-allocated buffer. The data type input accepts integers, floating-point numbers, Booleans, and timestamps. |
| −68007 | This channel or property value contains a data type that is not recognized by this version of LabVIEW. |
| −68006 | Failed to perform this operation. You cannot use the TDMS Advanced Asynchronous I/O functions and the TDMS Advanced Data Reference I/O functions jointly. |
| −68004 | Failed to manipulate the .tdms file when the file is opened with the TDMS Advanced Open function. You must either use the TDMS Open function to open the .tdms file or use the Advanced TDMS VIs and functions to manipulate the .tdms file. |
| −68003 | File is opened in asynchronous mode. You must either set the enable asynchronous input of the TDMS Advanced Open function to FALSE or use the TDMS Advanced Asynchronous Write or TDMS Advanced Asynchronous Read function to perform the operation. |
| −68002 | Failed to reserve file size. If you are running the TDMS Reserve File Size function on Windows with User Account Control enabled, you must run LabVIEW or the application with administrator privileges. Refer to the KnowledgeBase for more information about using User Account Control. |
| −68001 | Failed to perform the operation. You must use the TDMS Advanced Open function to open the .tdms file. |
| −68000 | Concurrent references to the same .tdms file cannot be opened with different values for the disable buffering? or enable asynchronous? input of the TDMS Advanced Open function. |
| −2595 | Failed to get the version information about the DataPlugin. |
| −2594 | An error occurred while connecting to the DataPlugin server. Possible reasons include a failed network connection or a server connection problem. |
| −2593 | An error occurred while installing the DataPlugin. Possible reasons include an invalid DataPlugin name or a failed network connection. |
| −2592 | TDMS does not support replacing channel values. |
| −2591 | You must install NI-DAQmx on the computer to store NI-DAQmx properties by using the Storage/DataPlugin VIs. |
| −2590 | Failed to export the DataPlugin. You can export only DataPlugins with a type of VBS or VBCrypt. Use the List DataPlugins VI to view the type of a DataPlugin. |
| −2589 | Failed to unregister the DataPlugin. You cannot unregister the DataPlugins that LabVIEW installs by default. |
| −2588 | Failed to register the DataPlugin. The DataPlugin .uri file might contain invalid DataPlugin information. |
| −2587 | LabVIEW failed to write data to the .tdms file. Ensure that the file format version you specified for the TDMS Open function supports the data you want to write. For example, to write interleaved data or data you acquire from an NI-DAQmx device, you must select 2.0 for the file format version input. To write data in big-endian format, you also must select 2.0 for the file format version input. |
| −2586 | Support for the TDMS file format is not currently installed on your machine. You can download it from the DataPlugins Web site at ni.com. |
| −2585 | The .tdm file format is not currently supported on this operating system. |
| −2583 | Cannot append data to the existing file because the value of the X Value Columns option of the Write to Measurement File Express VI changed. This error occurs when the value of the X Value Columns option changes from the value specified when the file was first created. To correct this error, use the same X Value Columns value when you use this Express VI to append data to an existing file. |
| −2582 | The Write to Measurement File Express VI cannot append new data to the file because the time information of the signals stored in the file does not match the signals you are trying to append. You can append waveforms only if their dt values match and the t0 value of the new data matches the next time increment after the last saved value. To correct this error, set the Segment Headers option to One header per segment. |
| −2581 | The Write to Measurement File Express VI cannot append new data to the file because the signals stored in the file don't match the signals you are trying to append. To correct this error, set the Segment Headers option to One header per segment. |
| −2578 | After deleting data from a file, you must close the file and reopen it before you can perform a read operation. |
| −2575 | Storage VIs version conflict. This version of LabVIEW cannot interpret the parameters of the Storage VI. The VI was created in a more recent LabVIEW version. |
| −2574 | The string you wired to this VI contains binary characters that are not valid entries for string values in a .tdm file. To store binary data, use data channels with a data type of 8-bit unsigned integer. |
| −2572 | This property is not part of the Storage VI data structure. |
| −2571 | This object type is not part of the Storage VI data structure. |
| −2570 | LabVIEW could not write the file back to disk. The file might be write protected by the operating system. To open the file for a read-only operation, select open (read only) in the Overwrite options (if not wired) pull-down menu in the Configure Open Data Storage dialog box. |
| −2569 | LabVIEW cannot convert the object ID into a valid refnum. An object with this ID does not exist in the data storage file. |
| −2568 | LabVIEW failed to allocate memory from the operating system of your computer. |
| −2566 | An input parameter to this VI is invalid. |
| −2565 | LabVIEW could not load the data channel you specified from the data storage file. The channel either is empty or the properties that describe the channel, such as length or data type, are incomplete. You might be trying to read data in a format that is not compatible with the format in which it was written. If you are using the Read Data VI, which reads multiple channels, consider using a query condition to exclude some of the channels from being loaded. You can determine the data type of a channel by reading the Data type property. |
| −2564 | The software installed on this computer does not support the file format you requested. The Storage/DataPlugin VIs access files through plug-in libraries LabVIEW and DIAdem install. Refer to the National Instruments Web site to download the library you need. |
| −2562 | The data type of a property or channel could not automatically be coerced when writing to or reading from a data storage file. |
| −2561 | Data storage is write-protected. LabVIEW cannot write data to this data storage file because it is write-protected. The file might be write protected by the operating system. To open the file for a read-only operation, select open (read only) in the Overwrite options (if not wired) pull-down menu in the Configure Open Data Storage dialog box. |
| −2560 | LabVIEW cannot load the USI components the Storage/DataPlugin VIs require. These components are installed by LabVIEW and DIAdem. Refer to the National Instruments Web site to download the components you need. You may need to reinstall LabVIEW or DIAdem. |
| −2559 | The data storage file is already open. |
| −2558 | LabVIEW cannot open the data storage file. Ensure that you chose a correct DataPlugin for this file format. |
| −2557 | There is an error in the query expression. |
| −2556 | LabVIEW cannot find the object type. |
| −2555 | LabVIEW cannot write to a read-only data storage file. |
| −2554 | LabVIEW does not support the data type of this property. |
| −2553 | The object refnum is invalid. The node that returned this refnum might have encountered an error and did not return a valid refnum. The storage this refnum refers to might have closed before the call executed. This error usually is the result of an error being encountered, such as failing to open a storage or looking for a channel that does not exist. Valid refnums become invalid when the storage they refer to is closed. |
| −2551 | The property data type does not match. |
| −2550 | This property does not exist. |
| −2549 | Asynchronous reads from an earlier operation are still in progress. You cannot configure or start an asynchronous read unless the previous operation has been completed or stopped. You can stop asynchronous reads by using the TDMS Stop Asynchronous Reads function. |
| −2547 | LabVIEW failed to complete this operation. Verify that the values of both the max asynchronous writes input of the TDMS Configure Asynchronous Writes function and the number of buffers input of the TDMS Configure Asynchronous Reads function are less than 64. Also verify the array size of the data input of the TDMS Advanced Write function is below the maximum value. Refer to the LabVIEW Help for more information about using the TDMS Advanced Write function. |
| −2546 | Asynchronous reads or writes failed due to timeout. Increase the timeout value for the corresponding function. |
| −2545 | TDMS asynchronous mode is not initialized properly. Make sure the enable asynchronous? input of the TDMS Advanced Open function is TRUE. If you are writing data to a file, also make sure the TDMS Configure Asynchronous Writes function exists. If you are reading data from a file, also make sure that both the TDMS Configure Asynchronous Reads and the TDMS Start Asynchronous Reads functions exist. |
| −2544 | With operating system buffering disabled, array sizes and file positions for the Advanced TDMS VIs and functions must be integer multiples of the hard disk sector size. Use the TDMS Advanced Open function to retrieve the sector size. |
| −2543 | LabVIEW failed to open the .tdms file for raw data access. This error occurs if the file format version is 1.0 or if the file contains raw data that is not encoded in native-endian. Use the TDMS Defragment function and the TDMS Convert Format VI to convert the file to native-endian and version 2.0. |
| −2542 | Files that contain DAQmx data samples cannot be processed by the TDMS Convert Format, TDMS Defragment, and TDMS Delete Data functions. |
| −2541 | Failed to scale the data in the .tdms file. The NI TDMS component on your computer does not support the scale type. Upgrade the NI TDMS component to the latest version before reading the .tdms file. Refer to the National Instruments Web site for information about installing the latest version of the NI TDMS component. |
| −2540 | Reading data that was streamed to a .tdms file by NI-DAQmx and data that was added to the file using a different application requires separate TDMS Read functions. |
| −2539 | This file cannot be written to, because it is opened and locked by another thread or process. This typically happens when a file is written by a hardware driver, for example NI-DAQmx. |
| −2538 | Failed to add scaling information to the TDMS object. This object contains scaling information that has already been applied. |
| −2537 | Failed to convert the "name" property to TDMS file format version 2.0. In file format version 2.0, "name" must be a string. To correct this error, you can use the new property name input of the TDMS Convert Format VI to specify a new name for the "name" property. |
| −2536 | LabVIEW failed to scale the data in the .tdms file. Ensure that this function supports the data type that you specify. |
| −2535 | LabVIEW failed to create a scale for the .tdms file. |
| −2534 | The type of interleaved data is not supported by TDMS. |
| −2533 | LabVIEW failed to save the data in interleaved format because the data is either an analog waveform, a compressed digital table or waveform, or a 1D or 2D string array. LabVIEW saved the data in decimated format. |
| −2532 | Invalid group name and/or channel name. |
| −2531 | LabVIEW could not unload the TDMS file component. |
| −2530 | Failed to perform the operation on this .tdms file because pending data for this file exists. Use the TDMS Flush function to flush the data to disk. |
| −2529 | In TDMS files, channels in the same channel group must have unique names. You can provide unique channel names by using the "channel name(s)" input of the specified TDM Streaming Function. If you are using waveforms or the LabVIEW Express Dynamic Data Type, use the waveform attribute "NI_UpdateChannelName" to set a channel name. |
| −2526 | LabVIEW dynamically calculates the value of this property. You cannot write any values to this property. This typically applies to properties like "NI_ChannelLength" or "NI_DataType". |
| −2525 | TDMS file data could not be converted into the specified data type. |
| −2524 | You have attempted to open a TDM file. Use the Read From Measurement File Express VI or the Storage/DataPlugin VIs to open this file. |
| −2522 | This TDMS file is open as a read-only file. Close the file before you open it for writing. |
| −2519 | LabVIEW could not load the TDMS file component. The component is expected in the National Instruments\shared\TDMS directory. You might need to reinstall LabVIEW to fix this problem. |
| −2518 | The specified array dimension is not supported. The TDMS functions support only 1D or 2D arrays. |
| −2516 | LabVIEW could not create an index file for this TDMS file. The disk might be write protected. Without an index file, LabVIEW will not be able to open the TDMS file. |
| −2515 | When appending data to an existing data channel, the data types of the existing data and the new data did not match. |
| −2514 | This function does not accept the specified data type. |
| −2513 | LabVIEW does not support properties of the specified data type. |
| −2511 | The specified TDMS file is corrupt. |
| −2510 | This TDMS file complies with a new version of the TDMS format that is not supported by this version of LabVIEW. Refer to the DataPlugins Web site at ni.com for more information about the TDMS file format. |
| −2509 | LabVIEW no longer supports this version of the TDMS file format. |
| −2508 | Invalid property. |
| −2507 | Invalid group name and/or channel name. |
| −2506 | LabVIEW failed to read data from the TDMS file. |
| −2505 | LabVIEW failed to write data to the TDMS file. |
| −2504 | LabVIEW failed to close the TDMS file. |
| −2503 | Specified file does not comply with TDMS file format standards. |
| −2502 | String values are stored in TDMS files in utf8 unicode format. LabVIEW uses operating system functions to convert the unicode data, and one of these operating system functions has returned an error. This error may indicate that you are using characters that are not supported within the language settings on your machine. |
| −2501 | Invalid TDMS file reference. |
| 2552 | This property does not contain data. |