NI Platform Services Error Code Family
Below are all of the Error Codes that belong to the NI Platform Services Error Code Family (see Error List for list of Families).
| Code | Description |
|---|---|
| -380766 | Unable to load the specified library. |
| -380765 | An unexpected software error occurred. |
| -380764 | The PXI system description files are present but inaccessible. This may be a temporary problem caused by another process accessing the files. Contact NI if the problem persists. |
| -380763 | The PXI system description files are locked by another process. This may be a temporary problem caused by another process accessing the files. Contact NI if the problem persists. |
| -380762 | Unable to verify the PXI system information is up to date. |
| -380761 | The PXISA trigger manager library for the PXI chassis was not found. Ensure the software for your PXI chassis is installed and up to date. |
| -380760 | An internal software error occurred. |
| -380759 | This slot is not connected to the requested type of PXI trigger bus. To use this type of PXI trigger bus, move your device to another slot. |
| -380758 | There is no PXI_Star connection for this slot because it is a PXI system timing slot. If the device supports PXI system timing controller functionality, use a numbered PXI_Star connection to access the system timing slot's PXI_Star lines, or move the device to another slot. |
| -380757 | The requested PXI information is not available. Verify that the PXI Resource Manager for the system is up to date. Use NI MAX to select the active PXI Resource Manager for the system. |
| -380756 | An internal software error occurred. |
| -380755 | An internal software error occurred. |
| -380754 | An internal software error occurred. |
| -380753 | The PXI system description files are internally inconsistent. The PXI Resource Manager may be generating incorrect files. Use NI MAX to select the active PXI Resource Manager for the system. |
| -380752 | An internal software error occurred. |
| -380751 | The requested device, chassis, or controller is unknown to the PXI subsystem. |
| -380750 | The requested memory could not be allocated. |
| -89000 | An internal error occurred. |
| -52031 | The specified resource is currently in use. |
| -52030 | The current application development environment is not supported. |
| -52029 | The specified format is not supported. |
| -52028 | The specified language is not supported. |
| -52027 | The specified string contains characters that cannot be interpreted due to the installed language support and system locale settings.
If possible, do not use this character. Otherwise, ensure that the appropriate language support is installed on the system, and that the system locale is set correctly. For most Windows operating systems, this is done through the Regional Settings option in the Control Panel. For LabVIEW RT targets, install Language Support for LabVIEW RT and change the locale setting for the remote system on the System Settings tab in MAX. |
| -52026 | The operation could not be completed because the user does not have sufficient permissions. Consider running as an administrator. |
| -52025 | The operation was interrupted by a user mode signal. |
| -52024 | An unknown or unexpected communication fault occurred while attempting to read data from or write data to a device. |
| -52023 | No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified. |
| -52022 | IO processing is not active. |
| -52021 | There is not enough power to complete the requested operation. |
| -52020 | The requested resource has been removed. |
| -52019 | The supplied buffer is too small. |
| -52018 | A hardware failure has occurred. The operation could not be completed as specified. |
| -52017 | The operation you requested is redundant or invalid when the object is in this state. |
| -52016 | The thread was running when you attempted to start it (redundant state change). |
| -52015 | The acquisition of the synchronization object failed. |
| -52014 | The synchronization object was abandoned by the previous holder. |
| -52013 | The name or handle requested has already been reserved by another client. |
| -52012 | There is no more data available to read or no more space available in which to write. |
| -52011 | The operation has begun and will complete asynchronously. |
| -52010 | The requested resource must be initialized before use. |
| -52009 | The requested resource has been marked for deletion and is rejecting new requests. |
| -52008 | An unexpected operating system error occurred. |
| -52007 | The requested operation did not complete in time. |
| -52006 | The requested resource was not located. |
| -52005 | The parameter received by the function is not valid. |
| -52004 | The dynamic cast operation failed. |
| -52003 | An unexpected software error occurred. |
| -52002 | The requested feature is not supported. |
| -52001 | The memory could not be page locked. |
| -52000 | The specified number of bytes could not be allocated. |
| -50808 | A USB transfer failed due to a transaction error reported by the USB host controller. This may be due to a fault in the system's USB host controller, a USB cable, or a USB device. |
| -50807 | Applicable to a 1394 bus. An isochronous buffer descriptor was not found or a link driver stream failed to be connected or disconnected. |
| -50806 | Applicable to TCP Connections. Applicable to UDP/TCP Connections. An invalid address was used (i.e. sending to address 0). Note: The TCP stack prohibits connecting to the loopback address from a non-loopback address. |
| -50805 | Applicable to TCP Connections. This is a more specific version of kPALStatusConnectionRefused. The stream has already been opened at the same address and port. |
| -50804 | Applicable to TCP Connections. The stream/device was setup incorrectly (i.e. invalid buffer size etc.) or the device is no longer in a good state. |
| -50803 | Applicable to TCP Connections. The connection was aborted by the remote peer. |
| -50802 | Applicable to TCP Connections. A surprise removal of the underlying device occurred and/or the connection was aborted. |
| -50801 | Unable to connect to remote host. Please check that all network segments between this host and the remote host are working and that the remote host is ready to accept connections. |
| -50800 | Applicable to a 1394 bus. The generation count on the packet submitted is incorrect and the entire transfer failed. |
| -50700 | The wait function was interrupted by an internal or external source and has returned. The operation has not been completed as specified, and subsequent waits may also not complete. |
| -50651 | No messages could be read because the message queue is empty. The operation could not be completed as specified. |
| -50650 | The message could not be written because the message queue is full. The operation could not be completed as specified. |
| -50604 | The specified thread could not be joined because the thread has already exited or has been terminated. The operation could not be completed as specified. |
| -50603 | The specified stack size is not supported. The operation could not be completed as specified. |
| -50602 | The wrong instance of iThreadController was used while attempting to join to a thread. The operation could not be completed as specified. |
| -50601 | An internal thread data structure has been corrupted. The operation could not be completed as specified. |
| -50600 | The specified thread is not runnable. The operation could not be completed as specified. |
| -50551 | The thread that acquired the synchronization object has exited or has been terminated. This error applies to mutex-like synchronization objects, where the thread that acquires the synchronization object owns it until the thread releases it. The resource that the synchronization object protects may be in an unknown state. |
| -50550 | A synchronization object was not acquired within the time limit. The operation could not be completed as specified. |
| -50503 | The Receiver Socket is invalid. The operation could not be completed as specified. |
| -50502 | The Socket Listener specified is invalid. The operation could not be completed as specified. |
| -50501 | The Socket Listener is already registered. The operation could not be completed as specified. |
| -50500 | The dispatch function has already been exported. |
| -50450 | A DMA link event was missed - probably because the interrupt was not serviced in time. The data being moved is incomplete as a result. The operation could not be completed as specified. |
| -50413 | A transfer was aborted because of a hardware error on the bus on which the transfer was occurring. |
| -50412 | A transfer was aborted because it could not be completed within the maximum number of retry attempts allowed by the bus on which the transfer was occurring. |
| -50411 | There was no more data in the buffer when new data was being read. The data returned by the operation is stale as a result. |
| -50410 | There was no more space in the buffer when new data was written. The oldest unread data in the buffer was lost as a result. |
| -50409 | A hardware buffer has overflowed. |
| -50408 | A hardware buffer has underflowed. |
| -50407 | There is no more space in the buffer. |
| -50406 | There is no more data in the buffer |
| -50405 | No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified. |
| -50404 | No transfer is in progress because the transfer was halted by the system. The operation could not be completed as specified. |
| -50403 | A transfer is already in progress. The operation could not be completed as specified. |
| -50402 | No transfer is in progress because no transfer was initiated. The operation could not be completed as specified. |
| -50401 | An unknown or unexpected communication fault occurred while attempting to read data from or write data to a device. |
| -50400 | The transfer did not complete within the timeout period or within the specified number of retries. |
| -50355 | The Memory Manager detected that one or more allocated chunks were not freed. The operation was completed but the state of the system may be unreliable. |
| -50354 | The Memory Manager detected corruption in its internal data structures. The state of the system may be unreliable. |
| -50353 | One or more memory pages in the specified logical buffer could not be locked into physical memory. The operation could not be completed as specified. |
| -50352 | The requested memory could not be allocated. |
| -50351 | The specified buffer is aligned to an address boundary that prevents moving data to or from the specified device. The operation could not be completed as specified. |
| -50350 | A memory configuration problem is interfering with a background transfer mechanism. This could mean that a buffer failed to be allocated or that a buffer was allocated but is not in the address range of the targeted bus master. The operation could not be completed as specified. |
| -50303 | The specified device could not be initialized. The operation could not be completed as specified. |
| -50302 | The specified device is managed by this software stack but a resource or some other sort of functionality associated with the device is not currently supported by this software stack. The operation could not be completed as specified. |
| -50301 | The specified device is not managed by this software stack. The operation could not be completed as specified. |
| -50300 | The specified device is not present or is deactivated. The operation could not be completed as specified. |
| -50265 | The specified feature is implemented but has been disabled in the current environment. The operation could not be completed as specified. |
| -50264 | The specified software component is busy or still in use. The operation could not be completed as specified. |
| -50263 | The specified software component has already been installed. The operation could not be completed as specified. |
| -50262 | The specified software component cannot be unloaded. The operation could not be completed as specified. |
| -50261 | The specified software component is not currently loaded. The operation could not be completed as specified. |
| -50260 | The specified software component has already been loaded. The operation could not be completed as specified. |
| -50259 | The specified software component has circular dependency. The operation could not be completed as specified. |
| -50258 | The specified software component failed to initialize. The operation could not be completed as specified. |
| -50257 | The specified software component could not be loaded because its image is corrupt. The operation could not be completed as specified. |
| -50256 | The specified feature has not been implemented for this environment. The operation could not be completed as specified. |
| -50255 | A function imported from another library could not be found. The operation could not be completed as specified. |
| -50254 | The specified function is no longer supported. The operation could not be completed as specified. |
| -50253 | The specified software component is not backward compatible with the client that was attempting to load it. The client was not loaded. |
| -50252 | The specified software component is not forward compatible with the client that was attempting to load it. The client was not loaded. |
| -50251 | The specified software component is not available. The component was not loaded. |
| -50250 | Two or more components of the package being loaded are unable to operate together due to a version mismatch. A failure of this sort is generally indicative of an installation problem. The package was not loaded. |
| -50209 | An undetermined failure occurred while operating on the specified file. The operation could not be completed as specified. |
| -50208 | A failure occurred while attempting to write a buffer to the specified file. The operation could not be completed as specified. |
| -50207 | A failure occurred while attempting to read a buffer from the specified file. The operation could not be completed as specified. |
| -50206 | The specified offset in the specified file could not be found. The operation could not be completed as specified. |
| -50205 | The specified file could not be closed. The operation could not be completed as specified. |
| -50204 | The specified file could not be opened. The operation could not be completed as specified. |
| -50203 | There is no more space on the targeted disk. The operation could not be completed as specified. |
| -50202 | A system call returned an error. The operation could not be completed as specified. |
| -50201 | A system call returned an error while NI Platform Services was launching. The NI Platform Services launch could not be completed. |
| -50200 | This function has not been implemented for this operating system. The operation could not be completed as specified. |
| -50175 | The specified mathematical operation results in an overflow. |
| -50152 | A hardware failure has occurred. The operation could not be completed as specified. |
| -50151 | The firmware - which is software resident on a device - has entered an unknown state usually as a result of a cascade failure induced by an unexpected series of state inputs. The operation could not be completed as specified, and you should immediately terminate all further transactions if you are able to do so. |
| -50150 | The software has entered an unknown state - usually as a result of a cascade failure induced by an unexpected series of state inputs. The operation could not be completed as specified and you should immediately terminate all further transactions if you are able to do so. |
| -50108 | The message-transport queue for the implied arena is full. The operation could not be completed as specified. |
| -50107 | The specified resource is ambiguous or a unique resource could not be determined based on the qualifying attributes. The operation could not be completed as specified. |
| -50106 | The resource is in use. The operation could not be completed as specified. |
| -50105 | The resource was already initialized and cannot be initialized again. The operation could not be completed as specified. |
| -50104 | The specified resource has not been initialized. The operation could not be completed as specified. |
| -50103 | The specified resource is reserved. The operation could not be completed as specified. |
| -50102 | The specified resource is not reserved. The operation could not be completed as specified. |
| -50101 | The requested resource does not exist or exists but is in a state which prevents its reservation. The operation could not be completed as specified. |
| -50100 | The resource is controlled by the OS or a related system and should not be manipulated directly. The operation could not be completed as specified. |
| -50020 | The specified token is not valid. The operation could not be completed as specified. |
| -50019 | The specified multitasking mode is invalid. The operation could not be completed as specified. |
| -50018 | The library specifier is invalid. The operation could not be completed as specified. |
| -50017 | The specified address space is not a valid address space. The operation could not be completed as specified. |
| -50016 | The specified window type is not valid or is inappropriate in the context of the current device configuration. The operation could not be completed as specified. |
| -50015 | The specified address class is not valid in the context of the current device configuration. The operation could not be completed as specified. |
| -50014 | The specified count is too small or large or of the wrong granularity for write operations. In cases where an offset is also specified the maximum count may be derived from the offset. The operation could not be completed as specified. |
| -50013 | The specified offset is out of range for write operations. The operation could not be completed as specified. |
| -50012 | The specified mode is not supported for write operations. The operation could not be completed as specified. |
| -50011 | The specified count is too small or large or of the wrong granularity for read operations. In cases where an offset is also specified the maximum count may be derived from the offset. The operation could not be completed as specified. |
| -50010 | The specified offset is out of range for read operations. The operation could not be completed as specified. |
| -50009 | The specified mode is not supported for read operations. The operation could not be completed as specified. |
| -50008 | The specified count is too small or large or of the wrong granularity. In cases where an offset is also specified the maximum count may be derived from the offset. The operation could not be completed as specified. |
| -50007 | The specified offset is out of range. The operation could not be completed as specified. |
| -50006 | The specified mode is not supported. The operation could not be completed as specified. |
| -50005 | The specified data width is not supported or cannot be transferred on the bus. The operation could not be completed as specified. |
| -50004 | A pointer-type parameter is invalid. This may mean that the pointer is NULL when it should not be or not NULL when it should be or is not NULL but does not appear to point to the appropriate type of object or data. The operation could not be completed as specified. |
| -50003 | A selector - usually of an enumerated type - is inappropriate or out of range. The operation could not be completed as specified. |
| -50002 | The specified device is not a valid device. The operation could not be completed as specified. |
| -50001 | An attribute whether explicit or implicit is not relevant or is not relevant given the current system state. The operation could not be completed as specified. |
| -50000 | The value of one of the specified parameters conflicts with the state or the value of another parameter. The operation could not be completed as specified. |
| -26853 | The call should be retried. |
| -26852 | At least one of the PXI System Description files does not exist. |
| -26851 | Initialization completed using existing PXI system files. PXI System files were not regenerated due to a user setting. |
| -26850 | The PXI System has already been initialized. |
| -26809 | Some PXI features are unavailable because one or more PXI system description files could not be read properly. For more information, visit ni.com/info and enter the Info Code exvgq4. |
| -26808 | The PXISA configuration file is currently locked and inaccessible. |
| -26807 | The NI PXI Resource Manager is not currently the active PXI resource manager for the system. |
| -26806 | The attribute is invalid. |
| -26805 | The handle is invalid. |
| -26804 | The NI PXI Resource Manager service is inaccessible, probably because it is either not running, or still starting up. |
| -26803 | A component recursively called into the PXI resource manager while it was initializing. |
| -26802 | A timeout occurred. |
| -26801 | An unspecified error occurred in the PXI subsystem. |
| -26657 | No handler is known for the specified data tree. |
| -26656 | Data requested is incompatible with the specified data type. |
| -26655 | File is internally inconsistent. |
| -26654 | Child not found. |
| -26653 | Attribute not found. |
| -26652 | Error reading or writing file. |
| -26651 | Error reading file. |
| -26650 | Error opening file. |
| -26621 | Invalid Parameter |
| -26620 | Conflict detected while renumbering a chassis. |
| -26600 | MXS PXI system not found |
| -26550 | PCI description string parse error |
| -26500 | Module parse error |
| -26452 | Peripheral Registration Parse Error |
| -26451 | Peripheral Driver Error |
| -26450 | Peripheral Driver Load Error |
| -26404 | The PXI system description file is invalid. Contact the vendor of your PXI resource manager software to resolve the issue. |
| -26403 | System description spec limitation |
| -26402 | System description write error |
| -26401 | System description parse error |
| -26400 | System description file not found |
| -26352 | Controller registration parse error |
| -26351 | Controller driver error |
| -26350 | Controller driver load error |
| -26302 | Controller parse error |
| -26301 | Controller type invalid |
| -26300 | Controller file not found |
| -26253 | Chassis Driver Not Found |
| -26252 | Chassis Registration Parse Error |
| -26251 | Chassis Driver Error |
| -26250 | Chassis Driver Load Error |
| -26209 | Chassis EEPROM Unrecognized Version |
| -26208 | Chassis EEPROM Invalid |
| -26207 | Chassis Hardware Not Found |
| -26206 | Chassis trigger parse error |
| -26205 | Chassis bridge parse error |
| -26204 | Chassis slot parse error |
| -26203 | Chassis segment parse error |
| -26202 | Chassis parse error |
| -26201 | Chassis bridge not found |
| -26200 | Chassis file not found |
| -26113 | The buffer is insufficient to hold the data requested. |
| -26112 | Error creating directory. |
| -26111 | Access Denied |
| -26110 | File path not found. |
| -26109 | File already exists. |
| -26108 | Error reading file. |
| -26107 | Error deleting file. |
| -26106 | Error copying file. |
| -26105 | File could not be closed. |
| -26104 | Error opening file. |
| -26103 | File not found. |
| -26102 | System not initialized |
| -26101 | Invalid configuration |
| -26100 | Allocation error |
| -26010 | The PXISA trigger manager for the chassis reports that the chassis has been disconnected. |
| -26009 | The PXISA trigger manager for the chassis reports that another application has already reserved the line. |
| -26008 | The PXISA trigger manager for the chassis reports that the destination of this route is already used by a different backplane route. |
| -26007 | The PXISA trigger manager for the chassis reports that there is a conflicting route, and the line could not be unreserved. |
| -26006 | The PXISA trigger manager for the chassis reports that the line is currently being used for a conflicting route. |
| -26005 | The PXISA trigger manager for the chassis reports that the line is already reserved by this application. |
| -26004 | The PXISA trigger manager for the chassis reports the destination line for the route is not reserved, but this reservation is required for the route to be programmed. |
| -26003 | The PXISA trigger manager for the chassis reports the line was not reserved. Verify that another application or API is not clearing trigger reservations it has not created. |
| -26002 | The PXISA trigger manager for the chassis was called with an invalid parameter. |
| -26001 | The PXISA trigger manager for the chassis does not support the requested operation. |
| -26000 | The PXISA trigger manager for the chassis returned a vendor-specific or generic error. |
| 26000 | The PXISA trigger manager for the chassis returned a vendor-specific or generic error. |
| 26001 | The PXISA trigger manager for the chassis does not support the requested operation. |
| 26002 | The PXISA trigger manager for the chassis was called with an invalid parameter. |
| 26003 | The PXISA trigger manager for the chassis reports the line was not reserved. Verify that another application or API is not clearing trigger reservations it has not created. |
| 26004 | The PXISA trigger manager for the chassis reports the destination line for the route is not reserved, but this reservation is required for the route to be programmed. |
| 26005 | The PXISA trigger manager for the chassis reports that the line is already reserved by this application. |
| 26006 | The PXISA trigger manager for the chassis reports that the line is currently being used for a conflicting route. |
| 26007 | The PXISA trigger manager for the chassis reports that there is a conflicting route, and the line could not be unreserved. |
| 26008 | The PXISA trigger manager for the chassis reports that the destination of this route is already used by a different backplane route. |
| 26009 | The PXISA trigger manager for the chassis reports that another application has already reserved the line. |
| 26010 | The PXISA trigger manager for the chassis reports that the chassis has been disconnected. |
| 26100 | Allocation error |
| 26101 | Invalid configuration |
| 26102 | System not initialized |
| 26103 | File not found. |
| 26104 | Error opening file. |
| 26105 | File could not be closed. |
| 26106 | Error copying file. |
| 26107 | Error deleting file. |
| 26108 | Error reading file. |
| 26109 | File already exists. |
| 26110 | File path not found. |
| 26111 | Access denied. |
| 26112 | Error creating directory. |
| 26113 | The buffer is insufficient to hold the data requested. |
| 26200 | Chassis file not found |
| 26201 | Chassis bridge not found |
| 26202 | Chassis parse error |
| 26203 | Chassis segment parse error |
| 26204 | Chassis slot parse error |
| 26205 | Chassis bridge parse error |
| 26206 | Chassis trigger parse error |
| 26300 | Controller file not found |
| 26301 | Controller type invalid |
| 26302 | Controller parse error |
| 26350 | Controller driver load error |
| 26351 | Controller driver error |
| 26352 | Controller registration parse error |
| 26400 | System description file not found |
| 26401 | System description parse error |
| 26402 | System description write error |
| 26403 | System description spec limitation |
| 26404 | The PXI system description file is invalid. Contact the vendor of your PXI resource manager software to resolve the issue. |
| 26450 | Peripheral Driver Load Error |
| 26451 | Peripheral Driver Error |
| 26452 | Peripheral Registration Parse Error |
| 26500 | Module parse error |
| 26550 | PCI description string parse error |
| 26600 | MXS PXI system not found |
| 26620 | Conflict detected while renumbering a chassis. |
| 26621 | Invalid Parameter |
| 26650 | Error opening file. |
| 26651 | Error reading file. |
| 26652 | Error reading or writing file. |
| 26653 | Attribute not found. |
| 26654 | Child not found. |
| 26655 | File is internally inconsistent. |
| 26656 | Data requested is incompatible with the specified data type. |
| 26657 | No handler is known for the specified data tree. |
| 26801 | An unspecified error occurred in the PXI subsystem. |
| 26802 | A timeout occurred. |
| 26803 | A component recursively called into the PXI resource manager while it was initializing. |
| 26804 | The NI PXI Resource Manager service is inaccessible, probably because it is either not running, or still starting up. |
| 26805 | The handle is invalid. |
| 26806 | The attribute is invalid. |
| 26807 | The NI PXI Resource Manager is not currently the active PXI resource manager for the system. |
| 26808 | The PXISA configuration file is currently locked and inaccessible. |
| 26809 | Some PXI features are unavailable because one or more PXI system description files could not be read properly. For more information, visit ni.com/info and enter the Info Code exvgq4. |
| 26850 | The PXI System has already been initialized. |
| 26851 | Initialization completed using existing PXI system files. PXI System files were not regenerated due to a user setting. |
| 26852 | At least one of the PXI System Description files does not exist. |
| 26853 | The call should be retried. |
| 50000 | The value of one of the specified parameters conflicts with the state or the value of another parameter. The operation was completed by ignoring or overriding the conflicting parameters. |
| 50001 | An attribute, whether explicit or implicit, is not relevant or is not relevant given the current system state. The operation was completed by ignoring or overriding the attribute in question. |
| 50002 | The specified device is not a valid device. The operation was completed by ignoring or overriding the device parameter. |
| 50003 | A selector, usually of an enumerated type, is inappropriate or out of range. The operation was completed by ignoring or overriding the selector. |
| 50004 | A pointer-type parameter is invalid. This may mean that the pointer is NULL when it should not be, or not NULL when it should be, or is not NULL but does not appear to point to the appropriate type of object or data. The operation was completed by ignoring or overriding the pointer. |
| 50005 | The specified data width is not supported or cannot be transferred on the bus. The operation was completed by ignoring or overriding the specified data width. |
| 50006 | The specified mode is not supported. The operation was completed by ignoring or overriding the mode. |
| 50007 | The specified offset is out of range. The operation was completed by ignoring or overriding the offset. |
| 50008 | The specified count is too small, too large, or of the wrong granularity. In cases where an offset is also specified, the maximum count may be derived from the offset. The operation was completed by ignoring or overriding the count. |
| 50009 | The specified mode is not supported for read operations. The operation was completed by ignoring or overriding the mode. |
| 50010 | The specified offset is out of range for read operations. The operation was completed by ignoring or overriding the offset. |
| 50011 | The specified count is too small, too large, or of the wrong granularity for read operations. In cases where an offset is also specified, the maximum count may be derived from the offset. The operation was completed by ignoring or overriding the count. |
| 50012 | The specified mode is not supported for write operations. The operation was completed by ignoring or overriding the mode., |
| 50013 | The specified offset is out of range for write operations. The operation was completed by ignoring or overriding the offset. |
| 50014 | The specified count is too small, too large, or of the wrong granularity for write operations. In cases where an offset is also specified, the maximum count may be derived from the offset. The operation was completed by ignoring or overriding the count. |
| 50015 | The specified address class is not valid in the context of the current device configuration. The operation was completed by ignoring or overriding the address class. |
| 50016 | The specified window type is not valid, or is inappropriate in the context of the current device configuration. The operation was completed by ignoring or overriding the window type. |
| 50019 | The specified multitasking mode is invalid. The operation was completed by ignoring or overriding the multitasking mode. |
| 50100 | The resource is controlled by the OS or a related system and should not be manipulated directly. The operation was completed but the state of the system may be unreliable. |
| 50101 | The requested resource does not exist, or exists but is in a state which prevents its reservation. The operation was completed by reserving a functional subset of the requested resource. |
| 50102 | The specified resource is not reserved. The operation was completed by reserving the resource or by ignoring or overriding the specified resource. |
| 50103 | The specified resource is reserved. The operation was completed by ignoring or overriding the specified resource. |
| 50104 | The specified resource has not been initialized. The operation was completed by initializing the resource on your behalf. |
| 50105 | The resource was already initialized. The operation was completed by initializing the resource again which may have invalidated the state of your system as you understand it. |
| 50106 | The resource is in use. The operation was partially completed which may have invalidated the state of your system as you understand it. |
| 50107 | The specified resource is ambiguous or a unique resource could not be determined based on the qualifying attributes. The operation was completed but doing so may have invalidated the state of your system as you understand it. |
| 50151 | The firmware, which is software resident on a device, has entered an unknown state, usually as a result of a cascade failure induced by an unexpected series of state inputs. The operation was completed by disabling the firmware thus restoring the intrinsic behavior of the device. |
| 50152 | A hardware failure has occurred. The operation was completed by using alternative hardware. |
| 50200 | This function is not relevant for this operating system. No operation was performed. |
| 50202 | A system call returned a warning. The operation was completed but the state of the system may be unreliable. |
| 50254 | The specified function has been deprecated. The operation was completed but you should update your source code as soon as it is practical to do so. |
| 50255 | A function imported from another library could not be found. The operation was completed through alternate means. |
| 50256 | The specified feature may not operate as expected in this environment. The operation was completed but doing so may have invalidated the state of your system as you understand it. |
| 50258 | The specified software component initialized but returned a warning. The operation was completed but the state of the system may be unreliable. |
| 50260 | The specified software component has already been loaded. |
| 50262 | The specified software component cannot be unloaded. The operation was completed through alternate means. |
| 50351 | The specified buffer is aligned to an address boundary that prevents moving data to or from the specified device in an efficient manner. The operation was completed by using a smaller data width. |
| 50355 | The Memory Manager detected that one or more allocated chunks were not freed. The operation was completed but the state of the system may be unreliable. |
| 50402 | No transfer is in progress because no transfer was initiated. The operation was completed but doing so may have invalidated the state of your system as you understand it. |
| 50403 | A transfer is already in progress. The operation was completed but doing so may have invalidated the state of your system as you understand it. |
| 50404 | No transfer is in progress because the transfer was halted by the system. The operation was completed but doing so may have invalidated the state of your system as you understand it. |
| 50405 | No transfer is in progress because the transfer was aborted by the client. The operation was completed but doing so may have invalidated the state of your system as you understand it. |
| 50406 | There is no more data in the buffer. |
| 50407 | There is no more space in the buffer. |
| 50408 | A hardware buffer has underflowed. |
| 50409 | A hardware buffer has overflowed. |
| 50410 | There was no more space in the buffer when new data was written. The oldest unread data in the buffer was lost as a result. |
| 50411 | There was no more data in the buffer when new data was being read. The data returned by the operation is stale as a result. |
| 50500 | The dispatch function has already been exported. |
| 50551 | The thread that acquired the synchronization object has exited or has been terminated. |
| 52000 | The specified number of bytes could not be allocated. |
| 52001 | The memory could not be page locked. |
| 52002 | The requested feature is not supported. |
| 52003 | An unexpected software error occurred. |
| 52004 | The dynamic cast operation failed. |
| 52005 | The parameter received by the function is not valid. |
| 52006 | The requested resource was not located. |
| 52007 | The requested operation did not complete in time. |
| 52008 | An unexpected operating system error occurred. |
| 52009 | The requested resource has been marked for deletion and is rejecting new requests. |
| 52010 | The requested resource must be initialized before use. |
| 52011 | The operation has begun and will complete asynchronously. |
| 52012 | There is no more data available to read or no more space available in which to write. |
| 52013 | The name or handle requested has already been reserved by another client. |
| 52014 | The synchronization object was abandoned by the previous holder. |
| 52015 | The acquisition of the synchronization object failed. |
| 52016 | The thread was running when you attempted to start it (redundant state change). |
| 52017 | The operation you requested is redundant or invalid when the object is in this state. |
| 52018 | A hardware failure has occurred. The operation could not be completed as specified. |
| 52019 | The supplied buffer is too small. |
| 52020 | The requested resource has been removed. |
| 52021 | There is not enough power to complete the requested operation. |
| 52022 | IO processing is not active. |
| 52023 | No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified. |
| 52024 | An unknown or unexpected communication fault occurred while attempting to read data from or write data to a device. |
| 52025 | The operation was interrupted by a user mode signal. |
| 52026 | The operation could not be completed because the user does not have sufficient permissions. Consider running as an administrator. |
| 52027 | The specified string contains characters that cannot be interpreted due to the installed language support and system locale settings.
If possible, do not use this character. Otherwise, ensure that the appropriate language support is installed on the system, and that the system locale is set correctly. For most Windows operating systems, this is done through the Regional Settings option in the Control Panel. For LabVIEW RT targets, install Language Support for LabVIEW RT and change the locale setting for the remote system on the System Settings tab in MAX. |
| 52028 | The specified language is not supported. |
| 52029 | The specified format is not supported. |
| 52030 | The current application development environment is not supported. |
| 52031 | The specified resource is currently in use. |
| 380750 | The requested memory could not be allocated. |
| 380751 | The requested device, chassis, or controller is unknown to the PXI subsystem. |
| 380752 | An internal software error occurred. |
| 380753 | The PXI system description files are internally inconsistent. The PXI Resource Manager may be generating incorrect files. Use NI MAX to select the active PXI Resource Manager for the system. |
| 380754 | An internal software error occurred. |
| 380755 | An internal software error occurred. |
| 380756 | An internal software error occurred. |
| 380757 | The requested PXI information is not available. Verify that the PXI Resource Manager for the system is up to date. Use NI MAX to select the active PXI Resource Manager for the system. |
| 380758 | There is no PXI_Star connection for this slot because it is a PXI system timing slot. If the device supports PXI system timing controller functionality, use a numbered PXI_Star connection to access the system timing slot's PXI_Star lines, or move the device to another slot. |
| 380759 | This slot is not connected to the requested type of PXI trigger bus. To use this type of PXI trigger bus, move your device to another slot. |
| 380760 | An internal software error occurred. |
| 380761 | The PXISA trigger manager library for the PXI chassis was not found. Ensure the software for your PXI chassis is installed and up to date. |
| 380762 | Unable to verify that the PXI system information is up to date. |
| 380763 | The PXI system description files are locked by another process. This may be a temporary problem caused by another process accessing the files. Contact NI if the problem persists. |
| 380764 | The PXI system description files are present but inaccessible. This may be a temporary problem caused by another process accessing the files. Contact NI if the problem persists. |
| 380765 | An unexpected software error occurred. |
| 380766 | Unable to load the specified library. |