Skip to content

Commit 095d35e

Browse files
authored
Merge pull request #195252 from andrewbrownmsft/andbrown041522
Fixing table width issue
2 parents e80d4a4 + f30ab38 commit 095d35e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot-hub-device-update/device-update-error-codes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,8 +56,8 @@ The following table lists error codes pertaining to the content service componen
5656
| "UpdateName" | Cannot import a new update name for the specified provider. | You have reached a [limit](device-update-limits.md) 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. |
5757
| "UpdateVersion" | Cannot import a new update version for the specified provider and name. | You have reached a [limit](device-update-limits.md) 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. |
5858
| "UpdateProviderCompatibility" | Cannot import additional update provider with the specified compatibility. | When defining device manufacturer and device model 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 manufacturer/model. This means if you try to use the same manufacturer/model compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by manufacturer/model) use the same Provider and Name. While not required, you may want to consider making the Provider the same as the manufacturer and the Name the same as the model, just for simplicity. |
59-
| "UpdateNameCompatibility" | Cannot import additional update name with the specified compatibility. | Same as for UpdateProviderCompatibility.ContentLimitNamespaceCompatibility. |
60-
| "UpdateVersionCompatibility" | Cannot import additional update version with the specified compatibility. | Same as for UpdateProviderCompatibility.ContentLimitNamespaceCompatibility. |
59+
| "UpdateNameCompatibility" | Cannot import additional update name with the specified compatibility. | When defining device manufacturer and device model 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 manufacturer/model. This means if you try to use the same manufacturer/model compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by manufacturer/model) use the same Provider and Name. While not required, you may want to consider making the Provider the same as the manufacturer and the Name the same as the model, just for simplicity. |
60+
| "UpdateVersionCompatibility" | Cannot import additional update version with the specified compatibility. | When defining device manufacturer and device model 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 manufacturer/model. This means if you try to use the same manufacturer/model compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by manufacturer/model) use the same Provider and Name. While not required, you may want to consider making the Provider the same as the manufacturer and the Name the same as the model, just for simplicity. |
6161
| "CannotProcessUpdateFile" | Error processing source file. | |
6262
| "ContentFileCannotDownload" | Cannot download source file. | Check to make sure the URL for the update file(s) is still valid. |
6363
| "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. <br><br>Once you have removed the malware from any files being imported, you can start the import process again. |

0 commit comments

Comments
 (0)