Unable to load the specified library. An unexpected software error occurred. 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. 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. Unable to verify the PXI system information is up to date. 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. An internal software error occurred. 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. 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. 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. An internal software error occurred. An internal software error occurred. An internal software error occurred. 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. An internal software error occurred. The requested device, chassis, or controller is unknown to the PXI subsystem. The requested memory could not be allocated. The call should be retried. At least one of the PXI System Description files does not exist. Initialization completed using existing PXI system files. PXI System files were not regenerated due to a user setting. The PXI System has already been initialized. 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. The PXISA configuration file is currently locked and inaccessible. The NI PXI Resource Manager is not currently the active PXI resource manager for the system. The attribute is invalid. The handle is invalid. The NI PXI Resource Manager service is inaccessible, probably because it is either not running, or still starting up. A component recursively called into the PXI resource manager while it was initializing. A timeout occurred. An unspecified error occurred in the PXI subsystem. No handler is known for the specified data tree. Data requested is incompatible with the specified data type. File is internally inconsistent. Child not found. Attribute not found. Error reading or writing file. Error reading file. Error opening file. Invalid Parameter Conflict detected while renumbering a chassis. MXS PXI system not found PCI description string parse error Module parse error Peripheral Registration Parse Error Peripheral Driver Error Peripheral Driver Load Error The PXI system description file is invalid. Contact the vendor of your PXI resource manager software to resolve the issue. System description spec limitation System description write error System description parse error System description file not found Controller registration parse error Controller driver error Controller driver load error Controller parse error Controller type invalid Controller file not found Chassis Driver Not Found Chassis Registration Parse Error Chassis Driver Error Chassis Driver Load Error Chassis EEPROM Unrecognized Version Chassis EEPROM Invalid Chassis Hardware Not Found Chassis trigger parse error Chassis bridge parse error Chassis slot parse error Chassis segment parse error Chassis parse error Chassis bridge not found Chassis file not found The buffer is insufficient to hold the data requested. Error creating directory. Access Denied File path not found. File already exists. Error reading file. Error deleting file. Error copying file. File could not be closed. Error opening file. File not found. System not initialized Invalid configuration Allocation error The PXISA trigger manager for the chassis reports that the chassis has been disconnected. The PXISA trigger manager for the chassis reports that another application has already reserved the line. The PXISA trigger manager for the chassis reports that the destination of this route is already used by a different backplane route. The PXISA trigger manager for the chassis reports that there is a conflicting route, and the line could not be unreserved. The PXISA trigger manager for the chassis reports that the line is currently being used for a conflicting route. The PXISA trigger manager for the chassis reports that the line is already reserved by this application. 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. 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. The PXISA trigger manager for the chassis was called with an invalid parameter. The PXISA trigger manager for the chassis does not support the requested operation. The PXISA trigger manager for the chassis returned a vendor-specific or generic error. The PXISA trigger manager for the chassis returned a vendor-specific or generic error. The PXISA trigger manager for the chassis does not support the requested operation. The PXISA trigger manager for the chassis was called with an invalid parameter. 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. 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. The PXISA trigger manager for the chassis reports that the line is already reserved by this application. The PXISA trigger manager for the chassis reports that the line is currently being used for a conflicting route. The PXISA trigger manager for the chassis reports that there is a conflicting route, and the line could not be unreserved. The PXISA trigger manager for the chassis reports that the destination of this route is already used by a different backplane route. The PXISA trigger manager for the chassis reports that another application has already reserved the line. The PXISA trigger manager for the chassis reports that the chassis has been disconnected. Allocation error Invalid configuration System not initialized File not found. Error opening file. File could not be closed. Error copying file. Error deleting file. Error reading file. File already exists. File path not found. Access denied. Error creating directory. The buffer is insufficient to hold the data requested. Chassis file not found Chassis bridge not found Chassis parse error Chassis segment parse error Chassis slot parse error Chassis bridge parse error Chassis trigger parse error Controller file not found Controller type invalid Controller parse error Controller driver load error Controller driver error Controller registration parse error System description file not found System description parse error System description write error System description spec limitation The PXI system description file is invalid. Contact the vendor of your PXI resource manager software to resolve the issue. Peripheral Driver Load Error Peripheral Driver Error Peripheral Registration Parse Error Module parse error PCI description string parse error MXS PXI system not found Conflict detected while renumbering a chassis. Invalid Parameter Error opening file. Error reading file. Error reading or writing file. Attribute not found. Child not found. File is internally inconsistent. Data requested is incompatible with the specified data type. No handler is known for the specified data tree. An unspecified error occurred in the PXI subsystem. A timeout occurred. A component recursively called into the PXI resource manager while it was initializing. The NI PXI Resource Manager service is inaccessible, probably because it is either not running, or still starting up. The handle is invalid. The attribute is invalid. The NI PXI Resource Manager is not currently the active PXI resource manager for the system. The PXISA configuration file is currently locked and inaccessible. 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. The PXI System has already been initialized. Initialization completed using existing PXI system files. PXI System files were not regenerated due to a user setting. At least one of the PXI System Description files does not exist. The call should be retried. The requested memory could not be allocated. The requested device, chassis, or controller is unknown to the PXI subsystem. An internal software error occurred. 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. An internal software error occurred. An internal software error occurred. An internal software error occurred. 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. 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. 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. An internal software error occurred. 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. Unable to verify that the PXI system information is up to date. 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. 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. An unexpected software error occurred. Unable to load the specified library.