New Update : I was able to get the exact reason for the extended result code. Had to update the script as per the example script . All the steps seem to working except for the actual installation. Here is a snippet of my InstallUpdate() function (gets executed on passing the --action-install flag). As you can see I am trying to run a dpkg -i for some deb packages. On running the script locally with the following flags the below mentioned output is seen In short, the update takes place and upgrades the package from 0.0.5 -> 0.0.6. But while trying to run the same via Azure IoT Hub device updates the following logs are seen for script handler. As seen clearly, no logs are generated. What could be the possible reason for this? While trying to deploy an update which uses a script handler, the deployment fails with the ExtendedResultCode = 810549253 . As per the documentation , the equivalent unsigned hex (in this case, 30500005 ) should be of the format F FFFFFF where the first nibble is the Facility Code and the rest of the bits are the Error Code. Refer to the table below for available Facility Code values : In this case, the corresponding unsigned hex is 30500005 . As per the format, our Facility Code is coming as 3. Any ideas on how to debug the failure of this update?

Device Update for IoT Hub device failing when using script handler.

Sriyuta Srivastava 10

New Update :

I was able to get the exact reason for the extended result code. Had to update the script as per the

All the steps seem to working except for the actual installation. Here is a snippet of my InstallUpdate() function (gets executed on passing the --action-install flag).

User's image

As you can see I am trying to run a dpkg -i for some deb packages.

On running the script locally with the following flags the below mentioned output is seen User's image

In short, the update takes place and upgrades the package from 0.0.5 -> 0.0.6.

But while trying to run the same via Azure IoT Hub device updates the following logs are seen for script handler.

User's image

As seen clearly, no logs are generated. What could be the possible reason for this?

While trying to deploy an update which uses a script handler, the deployment fails with the ExtendedResultCode = 810549253.

User's image

As per the documentation, the equivalent unsigned hex (in this case, 30500005) should be of the format F FFFFFF where the first nibble is the Facility Code and the rest of the bits are the Error Code. Refer to the table below for available Facility Code values : User's image

In this case, the corresponding unsigned hex is 30500005. As per the format, our Facility Code is coming as 3.

Any ideas on how to debug the failure of this update?

AshokPeddakotla-MSFT 27,571 Reputation points

2023-07-20T15:24:55.84+00:00

Sriyuta Srivastava

Are you seeing this error for the first time?

Can you check the logs of the device that failed to deploy the update? The logs may provide more information about the specific error that occurred.

Check the script handler that you are using to deploy the update. If possible could you add more details about the script which you are trying?

Hari Prashanth 25

Im facing similar issue while trying to deploy an update which uses script handler. I get a description which says - Cannot parse the script result file '/var/lib/adu/downloads/d270d434-629d-4b08-b553-73f79c763380/action--action-download_aduc_result.json' along with Extended result code: 810549765.
SSH-ed into the IoT edge device and there was no such result file found in the path '/var/lib/adu/downloads/d270d434-629d-4b08-b553-73f79c763380/action--action-download_aduc_result.json'.

Given below are the contents of updatescript.sh file and systemupdate.importmanifest.json file.

updatescript.sh file

#!/bin/bash

# Update all system packages to the latest

sudo apt update -y 
sudo apt upgrade -y

systemupdate.importmanifest.json

{
  "compatibility": [
    {
      "manufacturer": "beelink",
      "model": "edgeappliance"
    }
  ],
  "createdDateTime": "2023-08-07T11:24:23Z",
  "description": "ubuntu update",
  "files": [
    {
      "filename": "updatescript.sh",
      "hashes": {
        "sha256": "petQB+fmawhdUvXM+rEnxR86syv0KoAVHz47ic7o220="
      },
      "sizeInBytes": 97
    }
  ],
  "instructions": {
    "steps": [
      {
        "handler": "microsoft/script:1",
		"files": [
          "updatescript.sh"
        ],
		"handlerProperties": {
			"scriptFileName": "updatescript.sh",
        },
        "type": "inline"
      }
    ]
  },
  "manifestVersion": "5.0",
  "updateId": {
    "name": "systemupdate",
    "provider": "Stratus",
    "version": "3.0"
  }
}

Sriyuta Srivastava 10 Reputation points

2023-08-10T07:21:59.7833333+00:00
@Hari Prashanth Took me sometime to get here but there are some points that you might seem helpful.

Your update script is wrong. IoT hub expects the script in a specific manner(Some functions and flags should be there by default you can add yours on top of it). Refer to example script to generate your script.

To understand the execution of the script on the device side please refer to the readme.MD . Not very descriptive but still give you basic idea of how the script is executed on the device side.

Now coming on to the actual issue that you are facing, that error code 810549765 which means ADUC_ERC_SCRIPT_HANDLER_INSTALL_FAILURE_PARSE_RESULT_FILE. You can find the extended results codes here .

The script gets called at different stages with different flags. The following are the flags that get called, in chronological order

--action-is-installed

--action-download

--action-install

--action-apply

--action-cancel, if needed

All of these flags are not passed at the same time. The script run again and again with different flags. At each stage a result file is generated, which decides the execution of the next step.

In your scenario, it is not able to find the download result file, action--action-download_aduc_result.json. Hence the error.

My advice is just fix your update script as per the example script and this particular error should be gone.

Last but not the least, try referring to the repo than the official documentation. It is easier to understand what is happening when you're looking at the actual code.
Sriyuta Srivastava 10 Reputation points

2023-08-10T12:40:21.25+00:00

Hi Ashok, I was able to get the exact reason for the extended result code. Had to update the script as per the

example script .

All the steps seem to working except for the actual installation. Here is a snippet of my InstallUpdate() function (gets executed on passing the --action-install flag).

As you can see I am trying to run a dpkg -i for some deb packages.

On running the script locally with the following flags the below mentioned output is seen

In short, the update takes place and upgrades the package from 0.0.5 -> 0.0.6.

But while trying to run the same via Azure IoT Hub device updates the following logs are seen for script handler.

As seen clearly, no logs are generated. What could be the possible reason for this?
LeelaRajeshSayana-MSFT 13,471 Reputation points

2023-08-15T12:54:07.3+00:00

Hi @Sriyuta Srivastava Apologies for the delay in getting back to you. I would like to check and confirm if this is still an ongoing issue. I request you to create a support ticket for further investigation and immediate assistance on this. Please let us know if you do not have a support plan. Thank you.
Sriyuta Srivastava 10 Reputation points

2023-08-17T11:42:53.47+00:00

Hi @LeelaRajeshSayana-MSFT , this is still an ongoing issue. I have searching through the portal multiple times, all I ever get to is the diagnostics. Can you please help me with the steps to raise a ticket for the same?
LeelaRajeshSayana-MSFT 13,471 Reputation points

2023-08-17T20:49:18.5166667+00:00

Hi @Sriyuta Srivastava For a deeper investigation and immediate assistance on this issue, please file a support request @ https://aka.ms/azsupt? If you do not have access to a support plan, could you please send an email to azcommunity@microsoft.com with the below details, so that we can work closely on this matter.

Thread URL: Link to this thread.
Azure Subscription ID:
Email Subject : Attn Ashok