Integration runtimes are not auto-updating

Question

Our Azure Data Factory integration runtimes are not auto-updating even though we have them set to auto-update.

We checked the troubleshooting items listed, and none seem to apply.

• auto-update is turned on
• we are able to access the download center from the IR
• no error that the estimated upgrade date has passed
• the upgrade service is running
• we have .net version above 4.7.2
• we don't have a x86 machine
• we have enough drive space
• not sure how to check whether the IR credential has not synced, i assume it has as we have not received any error messages like that.

The auto-update is supposed to try daily at a certain time as far as I am aware. It is a quiet time for our data factory with usually no pipelines running, but the integration runtimes have not updated since June 2024.

Could anyone give any guidance as to why the auto-updates are not happening?

Thank you,

Jackie

Answer 1

Hi @phemanth We are still working on troubleshooting this. I've checked a few things but still trying to find/figure out the others.

1. IR credential sync: I am seeing our SHIRs as synced under Credential status.
2. Daily auto-update schedule: Yes, verified we have set the intended scheduled time.
3. Azure Data Factory version: I can't find that information in Azure Portal under Overview but if I click on the JSON code in Azure Portal for our Data Factory and search for version I see: "version": "2018-06-01", Would that mean we are running an old version? Does this get auto updated?
4. Firewall or network restrictions: We still need to check with our internal IT if these URLs are allowed and ports are open. https://*.azure.com, https://*.microsoft.com, and https://*.windows.net
5. Azure Data Factory logs: I'm not finding logs. Do I need to remote into our SHIRs and find logs there I assume?

Answer 2

@JB

Thanks for the update on the troubleshooting progress. I'll help clarify some of the points you've checked and provide guidance on the remaining ones.

IR credential sync: Good to hear that you've verified the SHIRs as synced under Credential status. This should not be the cause of the issue.

Daily auto-update schedule: You've confirmed that the schedule is set correctly, so this is unlikely to be the cause.

Azure Data Factory version: The version you found in the JSON code, "2018-06-01", refers to the API version of your Azure Data Factory instance. This is not the same as the version of the Azure Data Factory service itself. The API version is used to specify the version of the Azure Data Factory REST API that your instance is compatible with.

The Azure Data Factory service is automatically updated by Microsoft, and you don't need to worry about updating it manually. However, it's possible that your instance is not using the latest features or fixes if the API version is outdated.

To check the actual version of the Azure Data Factory service, you can follow these steps:

• Go to the Azure portal and navigate to your Azure Data Factory resource.
• Click on "Author & Monitor".
• Click on the three dots (ellipsis) next to the "Author & Monitor" button.
• Click on "About".
• Look for the "Version" information.

1. Firewall or network restrictions: It's great that you're working with your internal IT to verify the firewall and network settings. Please ensure that the necessary ports and URLs are allowed, as mentioned earlier.
2. Azure Data Factory logs: You don't need to remote into your SHIRs to find logs. Instead, you can check the Azure Monitor logs for your Azure Data Factory resource. To do this:

• Go to the Azure portal and navigate to your Azure Data Factory resource.
• Click on "Monitor".
• Click on "Logs".
• Select the log category and time range you're interested in.
• Look for any errors or warnings related to the auto-update process.

Additionally, you may want to consider checking the Azure Data Factory resource's activity log, as I mentioned earlier, to see if there are any errors or warnings related to the integration runtime