Self Hosted Integration Runtime Connection Failed with Azure Cosmos DB for PostgreSQL

Question

In datafactory we have a step which connects with Azure CosmosDB for PostgreSQL to copy the some data to other DB using self hosted integration runtime, Its was working fine till last week. Suddenly there is intermittent connectivity issue & we are getting following error.

The same activity able to make connection if we retry couple of times. Some stages establish connections successfully, while others fail with error.

message: Copy failed with error: 'Type=System.Security.Authentication.AuthenticationException,Message=A call to SSPI failed, see inner exception.,Source=System,StackTrace=   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at Npgsql.NpgsqlConnector.d__153.MoveNext()

We have also tried setting up new IR'S, for the same. But it still produces the same error output. We are unable to determine a solution to this problem, we would greatly appreciate any assistance in resolving this issue.

Answer

Hello @Farhan Abdul Shakoor

The error message you provided indicates that there is an issue with the SSL/TLS connection between the self-hosted integration runtime and Azure Cosmos DB for PostgreSQL.

To troubleshoot this issue, you can try the following steps:

Check if there are any firewall rules that might be blocking the connection between the self-hosted integration runtime and Azure Cosmos DB for PostgreSQL. You can check the firewall rules in the Azure portal for your Azure Cosmos DB account.
Check if the SSL/TLS certificate used by Azure Cosmos DB for PostgreSQL is valid and trusted by the self-hosted integration runtime. You can download the certificate from the Azure portal and install it on the machine where the self-hosted integration runtime is running.
Check if the self-hosted integration runtime is running on a machine with the latest updates and p4atches installed. You can also try restarting the machine to see if it resolves the issue.
Check if there are any network issues between the self-hosted integration runtime and Azure Cosmos DB for PostgreSQL. You can try running network diagnostics tools like ping and traceroute to identify any network issues.
Check if there are any issues with the authentication mechanism used by Azure Cosmos DB for PostgreSQL. You can try using a different authentication mechanism like username/password or Azure Active Directory to see if it resolves the issue.

I hope that this response with 5 steps addressed your query and helped you overcome your challenges. If so, please mark this response as Answered. This will not only acknowledge our efforts, but also assist other community members who may be looking for similar solutions.

Share via

Self Hosted Integration Runtime Connection Failed with Azure Cosmos DB for PostgreSQL

1 answer

Your answer