How to fix the issue "Client initialization failed. Check if the endpoint is reachable and if your auth token is valid" in azure data flow

Waz Wen Ou 5

Hi I created an Azure data flow that transfer json from json file to cosmos db. The CosmosDbNoSql linked service connects successful. The Blob storage linked service for json file connects successful as well. The data flow is ok without any error. When refreshing data preview in debug the error always display. "Client initialization failed. Check if the endpoint is reachable and if your auth token is valid. More info: https://aka.ms/cosmosdb-tsg-service-unavailable-java" User's image

The link displays the blow content; User's image

It would be appreciated someone can let me know how to do the process in red line or how to the issue as I don't find any details about it. Thanks million.

1 answer

ShaikMaheer-MSFT 38,301 Reputation points Microsoft Employee

2024-01-30T09:20:34.26+00:00

Hi Waz Wen Ou, Thank you for posting query in Microsoft Q&A Platform.

You mentioned that linked service of cosmosDB connects successfully. You might have used different IR in cosmosDB linked service and different IR in blob storage linked service.
Kindly try using IR of cosmosDB linked service in blob storage linked service too and see if that helps.

Please let me know how it goes. Thank you.
Please sign in to rate this answer.
Waz Wen Ou 5 Reputation points

2024-01-30T23:52:12.4266667+00:00

Hi Shaik Thank you for your reply. As I'm new in Azure I don't understand what IR is. Can you please give me more details and how to do that.Thanks

Waz Wen Ou 5 Reputation points

2024-01-31T01:09:45.8133333+00:00

Hi I created a new Azure integration runtime for cosmos. The connection works. The integration runtime for blob hasn't been changed and uses the default (AutoResolveIntegrationRuntime). The same issue happen again. Do you have any idea? Thanks.

Waz Wen Ou 5 Reputation points

2024-01-31T01:21:51.1866667+00:00

I created a new Azure integration runtime for Cosmos. The connection works well. The integration runtime for Blob hasn't been changed and uses the default (AutoResolveIntegrationRuntime). Then run the refreshing of data preview of data flow. The same issue happens again. Do you have any idea? Thanks

ShaikMaheer-MSFT 38,301 Reputation points Microsoft Employee

2024-01-31T06:35:27.56+00:00

Could you please try to use Azure integration runtime only in both blob and cosmos linked service and see if that helps?

Waz Wen Ou 5 Reputation points

2024-01-31T22:24:46.21+00:00

Hi Shaik Thank you for your reply. I created a Azure new IR for Cosmos and keep the default IR for Blob. When debug my data flow the same error raised again. Do you have any idea? Thanks in adv.

Cosmos IR

Blob IR

ShaikMaheer-MSFT 38,301 Reputation points Microsoft Employee

2024-02-01T06:36:34.1033333+00:00

No, don't use default IR in blob. In blob also use same Azure IR which you used for cosmos and see of that helps.

Waz Wen Ou 5 Reputation points

2024-02-02T04:57:28.1833333+00:00

Hi ShaiK I created an Azure IR and applied it to both. But the same error happen again. any idea? Thanks

ShaikMaheer-MSFT 38,301 Reputation points Microsoft Employee

2024-02-02T06:00:44.5233333+00:00

Hi Waz Wen Ou,

While you turning on debug session, make sure you select Azure IR in it. That way we may not see this error.

Hope this helps. Please let me know if you have any further queries.

Please consider hitting Accept Answer button. Accepted answers help community as well.

Waz Wen Ou 5 Reputation points

2024-02-05T02:34:27.5066667+00:00

Hi Shaik Thank you for your help. I found the issue was in Cosmos database as the Blob link service can works and I can preview Json data. The cosmos link service doesn't have permission to access Cosmos database. The below is the network setting of Cosmos database. Do you have any idea to how set up authentication token. Thanks.

ShaikMaheer-MSFT 38,301 Reputation points Microsoft Employee

2024-02-05T06:32:13.9066667+00:00

Hi Waz Wen Ou,
You tried with selecting Azure IR in the debug sessions enable part? If yes, then it helped to perform data preview? If yes, then kindly consider marking it as accepted answer. Regarding, allowing access, It seems you might need to add related IP address to allowed network. So technically IP addresses for your Azure IR we might need to add to firewall rules. For example, If your Azure IR is specific to East US, then use DataFactory.EastUs to get the IP address range for specific region and whitelist them. Also please note below message: Ref doc: https://www.microsoft.com/en-us/download/details.aspx?id=56519 Hope this helps. Please let me know how it goes.

Please consider hitting Accept Answer button. Accepted answers help community as well. Thank you.
Sign in to comment