| title | description | author | ms.author | ms.date | ms.topic | ms.service |
|---|---|---|---|---|---|---|
Error codes for Device Update for Azure IoT Hub | Microsoft Docs |
This document provides a table of error codes for various Device Update components. |
chrisjlin |
lichris |
1/26/2022 |
reference |
iot-hub-device-update |
This document provides a table of error codes for various Device Update components. It's meant to be used as a reference for users who want to parse their own error codes to diagnose and troubleshoot issues.
There are two primary client-side components that may throw error codes: the Device Update agent, and the Delivery Optimization agent. Error codes also come from the Device Update content service.
The Device Update for IoT Hub Core PnP interface reports ResultCode and ExtendedResultCode, which can be used to diagnose failures. Learn More about the Device Update Core PnP interface.
ResultCode is a general status code and ExtendedResultCode is an integer with encoded error information.
You'll most likely see the ExtendedResultCode as a signed integer in the PnP interface. To decode the ExtendedResultCode, convert the signed integer to
unsigned hex. Only the first 4 bytes of the ExtendedResultCode are used and are of the form F FFFFFFF where the first nibble is the Facility Code and
the rest of the bits are the Error Code.
0 00 00000 Total 4 bytes (32 bits)
- -- -----
| | |
| | |
| | +--------- Error code (20 bits)
| |
| +------------- Component/Area code (8 bits)
|
+--------------- Facility code (4 bits)
Refer to Device Update Agent result codes and extended result codes or implement a custom Content Handler for details on parsing codes.
The following table lists error codes pertaining to the content service component of the Device Update service. The content service component is responsible for handling importing of update content. More troubleshooting information is also available for importing proxy updates.
| Error Code | String Error | Next steps |
|---|---|---|
| "UpdateAlreadyExists" | Update with the same identity already exists. | Make sure you're importing an update that hasn’t already been imported into this instance of Device Update for IoT Hub. |
| "DuplicateContentImport" | Identical content imported simultaneously multiple times. | Same as for UpdateAlreadyExists. |
| "CannotProcessImportManifest" | Error processing import manifest. | Refer to import concepts and import update documentation for proper import manifest formatting. |
| "CannotDownload" | Cannot download import manifest. | Check to make sure the URL for the import manifest file is still valid. |
| "CannotParse" | Cannot parse import manifest. | Check your import manifest for accuracy against the schema defined in the import update documentation. |
| "UnsupportedVersion" | Import manifest schema version is not supported. | Make sure your import manifest is using the latest schema defined in the import update documentation. |
| Error importing update due to exceeded limit. | Cannot import additional update provider. | You've reached a limit on the number of different Providers allowed in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
| Error importing update due to exceeded limit. | Cannot import additional update name for the specified provider. | You've reached a limit on the number of different Names allowed under one Provider in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
| Error importing update due to exceeded limit. | Cannot import additional update version for the specified provider and name. | You've reached a limit on the number of different Versions allowed under one Provider and Name in your instance of Device Update for IoT Hub. Delete some updates with that Name from your instance and try again. |
| Error importing update due to exceeded limit. | Cannot import additional update provider with the specified compatibility. | When defining compatibility properties in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given set of compatibility properties. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, make sure that all updates for a given device (as defined by compatibility properties) use the same Provider and Name. |
| Error importing update due to exceeded limit. | Cannot import additional update name with the specified compatibility. | When defining device compatibility properties in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given set of compatibility properties. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, make sure that all updates for a given device (as defined by compatibility properties) use the same Provider and Name. |
| Error importing update due to exceeded limit. | Cannot import additional update version with the specified compatibility. | When defining device compatibility properties in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given set of compatibility properties. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, make sure that all updates for a given device (as defined by compatibility properties) use the same Provider and Name. |
| "CannotProcessUpdateFile" | Error processing source file. | |
| "ContentFileCannotDownload" | Cannot download source file. | Check to make sure the URL for the update file(s) is still valid. |
| "SourceFileMalwareDetected" | A known malware signature was detected in a file being imported. | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. If a known malware signature is identified, the import will fail and a unique error message will be returned. The error message contains the description of the malware signature, and a file hash for each file where the signature was detected. You can use the file hash to find the exact file being flagged, and use the description of the malware signature to check that file for malware. Once you have removed the malware from any files being imported, you can start the import process again. |
| "SourceFilePendingMalwareAnalysis" | A signature was detected in a file being imported that may indicate malware is present. | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. The import will fail if a scan signature has characteristics of malware, even if there is not an exact match to known malware. When this occurs, a unique error message will be returned. The error message contains the description of the suspected malware signature, and a file hash for each file where the signature was detected. You can use the file hash to find the exact file being flagged, and use the description of the malware signature to check that file for malware. Once you've removed the malware from any files being imported, you can start the import process again. If you're certain your files are free of malware and continue to see this error, use the Contact Microsoft Support process. |