The Integration Runtime (Self-hosted) node has encountered an error during registration.

Eddy-6624 20 Reputation points
2024-05-08T14:39:03.7033333+00:00

I am not able to register Self Hosted Integration Runtime on my Machine. This is the error I am getting :

User's image

The Integration Runtime (Self-hosted) node has encountered an error during registration. Unable to determine the Integration Runtime (Self-hosted) node status. Confirm that the Integration Runtime (Self-hosted) Host Service is running, and a valid SSL certificate has been specified.


In the Logs I get this information :

Failed to get service token from ADF service with key IR@a68e529a-ae7a-724fff69aad6@xxxDataFactory@ServiceEndpoint=xxxdatafactory.eastus.datafactory.azure.net@****************** and time cost is: 3.8236143 seconds, the error code is: UnexpectedFault, activityId is: 40797b25-a932-4e79-86dd-ccbcd4d7cf7f and detailed error message is An error occurred while sending the request.
The underlying connection was closed: An unexpected error occurred on a send.
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
An existing connection was forcibly closed by the remote host
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
9,711 questions
{count} votes

Accepted answer
  1. Harishga 4,160 Reputation points Microsoft Vendor
    2024-05-09T06:40:48.0766667+00:00

    Hi @Eddy-6624
    Welcome to Microsoft Q&A platform and thanks for posting your question here.

    The error message you're seeing that there's an issue with the registration of a Self-hosted Integration Runtime node in Azure Data Factory. Here's how you can troubleshoot the problem:

    • Make sure that the Integration Runtime (Self-hosted) Host Service is running on your machine. You can do this by going to the Services application in Windows and looking for the Integration Runtime service. If it's not running, start the service.
    • Confirm that a valid SSL certificate has been specified for the Integration Runtime. The certificate must be a publicly trusted X509 v3 certificate, and each Integration Runtime node must trust this certificate. If the certificate is not valid, update it with a valid one.
    • If there’s a network firewall, make sure that the necessary rules are added to allow access to the VM with the NIC IP address. Check the firewall settings and add the required rules if they're missing.
    • Utilize the self-hosted integration runtime diagnostic tool available from the Configuration Manager to identify any issues. Run the diagnostic tool and follow the instructions to fix any issues that are identified.
    • If the above steps don’t resolve the issue, consider uninstalling and reinstalling the Integration Runtime. Make sure to download the manual Integration Runtime (not the express version) and install the latest version. This will ensure that any corrupted files are replaced.
    • Make sure that your Integration Runtime is using TLS 1.2, which is the default security protocol for Windows Server 2012 and later versions. Check for any available updates and install them to ensure that your Integration Runtime is up to date.

    Reference:
    https://learn.microsoft.com/en-us/azure/data-factory/tutorial-enable-remote-access-intranet-tls-ssl-certificate

    https://learn.microsoft.com/en-us/azure/data-factory/self-hosted-integration-runtime-diagnostic-tool

    I hope this information helps you. Let me know if you have any further questions or concerns.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful