DocsICP FilingConsole
官方文档
首页

Error codes received by devices

更新时间：
复制 MD 格式
产品详情
我的收藏

This topic describes the error codes that IoT Platform may return to devices.

Common error codes

Table 1. General common error codes

Error code

Cause

Solution

400

The system failed to process the request.

Submit a ticket.

429

The request frequency is too high and has triggered throttling.

Submit a ticket.

460

The data reported by the device is empty, the parameter format is invalid, or the number of parameters exceeds the limit.

Check the parameter information against the data format specified in the Alink protocol documentation.

500

An unknown system error occurred.

Submit a ticket.

5005

The system failed to query the product information.

In the IoT Platform console, query the product information and verify the ProductKey.

5244

The system failed to query the metadata of a LoRaWAN product.

Submit a ticket.

6100

The specified device information was not found.

In the IoT Platform console, check the device information in the device management module.

6203

The system failed to parse the topic.

Submit a ticket.

6250

The system failed to query the product information.

In the IoT Platform console, query the product information and verify the ProductKey.

6204

The device is disabled. You cannot perform operations on the device.

In the IoT Platform console, check the device status in the device management module.

6450

After being parsed by a script into the standard Alink format, the custom or pass-through data does not contain the method parameter.

In Simple Log Service in the IoT Platform console or in the on-premises device logs, check whether the data reported by the device contains the method parameter.

6760

A system error occurred.

Submit a ticket.

Table 2. Common data parsing error codes

Error code

Cause

Troubleshooting

26001

The script content is empty when the system attempts to parse data.

In the IoT Platform console, go to the Data Parsing tab for the product and confirm that the script is submitted.

Note

Scripts that are not submitted cannot be called.

26002

The script runs, but the content is invalid. For example, the script may have a syntax error.

Test the script with the same data. View the specific error message and modify the script. We recommend that you test the script in detail on your on-premises server before you submit it to IoT Platform.

26006

The script runs, but the content is invalid. The script must contain the protocolToRawData and rawDataToProtocol services. An error is reported if one of the services is missing.

In the IoT Platform console, go to the Data Parsing tab for the product and check whether the script contains the protocolToRawData and rawDataToProtocol services.

26007

The script runs, but the returned result is in an invalid format. The script must contain the protocolToRawData and rawDataToProtocol services. The protocolToRawData service must return a byte[] array, and the rawDataToProtocol service must return a JSON object. This error is reported if the returned result is not in the required format.

Test the script in the IoT Platform console or on your on-premises server and check whether the format of the returned result is valid.

26010

The request frequency is too high and has triggered throttling.

Submit a ticket.

Table 3. Common TSL error codes

Error code

Cause

Troubleshooting

5159

The system failed to query the property definition during Thing Specification Language (TSL) verification.

Submit a ticket.

5160

The system failed to query the event definition during TSL verification.

Submit a ticket.

5161

The system failed to query the service definition during TSL verification.

Submit a ticket.

6207

The data reported by the device in the Alink format, or the data returned after the script is parsed, is not in the JSON format.

For more information about the data format, see Device properties, events, and services. Report data in the required format.

6300

The method parameter does not exist. During TSL verification, the data reported by the device in the standard Alink format, or the custom or pass-through data converted by a script, does not contain the method parameter required by the Alink protocol.

In Simple Log Service in the IoT Platform console or in the on-premises device logs, check whether the reported data contains the method parameter.

6301

During TSL verification, the system found that the data is defined as an array, but the reported data is not an array.

In the IoT Platform console, go to the Feature Definition tab for the product, view the data format in the product's TSL, and then report data in the required format.

6302

During TSL verification for service request parameters, the system found that a required parameter is missing.

In the IoT Platform console, view the feature definitions for the product to which the device belongs, query the request parameters of the service, and then check the input parameters.

6306

During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The value of the input parameter is outside the range specified in the feature definition.

In the IoT Platform console, view the feature definitions for the product to which the device belongs and check the data type and value range of the input parameter.

6307

The input parameter does not comply with the specifications for 32-bit floating-point numbers in the TSL. During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The value of the input parameter is outside the range specified in the feature definition.

6308

The input parameter does not comply with the specifications for Boolean data in the TSL. During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The value of the input parameter is outside the range specified in the feature definition.

6310

The input parameter does not comply with the specifications for character data in the TSL. During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The length of the character parameter exceeds the limit.

6322

The input parameter does not comply with the specifications for 64-bit floating-point numbers in the TSL. During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The value of the input parameter is outside the range specified in the feature definition.

6304

During TSL verification, the system found that the input parameter does not exist in the struct.

In the IoT Platform console, view the feature definitions for the product to which the device belongs and check the data type of the input parameter.

6309

The input parameter does not comply with the specifications for enumeration data in the TSL.

6311

The input parameter does not comply with the specifications for date data in the TSL. During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The character type is not in the UTC timestamp character format.

6312

The input parameter does not comply with the specifications for struct data in the TSL. During TSL verification, the system found that:

  • The data type of the input parameter is inconsistent with the data type defined in the TSL.

  • The number of parameters in the struct is inconsistent with the number defined in the TSL.

6320

The device's property information cannot be found when the system queries the device's TSL.

In the IoT Platform console, check whether the property exists in the feature definitions for the product to which the device belongs. If the property does not exist, you must add a property definition.

6321

During TSL parsing, the system found that the identifier of a property, event, or service is empty.

Submit a ticket.

6317

During TSL verification, the system found that key information, such as type, is missing from the TSL, or the specs parameter is empty.

Submit a ticket.

6324

The array parameter is invalid. During TSL verification, the system found that:

  • The array parameter does not comply with the TSL definition.

  • The number of elements in the array exceeds the maximum number defined in the TSL.

  • In the IoT Platform console, go to the product page to view the feature definitions for the product to which the device belongs. Check the definition of the array.

  • View the logs reported by the device to check the number of elements in the array of the reported data.

6325

The array parameter contains an unsupported element type. The elements in an array can be of the integer, 32-bit floating-point, 64-bit floating-point, string, or struct type.

Check whether the element type of the input array is supported.

6326

An error occurred when the system checked the format of the time field in the reported data during TSL verification.

For more information about the data format, see Device properties, events, and services. Report data in the required format.

6328

TSL verification failed because the input parameter is not an array.

In the IoT Platform console, view the feature definitions for the device's product and ensure that the input parameter is an array.

6318

TSL parsing failed due to a system error.

Submit a ticket.

6313

6329

6323

6316

6314

6301

Error codes related to device connection using a Link SDK

  • If a device that uses the open source Paho MQTT library disconnects from IoT Platform, you can view the error logs and error codes related to the MQTT disconnection. For more information, see Error codes.

  • Error codes may be returned to a device that uses a Java Link SDK to connect to IoT Platform. For more information, see Error codes.

Error codes related to device identity registration

  • Identity registration for a directly connected device

    • Request topic: /sys/${productKey}/${deviceName}/thing/sub/register

    • Response topic: /sys/${productKey}/${deviceName}/thing/sub/register_reply

    Error codes: 460, 5005, 5244, 500, 6288, 6100, 6619, 6292, and 6203

    The following table describes the error codes that are specific to this operation. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6288

    Dynamic device registration is disabled.

    In the IoT Platform console, go to the product page of the product to which the device belongs and enable dynamic device registration.

    6619

    The device is attached to another gateway.

    In the IoT Platform console, go to the product page of the sub-device and check whether the device is attached to a gateway.

  • Dynamic registration of a directly connected device (one-type-one-secret)

    Error codes: 460, 6250, 6288, 6600, 6289, 500, and 6292

    The following table describes the error codes that are specific to this operation. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6288

    Dynamic device registration is disabled.

    In the IoT Platform console, go to the product page for the product to which the device belongs and enable dynamic device registration.

    6292

    The signature method is not supported.

    Use a signature method that is supported by the signMethod parameter. For more information, see Device identity registration.

    6600

    Signature verification failed.

    Calculate the signature using the signing method in Device identity registration, and then verify the signature.

    6289

    The device is already activated when you attempt to dynamically register the directly connected device (one-type-one-secret).

    In the IoT Platform console, check the device status in the device management module.

Error codes related to device topology

  • Add a device topology

    • Request topic: /sys/${productKey}/${deviceName}/thing/topo/add
    • Response topic: /sys/${productKey}/${deviceName}/thing/topo/add_reply

    Error codes: 460, 429, 6402, 6100, 401, 6204, 6400, and 6203

    The following table describes the error codes that are specific to adding a device topology. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    401

    Failed to verify the signature when you add a topology.

    Calculate and verify the signature based on the signature method. For more information, see Manage topologies.

    6402

    The gateway and the sub-device are the same device. You cannot add the current gateway as a sub-device to itself.

    Verify that the information for the added sub-device is the same as the gateway information.

    6400

    The number of sub-devices added to the gateway exceeds the limit.

    For more information about the limits, see Limits. In the IoT Platform console, go to the Sub-devices tab for the gateway to view the number of existing sub-devices.

  • Delete a topology

    • Request topic: /sys/${productKey}/${deviceName}/thing/topo/delete
    • Response topic: /sys/${productKey}/${deviceName}/thing/topo/delete_reply.

    Error codes: 460, 429, 6100, 6401, and 6203

    The following table describes the error codes that are specific to deleting a device topology. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6401

    The topology does not exist.

    In the IoT Platform console, go to the Device Details page of the gateway in the Devices module and click the Sub-devices tab to view the sub-device information.

  • Retrieve a topology

    • Request topic: /sys/${productKey}/${deviceName}/thing/topo/get
    • Response topic: /sys/${productKey}/${deviceName}/thing/topo/get_reply

    Error codes: 460, 429, 500, and 6203

    For information about the error codes, see the "Common error codes" section in this topic.

  • Gateway reports discovered sub-devices

    • Request topic: /sys/${productKey}/${deviceName}/thing/list/found
    • Response topic: /sys/${productKey}/${deviceName}/thing/list/found_reply

    Error codes: 460, 500, 6250, 6280, and 6203

    The following table describes the specific error codes. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6280

    The name of the sub-device reported by the gateway is invalid. A device name can contain Chinese characters, letters, digits, and underscores (_). It must be 4 to 32 characters in length. A Chinese character is counted as two characters.

    Check whether the reported device name is valid.

Error codes related to sub-device online and offline status

  • Sub-device goes online

    Topic to which the gateway subscribes to receive messages: /ext/session/${productKey}/${deviceName}/combine/login_reply

    Error codes: 460, 429, 6100, 6204, 6287, 6401, 500, 9241, and 9240

  • Error during voluntary sub-device offline event

    Topic to which the gateway subscribes to receive messages: /ext/session/${productKey}/${deviceName}/combine/logout_reply

    Error codes: 460, 520, and 500

  • Forced sub-device offline event

    Topic to which the gateway subscribes to receive messages: /ext/error/${productKey}/${deviceName}

    Error codes: 427, 521, 522, and 6401

  • Failed to send a message from a sub-device

    Topic to which the gateway subscribes to receive messages: /ext/error/${productKey}/${deviceName}

    Error code: 520

  • The gateway failed to report messages from sub-devices in a batch using the proxy feature

    Topic to which the gateway subscribes to receive messages: /sys/${productKey}/${deviceName}/proxy/batch_post_reply

    Error code: 9242

The following table describes the error codes that are specific to sub-device online and offline events. For information about other error codes, see the "Common error codes" section in this topic.

Error code

Cause

Troubleshooting

427

The device is forced to go offline because the device certificate is used by another device.

IoT Platform identifies a device only based on the device certificate (ProductKey, DeviceName, and DeviceSecret).

  • The same device certificate is burned on multiple devices.

  • The network or power supply of the device is unstable. The device immediately reconnects to IoT Platform after an instantaneous network outage or power failure. In this case, IoT Platform identifies the reconnected device as a new device. Even if an error message is returned, the device can work as expected.

  • Go to the Device Details page in the console and check the time when the device was last connected to IoT Platform. You can determine whether the same device certificate information is used to connect another device to IoT Platform.

  • Check whether the network environment is stable by using one of the following methods:

428

The number of sub-devices under a single gateway exceeds the limit.

For more information about the limits, see Gateways and sub-devices.

Check the number of sub-devices under the gateway.

521

The device is deleted.

In the IoT Platform console, search for the device on the Devices page and confirm whether the device was deleted.

522

The device is disabled.

In the IoT Platform console, check the device status on the Devices page.

520

A sub-device session error occurred.

  • The sub-device session does not exist. The sub-device may not be online or may have already gone offline.

  • The sub-device session is online, but the sub-device did not go online through the current gateway session.

6287

The system failed to verify the signature based on the product or device key.

Calculate and verify the signature based on the signature method. For more information, see Sub-device online and offline status.

1914

The number of sub-devices in a single batch online or offline request exceeds the limit of 5.

Check whether the number of sub-devices in the batch online or offline request exceeds the threshold.

1913

The sub-device was automatically taken offline by the cloud because the gateway went offline.

Query Simple Log Service to find the cause of the gateway going offline.

9242

The number of messages that a gateway reports from sub-devices in a batch using the proxy feature exceeds the limit of 50.

Check whether the number of messages reported from sub-devices in a batch exceeds the threshold.

9241

In a request to bring sub-devices online using the gateway's proxy feature, the connection type of an online device cannot be modified.

For more information about connection types, see the conntype parameter in Direct connection of an ApsaraMQ for MQTT client.

Check whether the gateway and sub-devices are online.

9240

In a batch online or offline request, the number of sub-devices under the gateway exceeds the limit of 10,000.

Check whether the number of sub-devices in the batch online or offline request exceeds the threshold.

Error codes related to device properties, events, and services

  • Device reports properties

    • Pass-through data format:

      • Request topic: /sys/${productKey}/${deviceName}/thing/model/up_raw

      • Response topic: /sys/${productKey}/${deviceName}/thing/model/up_raw_reply

    • Alink data format:

      • Request topic: /sys/${productKey}/${deviceName}/thing/event/property/post

      • Response topic: /sys/${productKey}/${deviceName}/thing/event/property/post_reply

    Error codes: 460, 500, 6250, 6203, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, 6325, 6200, 6201, 26001, 26002, 26006, and 26007

    The following table describes the error codes that are specific to this operation. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6106

    Too many properties are reported. A device can report a maximum of 200 valid properties at a time.

    In the IoT Platform console, choose O&M > Simple Log Service, or in the on-premises device logs, check the number of reported properties.

  • Device reports events

    • Pass-through data format:

      • Request topic: /sys/${productKey}/${deviceName}/thing/model/up_raw

      • Response topic: /sys/${productKey}/${deviceName}/thing/model/up_raw_reply

    • Alink data format:

      • Default module

        • Request topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.event.identifier}/post

        • Response topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.event.identifier}/post_reply

      • Custom module:

        • Request topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.functionBlockId}:${tsl.event.identifier}/post

        • Response topic: /sys/${productKey}/${deviceName}/thing/event/${tsl.functionBlockId}:${tsl.event.identifier}/post_reply

    Error codes: 460, 500, 6250, 6203, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, 6325, 6200, 6201, 26001, 26002, 26006, and 26007

    For information about the error codes, see the "Common error codes" section in this topic.

  • Gateway reports data from sub-devices in a batch

    • Pass-through data format:

      • Request topic: /sys/${productKey}/${deviceName}/thing/model/up_raw

      • Response topic: /sys/${productKey}/${deviceName}/thing/model/up_raw_reply

    • Alink data format:

      • Request topic: /sys/${productKey}/${deviceName}/thing/event/property/pack/post

      • Response topic: /sys/${productKey}/${deviceName}/thing/event/property/pack/post_reply

    Error codes: 460, 6401, 6106, 6357, 6356, 6100, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, 6325, 6200, 6201, 26001, 26002, 26006, and 26007

    The following table describes the error codes that are specific to this operation. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6401

    The topology does not exist.

    In the IoT Platform console, go to the Sub-devices tab for the gateway to confirm the sub-device information.

    6106

    Too many properties are reported. A device can report a maximum of 200 valid properties at a time.

    In the IoT Platform console, choose O&M > Simple Log Service, or in the on-premises device logs, check the number of reported properties.

    6357

    Too much sub-device data is reported. When a gateway reports data on behalf of sub-devices, the data for a maximum of 20 sub-devices can be reported at a time.

    View the reported data in the on-premises device logs.

    6356

    Too many events are reported. When a gateway reports data on behalf of sub-devices, a maximum of 200 events can be reported at a time.

    View the reported data in the on-premises device logs.

Error codes related to desired property values of devices

  • Device retrieves desired property values

    • Request topic: /sys/${productKey}/${deviceName}/thing/property/desired/get
    • Response topic: /sys/${productKey}/${deviceName}/thing/property/desired/get_reply

    Error codes: 460, 6104, 6661, and 500

    The following table describes the error codes that are specific to this operation. For information about other error codes, see the "Common error codes" section in this topic.

    Error code

    Cause

    Troubleshooting

    6104

    The request contains too many properties. A request can contain a maximum of 200 properties.

    In the IoT Platform console, choose O&M > Simple Log Service, or in the on-premises device logs, check the number of properties in the reported data.

    6661

    Failed to query the desired properties. A system error occurred.

    Submit a ticket for troubleshooting.

  • Device deletes desired property values

    • Request topic: /sys/${productKey}/${deviceName}/thing/property/desired/delete
    • Response topic: /sys/${productKey}/${deviceName}/thing/property/desired/delete_reply

    Error codes: 460, 6104, 6661, 500, 6207, 6313, 6300, 6320, 6321, 6326, 6301, 6302, 6317, 6323, 6316, 6306, 6307, 6322, 6308, 6309, 6310, 6311, 6312, 6324, 6328, and 6325

Error codes related to device tags

  • Device reports tag information

    • Request topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/update
    • Response topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/update_reply

    Error codes: 460 and 6100

  • Device deletes tag information

    • Request topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/delete
    • Response topic: /sys/${productKey}/${deviceName}/thing/deviceinfo/delete_reply

    Error codes: 460 and 500

Error codes related to obtaining TSL templates

  • Request topic: /sys/${productKey}/${deviceName}/thing/dsltemplate/get

  • Response topic: /sys/${productKey}/${deviceName}/thing/dsltemplate/get_reply

Error codes: 460, 5159, 5160, and 5161

Error codes related to device requests for update packages

  • Request topic: /sys/${productKey}/${deviceName}/thing/ota/firmware/get

  • Response topic: /sys/${productKey}/${deviceName}/thing/ota/firmware/get_reply

Error codes: 429, 9112, and 500

The following table describes the error codes that are specific to device requests for update packages. For information about other error codes, see the "Common error codes" section in this topic.

Error code

Cause

Troubleshooting

9112

The specified device information cannot be found.

In the IoT Platform console, confirm that the device information is correct in the device management module.

Error codes related to device requests for configuration information

  • Request topic: /sys/${productKey}/${deviceName}/thing/config/get
  • Response topic: /sys/${productKey}/${deviceName}/thing/config/get_reply

Error codes: 460, 500, 6713, and 6710

The following table describes the error codes that are specific to device requests for configuration information. For information about other error codes, see the "Common error codes" section in this topic.

Error code

Cause

Troubleshooting

6713

The Remote Configuration service is unavailable. The remote configuration switch for the product is turned off.

In the IoT Platform console, choose O&M > Remote Configuration and turn on the remote configuration switch for the product.

6710

The remote configuration information cannot be found.

In the IoT Platform console, choose O&M > Remote Configuration and check whether a remote configuration file is edited for the product.

Error codes related to custom device jobs

  • Device retrieves the details of a custom job

    • Request topic: /sys/${productKey}/${deviceName}/thing/job/get.

    • Response topic: /sys/${productKey}/${deviceName}/thing/job/get_reply.

    Error codes: 71012, 71034, and 71035

  • Device update tasks: Job status

    • Request topic: /sys/${productKey}/${deviceName}/thing/job/update.

    • Response topic: /sys/${productKey}/${deviceName}/thing/job/update_reply.

    Error codes: 71018, 71019, 71034, and 71035

Error code

Cause

Troubleshooting

71012

The data format of the request to retrieve job details is not JSON.

View the correct data format and report the request in the required format. For more information, see Obtain the details of a device job.

71018

The job is in one of the following states:

  • Completed

  • Timed out

  • Canceling

  • Canceled

  • Deleting

In the IoT Platform console, choose Devices > Jobs and confirm the status of the destination job in the job list.

71019

The task ID in the job does not exist.

In the IoT Platform console, choose Devices > Jobs. On the page that appears, go to the Job Details > Task Overview tab for the destination job and confirm whether the task ID exists.

71034

The job ID of the task does not match the current device.

In the IoT Platform console, choose Devices > Jobs. On the page that appears, go to the Job Details > Task Overview tab for the destination job and confirm whether the current device contains the task ID.

71035

  • When the device retrieves the job details, the job ID in the request data is not the ID of a custom job.

  • The task in the job is in a final state, such as:

    • REMOVED

    • TIMED_OUT: The operation timed out.

    • FAILED

    • SUCCEEDED: Successful

    • CANCELLED: Canceled

    • Rejected

In the IoT Platform console, choose Devices > Jobs. On the page that appears, go to the Job Details page for the destination job:

  • On the Job Information tab, confirm whether the Job Type is Custom Job.

  • On the Task Overview tab, confirm the status of the destination task.

Error codes related to file uploads from devices

For more information about the data format and parameter descriptions for file uploads, see Upload files.

  • Device requests to upload a file

    • Request topic: /sys/${productKey}/${deviceName}/thing/file/upload/mqtt/init.
    • Response topic: /sys/${productKey}/${deviceName}/thing/file/upload/mqtt/init_reply.

    Error codes: 78117, 78123, 78124, and 78125

  • Device uploads a file shard

    • Request topic: /sys/${productKey}/${deviceName}/thing/file/upload/mqtt/send.
    • Response topic: /sys/${productKey}/${deviceName}/thing/file/upload/mqtt/send_reply.

    Error codes: 78118, 78119, 78120, 78121, 78122, 78124, 78125, and 78126

Error code

Cause

Troubleshooting

78117

The size of the file that the device requests to upload exceeds the 16 MB limit.

Confirm whether the size of the file to be uploaded meets the requirement.

78118

The size of the file shard that the device uploads exceeds the 128 KB limit.

Confirm whether the size of the file shard meets the requirement. For more information, see Upload files.

78120

The size of the file shard that the device uploads is smaller than the 256 B limit.

78119

When the device uploads a subsequent file shard, the value of the offset parameter is inconsistent with the size of the file that has already been uploaded to the IoT Platform cloud.

Confirm whether the value of the offset parameter is correct when the device uploads the file shard.

78121

When the device uploads a file shard, the integrity check for the current file shard fails.

Troubleshoot the cause based on the error message from the CRC algorithm check.

78122

The file upload task does not exist.

Confirm whether the ID of the file to be uploaded is correct or exists.

78123

A file with the same name already exists.

Confirm whether the file processing policy set on the device supports uploading files with the same name. For more information, see Upload files.

78124

The file upload task is complete.

Important

For a file that has already been uploaded, the device cannot upload file shards or cancel the file upload task.

Confirm whether the uploaded file exists in IoT Platform. For more information, see View files.

78125

File integrity check failed.

Confirm whether the file integrity check value calculated by the IoT Platform cloud is the same as the integrity check value provided by the device during the file upload.

78126

The device uploaded the same file shard in parallel.

Confirm that the device has received the response message for the current data shard before sending the next one.

Previous：NTP serviceNext：Communications