NI PXI Platform Software Error Code Family
Below are all of the Error Codes that belong to the NI PXI Platform Software Error Code Family (see Error List for list of Families).
| Code | Description |
|---|---|
| -313585 | Unable to read the ExpressCard8360 devices in the system |
| -313584 | Failed to write to the ExpressCard8360 EEPROM |
| -313583 | ExpressCard8360 EEPROM is invalid |
| -313582 | On PLX8505 MXI devices, not able to read back data that was written to EEPROM |
| -313581 | On PLX8505 MXI devices, read I2C ACK when not expected |
| -313580 | On PLX8505 MXI devices, did not read I2C ACK when expected |
| -313569 | Error returned from Windows Configuration Manager functions |
| -313568 | Found an unconfigured CardBus bridge |
| -313567 | The parent's reservation doesn't exist |
| -313566 | Requested reservation exists already |
| -313565 | Error reading or writing to the registry |
| -313564 | No bus numbers are available to enumerate PCI bridges and devices |
| -313563 | Ran out of bus numbers while enumerating PCI devices and bridges |
| -313562 | An invalid PCI tree configuration was detected |
| -313561 | Invalid hardware device or configuration |
| -313560 | A calculated resource exceeded the limits of the system or device |
| -313336 | Expected a bridge or device to be known, but could not find record of it |
| -313335 | The slotpaths do not belong to the same root bus. |
| -313334 | Unknown Error. |
| -313333 | Access Denied. |
| -313332 | This operation is not supported. |
| -313331 | The device model requested is not supported. |
| -313330 | The device category requested is not supported. |
| -313329 | An error occurred reading from the registry. |
| -313328 | An internal software error occurred. |
| -313327 | The system could not fulfill the file matching request. |
| -313326 | Not a valid file matching pattern. |
| -313325 | A provided parameter was invalid or ill-formatted. |
| -313324 | The requested device and function information is not known. |
| -313323 | The .ini file is not in the correct format. |
| -313322 | Could not find the specified item in the .ini file. |
| -313321 | Could not find the specified section in the .ini file. |
| -313320 | Could not read from file. |
| -313319 | Error writing to file. |
| -313318 | File is not open with writeable permissions. |
| -313317 | File is not open |
| -313316 | Error opening a file |
| -313315 | Not a valid filepath |
| -313314 | Out of memory |
| -313313 | An EEPROM transaction has timed out. |
| -313312 | Attempted to access EEPROM address above 32K. |
| -313311 | Attempted to fetch the value of a non-existing register value pair. |
| -313310 | Attempted to operate on an unloaded EEPROM map. |
| -313309 | The EEPROM configuration is invalid. Check the validation signature and bits of command status register. |
| -313308 | The checksum for the requested ACPI table is invalid. |
| -313307 | The requested ACPI table could not be found. |
| -313306 | The RSDP ACPI table could not be found. |
| -313305 | A request was made to read the SSDT ACPI table, which is not supported. |
| -313304 | The type header for the requested PCI device is invalid. |
| -313303 | An attempt to access the PCI Configuration Space failed because this access has been disabled. |
| -313302 | An attempt to access the PCI Configuration Space failed. |
| -313301 | A value read from the registry was not of the expected type. |
| -313300 | An attempt was made to set the maximum payload size on a PCI device that does not support it. |
| 313300 | The system could not fulfill the file matching request. |
| 313301 | An attempt was made to add a new device definition to the database, but that device is already known. |