This section outlines error codes returned from the E-FOTA Advanced device client.
Success codes
| Error code | Description |
| 0 | Success. |
| 900 | The item was downloaded and installed successfully. |
| 956 | The license was retrieved successfully. |
| -1251 | Installation and post-update verification passed successfully. |
Download result codes
| Error code | Description |
| 901 |
Insufficient free space on the device. File can't be downloaded on to the device. |
| 902 |
The device user rejected the download file. |
| 903 | A network problem occurred during download. |
| 905 | The file doesn't match the description in the deployment descriptor. |
| 906 | The deployment descriptor was unreadable. |
| 907 | The target device doesn't support the file. |
| 951 | The file version specified on the DDVersion field in the deployment descriptor isn't compatible with the selected device. |
| 952 | There was a device error while downloading or installing an item. |
| 953 | The device can't use the file . This error code is sent after the file is downloaded but before it is installed. |
| 954 | The item is unavailable at the URL specified by the deployment descriptor. |
| 955 | The download was canceled because the file has been updated. |
| 957 | The license wasn't retrieved successfully. |
| 958 | The specified version is already on the device. |
| 959 | The device doesn't have the requirements to use the file. |
| 960 |
Indicates that the status according to the specific environment returned by the content handler. Another status will follow with the internal status code. |
| 970 | Different statuses for the file. Additional statuses will be returned for each file. |
| -1401 |
The device user rejected the download file. This result code can be returned before or after the download. |
| -2401 | The device user has canceled the download for the firmware update package. |
| -6214 | The device user has canceled the alert. |
Device error
| Error code | Description |
| -1 |
At least one of the selected device models doesn't exist. |
| -4 |
Device list is empty. |
| -34 |
Protocol version provided by the client isn't supported by the Knox E-FOTA Advanced portal. |
| -1400 | A client error occurred due to user or device behavior. |
| -1404 | The download failed due to insufficient memory. |
| -1406 | There was insufficient memory for the software installation. |
| -1448 | The transaction was aborted; other services are running. |
| -1449 | The transaction was aborted; the device is roaming. |
| -1451 | Not attempted due to update file version mismatch or lack of available storage. The software update was skipped due to previous errors. |
|
-1460 |
The install profile on the device operation failed. |
| -1461 | Setting details are invalid. |
| -1462 | Custom setting isn't supported on the device. |
| -1463 | Device wasn't found. |
| -2400 | The firmware update failed due to a device error. |
| -2501 |
There is insufficient memory to download the firmware update package. See the knowledge base article on how to troubleshoot this error. |
| -2502 | There is insufficient memory to install the firmware update. |
| -5300 | The device ready path doesn't exist. The device isn't ready for this operation. |
| -5330 | The inventory path doesn't exist. The update installer isn't installed and enabled. |
| -5334 | There was a general device error. |
| -5400 | The device isn't ready for the update. |
| -6215 | The end-user aborted or canceled the operation. The operation wasn't performed. |
|
-6216 |
The command was inside an atomic element and the atomic element failed; the command was successfully rolled back. |
| -6403 | The command was not found. |
| -6404 | The node was not found. |
| -6405 | The command isn't allowed. |
| -6406 | The alert isn't supported on the device. |
| -6416 | The client can't display the alert because of a limitation. For example, the choice list is too long. |
| -6500 | There was an undefined command error. The device couldn't perform the command for an unspecified reason. |
| -6516 | The command was inside an atomic element and the atomic element failed; the command was not successfully rolled back. The server should try to restore the device back to its original state. |
Server error
| Error code | Description |
| -11 |
A software instance wasn't specified, or doesn't exist. |
| -12 |
The latest software version doesn't exist. |
| -16 |
The specified trigger doesn't exist. |
| -25 |
No SCOMO URI defined for the device model. The device can't perform the operation without a defined SCOMO URI. |
| -26 |
The required configuration property wasn't found. |
| -27 |
At least one of the selected software versions isn't suitable for the selected device model. |
| -28 |
No suitable deployment package (DP) was found for the DP reader installed on the device. This error occurred when attempting to create the DP. The software is managed by the server but the existing version on the client isn't. In order to manage this device, the client version must be managed on the server. |
| -29 |
The deployment package doesn't exist. |
|
-30 |
The deployment package version is invalid. |
| -31 | The deployment package exceeds the maximum size allowed by the device model. |
| -32 | The deployment package encoding is not supported. The error occurred when attempting to create the deployment package. |
| -33 | The deployment package could not be signed. |
| -100 | Undefined internal error. |
| -101 | Unexpected error. |
| -454 | Invalid update package. |
| -1454 | Update package is invalid. |
| -1500 |
The update failed due to a server error. See the knowledge base article on how to troubleshoot this error. |
| -1501 | The update failed; the server is unavailable or isn't responding. |
| -1550 | The update failed; there was a server error with a vendor-specified result code. |
| -2409 |
The firmware update failed due to an unexpected error. See the knowledge base article on how to troubleshoot this error. |
| -2550 | The installation of the firmware update failed due to an unexpected error. |
Update file error
| Error code | Description |
| -7 |
A software version wasn't specified or doesn't exist. |
| -17 |
At least one of the selected updates doesn't exist. |
| -18 |
At least one of the required update files doesn't exist. |
| -19 |
The firmware version doesn't exist. |
| -1551 | Download URL has expired. |
Installation error
| Error code | Description |
| -20 |
At least one of the selected software versions is inactive. |
| -453 | Installation conditions response time out. |
| -1001 | iOS app failed to install to the target device. |
| -1002 | Operation failed to remove an iOS app from the target device. |
| -1405 |
The software installation failed. See the knowledge base article on how to troubleshoot this error. |
| -1407 |
Failed to validate the digital signature of the Delivery Package (DP). See the knowledge base article on how to troubleshoot this error. |
| -1408 | The software removal failed. |
| -1409 | The software activation failed. |
| -1410 | The software deactivation failed. |
| -1413 | The device doesn't support the required environment type for the software update. |
| -1447 | The transaction was aborted; another transaction is already in progress. |
| -1453 | Installation conditions response time out. |
| -1455 | Device ID or software version mismatch. |
| -1456 | The update file included on the applied storage is no longer valid. |
| -1458 | The update format is invalid or some of the files are missing. |
| -1470 | Failed to validate certificate of the delivery package or software component in delivery package. |
| -1471 | The certificate of the delivery package or software component in the delivery package expired. |
| -1472 | Installation succeeded; version rollback succeeded. |
| -1473 | Installation failed; version rollback succeeded. |
| -1474 | Installation succeeded or partially succeeded; version rollback failed. |
| -1475 | Installation failed or partially succeeded; version rollback failed . |
| -1476 | Post-update verification failed; version rollback succeeded. |
| -1477 | Post-update verification failed; version rollback failed. |
| -1478 | Post-update verification failed; version rollback failed due to missing source version file or the file is not accessible. |
| -1479 | Installation failed or partially succeeded; version rollback failed due to missing source file or the file is not accessible. |
| -1480 | Installation succeeded, version rollback failed due to source version file issue. |
| -1482 | Installation not attempted. Update file version didn't match or there is a lack of available storage. |
| -2402 | The firmware update package is corrupt. |
| -2403 | The firmware update package is for a different device model. |
| -2404 | Failed to validate the firmware update package signature. |
| -2405 | The update package is not acceptable. |
| -2408 | FUMO is not implemented on the device. |
| -2410 | The firmware update failed due to an installation error. |
Network error
| Error code | Description |
| 503 | There was a network problem while downloading the file. |
| -1402 |
The software download failed. See the knowledge base article on how to troubleshoot this error. |
| -1403 | An authentication failure occurred during the software download. |
| 1465 | Validation of additional profile data on the device failed. |
| -2406 | There was a Device Management (DM) session authentication failure. |
| -2407 | There was a DM session time out. |
| -2411 | The server URL is invalid or malformed. |
| -2412 | The server is unavailable. |
| -2500 | There was a server error during the download. |
| -5000 | There was a DM server error. |
Time out error
| Error code | Description |
| -450 | The device user's response has timed out. |
| -600 | Waiting for a report from a device. |
| -1450 |
Device user's response has timed out. See the knowledge base article on how to troubleshoot this error. |
| 1464 | A timeout occurred when updating a device configuration. |
| -6408 | The device user's response has timed out. |
Operation error
| Error code | Description |
| 0 | Operation successfully completed. |
| -7001 |
Operation canceled; a new request is being performed. See the knowledge base article on how to troubleshoot this error. |
| -7002 | Invalid operation; the grant request was rejected. The device isn't ready. |
| -7003 |
Operation not performed: The device already has the latest software update. See the knowledge base article on how to troubleshoot this error. |
| -7004 |
Invalid operation; campaign timed out. See the knowledge base article on how to troubleshoot this error. |
| -7005 |
Operation aborted; the operation was rejected by the user during download. See the knowledge base article on how to troubleshoot this error. |
| -7006 | Operation failed. |
| -7007 |
Operation partially successful and the device was partially updated. Client error code sent: -1200 and -1463 Server error code sent: -7007 |
| -7008 | Operation not permitted; the device is locked. |
| -7015 | Operation failed; part of the software installation was not attempted. |
| -7017 |
Installation not attempted; a device problem occurred. File version mismatch or insufficient storage detected. See the knowledge base article on how to troubleshoot this error. |
| -7018 | Partial update complete; part of the software installation was not attempted. |
| -7020 |
The device report is pending; report not received from the device. See the knowledge base article on how to troubleshoot this error. |
| -7021 | Operation failed; missing parameters detected on the device. |
| -7027 |
Operation canceled; an urgent server initiated operation has been prioritized. For example:
|
| -7031 | The tool version report is missing from the device. |
| -7032 |
An update file corresponding to the tool version is missing. See the knowledge base article on how to troubleshoot this error. |
| -7033 | The tool version report is missing a rollback update file from the device. |
| -7034 | Failed to upload the data to the data collector microservice. |
| -7035 | At least one software component doesn't support rollback. |
| -7036 | The E-FOTA client version isn't supported by the server. |
| -7037 | Failed to match the update files returned by the plugin. |
| -7044 | Attribute not found. The server needs to resolve an attribute. |
| -7046 | Data package can't be uploaded. The size exceeds the daily service limit. |
| -7047 | Incorrect signatures returned by the signing plugin. |
| -7048 | The external server response exceeded the maximum length. |
| -7049 | The device returned additional information that exceeded the maximum length. |
